What's so enterprisey about the modern Host/DI? Honestly seems really clean and thin to me.
Nothing, IMO. DI, when used properly, significantly cleans up code bases. It's code bases without DI that often become both untestable and unwieldy.
The keyword here is used properly.
Now go on to work on codebases with rules that every class must have an interface, there are no news, everything must come over service locators, 3rd APIs aren't accessed directly, rather over wrapper classes,....
Ah and no PR ever gets accepted if the rules aren't followed.
Re:.NET Myths Dispelled
by erik_seaberg on Sunday March 13, 2022 @06:04AM
(#30659800)
Any language that permits any style choices at all is going to be vulnerable to self-inflicted rules requiring bad style.
Just like any language used in enterprise shops is not free from enterprise space architects, and .NET is no exception given its customer base from Microsoft products.
Codebases with rules that every class must have an interface, there are no new in use other than basic stuff like arrays, everything must come over service locators (configurable externally), 3rd APIs aren't accessed directly, rather over wrapper classes,....
Re:.NET Myths Dispelled
by manigandham on Sunday March 13, 2022 @05:15PM
(#30665786)
Sounds like a problem with your devs/architects/process than the language stack. It would create a mess out of Java or Go or Ruby too.
Sometimes I feel like being on JEE 1.4 days.
Gotta love those enterprise architects.