2 ms·
They're getting more and more opinionated in some of the frameworks too, it's getting quite tiresome in the asp.net field. First it was harping on about pure re
by mattmanser 9y ago
They're getting more and more opinionated in some of the frameworks too, it's getting quite tiresome in the asp.net field. First it was harping on about pure restful controllers which are nothing but a massive PITA, then I had a dabble in ASP.net Core and they'd changed ConfigurationManager to be Dependency Injected instead of an incredibly simple static object.
Yeah it's great improvement to have it nicely typed, but keep it static, I don't want to be DI-ing everything, especially when I'm just throwing together a prototype.
I want easy to use, not dogmatic adherence to ideals that gain you absolutely nothing but a confusing mental model in something like semi-permanent config.
- cm2187 9y agoOpinionated and changing opinion frequently... First we had webforms, then rest api, then asp.net mvc, then asp.net core mvc and now razor pages to bring back webforms...
- mattmanser 9y agoWith a couple of dabbles in OData. ODataControllers are some of the most painfully bad things I have ever had the displeasure of programming with, I'm migrating our code bade back over to using API controllers with the semi-broken OData plugins rather than use them. Admittedly part of that is because OData is great for plugging into grids like datatables for jquery or kendo grid, but otherwise incredibly over-complicated. It sometimes feels as if they can't make their mind up about anything, and yet invest heavily in the latest fad that disappears a year later. Surprised they've not released an update yet that forces everyone to use yarn instead of nuget.
- Const-me 9y agoNot that frequently. Web forms are from 2002. It‘s ancient by today’s standard, much older than e.g. facebook or youtube.