4 ms·
It's still extremely buggy. Very difficult to get a .NET MVC app up and running (they're not using the term WebAPI anymore).
by dimgl 10y ago
It's still extremely buggy. Very difficult to get a .NET MVC app up and running (they're not using the term WebAPI anymore).
- mattmanser 10y agoI also think they've made a terrible decision, the first-class support for DI is a bad direction which has made many simple concepts like config settings into absolute farces that take 5 lines of code. It's code "purity" over usability. It's putting the core dev team's principles over their customers actual need, completely violating KISS, DRY and YAGNI. DI really is our generation's factories. I'm already seeing projects written by people who don't understand it making utter nightmare spagetti code, worse than any code I've ever seen. It's nasty scaffolding code which is a symptom of limitations of the language, definitely not code anyone should ever actually be wasting time writing. Instead of recognising it's a flash in the pan, the core team have embraced it and are trying to force it down everyone's necks, and a lot programmers simply don't get it and are making an utter mess instead.
- romanovcode 10y ago>and a lot programmers simply don't get it and are making an utter mess instead. Then maybe those programmers should go back to JS ES5?