@Unperverted-Vixen said in Thoughts on why so much .NET code is just awful...:
@MSgtSoupSandwich said in Thoughts on why so much .NET code is just awful...:
I guess that's my main point. There is probably no other framework or development technologies that has suffered through so many radically different flavors-of-the-month.
That's only because they keep starting over and making you learn new languages (e.g. Go, Node.js). .NET has been able to let you keep using the same language with newer web frameworks. IMO that's a feature, not a bug.
Agreed that this is what's happening. Don't agree that there's some benefit vs. just making a new language or framework. Keeping it all ".NET" is what got us to this sad place.
The result is a lot of code that's written by people learning the latest flavor-of-the-month vs. coherently applying something proven and well-known.
"Proven and well-known" != "the right tool for the job". If you want to do anything client-side on your site, Web Forms is poorly suited to the task.
In general, I'll take code written by someone who's not learning on the job over code written by someone who is.
I'd also dispute that it qualifies as "well-known". I'd be surprised if I could find more than two devs here who know the page lifecycle.
But if we hadn't all moved on to WPF / MVC maybe people would know those parts of the page lifecycle that actually matter.
This is not to say that I think WebForms was particularly good, though. Honestly, none of .NET is very good outside of maybe Linq, but if it were better-applied it would be more than adequate.
Have not been at a place where we could do that since 2017. Not sure exactly why... I think it has something to do with wanting to use "real" IIS, and also relates to the perception that things are faster the "attach to process" way once you've done the attachment two-step.
There's no need to use real IIS for development. IIS Express does the job just fine.
I agree, but something is motivating this "attach to process" shite. I'd dig into it more, but learning more about .NET isn't on my to-do list anymore. I endure it for money.
Other languages don't even suffer from this "build" issue. Two I have worked with professionally that have no such step are PHP and Clojure.
No, instead they suffer from being PHP and Clojure.
PHP? It's just unpretentious and unobtrusive. Ugly but useful.
Clojure is functional. It seems unfamiliar to people, but every language still being enhanced is getting functional programming grafted onto it right now. JavaScript is. C# largely has already. C++ is becoming functional, in a very obnoxious way. You can't dodge the core of Lisp by hiding in C# Web development anymore.