Why is there so much hate for ASP.NET?

define "hate"? :D
Idk, I think it's oki, I just never use it since I find it's stuff unattractive to my eye. :D

I hated how convoluted the framework was. Not C#, but all the messy config files that went into an application and you have no idea what half of them are or they they make your project slow to build on good days and broken on bad days. It made me feel distanced from the code itself. Tying together all the stuff it did increased the chance that something would break, and you wouldn't know how to fix it because the code was auto-generated.

...and what @AndSoWeCode said. 😂

Microsoft.

@dontbeevil In this case, it actually is a good reason.
ASP.NET still has the same flaw that caused the whole Microsoft mess: The underlying base technology is non-free. A single corporate entity has full control over the whole technology stack.
They could, in theory, from one minute to the next, decide that the fundamental technology your whole business is built upon is now legacy technology.

With a free platform, that cannot and will not happen. If you take the Java platform as an example, you can see that there is a multitude of languages for the JVM. So if you are unsatisfied with Java, you can gradually switch to another language without having to re-implement massive amounts of code.
This is only possible because the underlying platform is free, something that Microsoft, at the moment, is still not willing to do.

@3141 and what about .net core?

@AndSoWeCode no way. You lose control if you write crappy stuff. SoC is very well possible with asp.net and even webforms hated by many gives you almost full control of you are proficient in it. Anyway if you want full control use asp.net mvc.

Cuz it old

@AndSoWeCode who dafuq would'be launching a serious project on Mono though

@AndSoWeCode I agree that my language example was bad. But the availability of alternative languages for the .NET platform doesn't change the problem that the platform itself is still non-free. The fact that Mono now belongs to Microsoft, doesn't improve the situation, because Microsoft now has even more control over the platform.
Even without ownership of Mono, Microsoft could still shutdown the project with the shit ton of patents concerning C# and .NET.
As far as I know, .NET core is still a very limited subset, but I stand to be corrected on that topic.

@Obi-WanSpock Yea that's what I meant and I can see why now :D

@AndSoWeCode As far as I know it does let you do that. I have never ever encountered such issues, not in asp.net webforms nor asp.net mvc. I've been developing web apps on asp.net since the very beginning and still am today. Mvc really does give you full control and even with webforms you can do almost anything. So, now I'm wondering, what important stuff couldn't you get done?

It's heavy, even if you're using mono -- using .NET on a non windows OS just feels weird. The architecture for basic applications is fucking prehistoric. And finally, there are numerous better platforms available.

I don't see why in this day and age, any web developer (Frontend, backend, or full stack) wouldn't default to Node. One language, one dependency management system.. Everywhere vs architectural bullshit.

I too prefer Node honestly but I wanted to know what everybody thought
And obviously it's mostly negative :D
@neetjn

@InEdited hipsters. NPM and Yarn are both superior to compose, pip, and gems. The workflow with JS projects is so streamline.

You can bootstrap an app in an hour if you know what you're doing. You also have so many super sets at your disposal like Coffeescript for Python and ruby devs, and TypeScript for C++/C# devs.

It's 2017, tons of court trials since SCO case and people still believe that what Microsoft names "open source" is far from being Open Source.

I'd suggest to those of you, who have at least heard about SCO case, to check the license of dot net libs. Also to find out how many patents is protecting the dot net. Keep in mind that using a 'open software' doesn't mean you are protected from patent claims. If not Microsofts than 3rd party trolls. Like SCO.

@AndSoWeCode asp.net core is freaking awesome.

Im using it in production since 1.0 and never had any issues with it.

Microsoft is going the OpenSource way believe it or not.

Since ballmer and gates are gone, Microsoft has done great things.
I make a living by using microsofts tools without the need to pay them.

@AndSoWeCode For that I understand your opinion. But there are ways around it, even in older asp.net versions and it is so because in webforms the form runs server side. In asp.net mvc that really is not an issue at all.

But your opinion on this is not really fair. It's like me saying php sucks bigtime. And it does. Or is it because many people write crappy, unmaintainable code with it? Or I couldn't achieve something which was really easy in a different technology?

I get your point though but really, it is absolutely not that bad, especially when you have lots of experience with it and nowadays you can create almost anything with the MS stack.

@AndSoWeCode Like I said you don't have that form issue with asp.net mvc, you can use as many forms as you like. And you can plug in angularjs validation, even wirh custom validation attributes defined in backend c# with some extra js to have them working on client side as well. I'm absolutely sure about this as currently I'm working at a bank building a new account opening process built completely on asp.net mvc with angularjs and web api. We use many custom made angular directives for advanced validations too. I don"t get why you can't send any custom output. If you would implement for example an IHttpHandler you can send anything you want. But in my experience you almost never need that.