Hacker News Reader

Comment by procinct | Hacker News Reader

I definitely don’t find modern .NET (ie .NET Core) to be overly enterprisy or boilerplated at all. Certainly nothing like .NET framework or Java.

View on HN

Gotta admit GP has a point about naming though.

Search for info on .NET and you will find stuff on ASP.NET, .NET Framework, .NET Core at the very least. Probably more.

You have to really know what you are looking for and that's hard sometimes because everything is just .NET

This was made even worse when .NET Core was renamed to just '.NET', making it difficult to get good, specific results when googling.

Simply search for ".NET 5" and ".NET 6" including quotes.

I very rarely search "dotnet". Usually searches are based more around the specific technology/library/namespace in the ecosystem I have questions on. This feels to me like a non-issue.

This .net core good, asp.net MVC etc bad.

You haven't seen nice MVC middleware pipeline configurations with a decent number of services (DI).

Sometimes I feel like being on JEE 1.4 days.

Gotta love those enterprise architects.

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.

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,....

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.

Reply on news.ycombinator.com