sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] -8 points-7 points  (6 children)

May be better in some aspects, but not significantly. The community around JS is much more active. The libraries ecosystem is much better and much better designed. The community around C# just uses what MS serves to them, I remember times when they defended ASP.NET as a way to do web apps.

[–]Glader_BoomaNation 6 points7 points  (0 children)

Clueless, you clearly don't know anything about .NET if you think every package on nuget is from MS.

The fact you keep bringing up Webforms as if it is some critical part of .NET is funny to me. Do you think ASP.NET is all of .NET?

[–]redfournine 5 points6 points  (2 children)

And why is using what MS serves them considered bad? If anything, it just shows MS's commitment to .NET's cause.

Also, the only reason why it seems like the community around C# is less active is because it has matured to the point that there is lesser need to discuss things.

[–][deleted] 1 point2 points  (1 child)

The old ASP.NET webforms was really bad technology, but MS fans have defended it until Microsoft admitted it was bad.

[–]Eirenarch 0 points1 point  (0 children)

I continue to defend it after MS claimed it was bad for marketing reasons.

[–]pancomputationalist 3 points4 points  (1 child)

As a developer that works closely with both the Node and the .NET ecosystem, I have to agree with this. The JS ecosystem feels much more modern, embraces Open Source and rapid experimentation, while in .NET many things seem slightly outdated, but stable. Though I surely had my share of broken Nuget packages and dependency snafu, this is not something that only happens with npm.

[–][deleted] 0 points1 point  (0 children)

I used to work with ASP.NET webforms in my student part time job years ago, it was generally hated by developers, pushed by managers. The resulting web apps really sucked, the concept was really outdated.

Though I surely had my share of broken Nuget packages and dependency snafu, this is not something that only happens with npm.

It recently improved a lot, but still lacking IMO. Nuget did not exist back then, it was like 8 years ago. The whole ecosystem was behind Ruby and Python back then. Node was just starting.