Absolutely, … in their container… 
No, that part is absolutely appreciated. That’s fantastic.
Just a professional disagreement, nothing more, nothing less.
Personally, I’d love to buy @Epic_Santiago a few beers 
and pick his brain. Doesn’t mean I have to agree with him or Epicor’s mindset.
Yes but the SLA that you signed with Epicor says they have a 99.99999999999 ← not sure how many 9’s of uptime… and if you break it you buy it 
Responding to a few of the comments here:
I wasn’t thinking of a bribe, but c’mon down.
I got a few cases with your name on it.
This is the best place on the internet.
LOL…it’s Friday, we’re entitled to be thirsty early. Too bad our summer hours are now over…no more 3p departures, the suffering continues to 5p. Boo.
But refection has been getting the side-eye for the last few years in favor of source generators. They can’t do everything as reflection, but it can help with performance and some stability when using optimizations like “tree shaking.”
If he uses reflection from BPM, anything that can be tree shaken from platform code is already shaken away 
Asking from a point of ignorance, but I’ve seen this kind of code on this site:
Assembly assembly = Assembly.LoadFrom("some.dll");
When would this be shaken?
In fairness, Epicor also breaks their own code on update at a fair clip. That’s not a dig, it’s just the nature of the beast.
Presumably those that wrote the code can fix any such problem, and (typically) we arent using these patterns for the fun of it, we are solving real business problems.
You mention the goal isnt intended to corral more people into CSG’s arms, however you are leaving a very tall fence that people who want to get out of the line have to climb over (or under).
I hear you that customization isnt going away, but it feels like the difference between getting to chose the make\model of your car vs just the color.
I don’t think I can replace clever articles in couple of sentences, but theoretically, after the projects (that is all platform code) are compiled they can be analyzed for used classes/methods and unused one can be deleted.
If you load something using reflection in this code, this cannot be tracked and you risk to lose the method you are supposed to call.
Kevin 
uses our code after everything is compiled and theoretically treeshaken. So if he could write that code that loads “some.dll” and it contains the methods, then it good to be used at least until next release, where it can dissappear. But undocumented function can dissappear anyway 
Epicor (or any ERP provider), consultants/outsource OR staff developers can break anything. It’s an equal-opportunity opportunity at crashing the system. 
But a couple of paragraphs worked a charm! Thanks @Olga!
Next week, Microsoft is hosting a meeting with developers from other companies, most notably Crowdstrike, to find ways to allow these developers to securely solve business problems without taking down Windows. Some devs (both inside and outside of Microsoft) will argue that kernel access is the only way to solve business problems. Others in the room (mostly non-devs) will be more conservative and demand safety over performance or functionality. The meeting hopes to find a balance and maybe introduce a whole new paradigm, who knows? 
Epicor is in a similar position. It’s like we say here all of the time, what business problem are we trying to solve? If “that’s the way we always did it” is not working out any longer, let’s do what we tell our users and try to work within the system.
How is it ample warning when no timeline has been communicated? They may break everything I have in December. Or next May. Who knows?
Which one of your babies is going to die on the alter of security anyway?
