News for hackers. Stuff that matters.

A comment on .NET 10. Parent comment

Re:.NET 10 by sfn42 on Wednesday November 12, 2025 @06:56AM (#45899070)
So you don't like .NET, that's fine. I'm not saying everyone needs to use .NET. I'm saying pick one thing and stick with it.

That said I think you're exaggerating those complaints, the docs for C# are quite good imo and I've been working with ASP.NET web apps for half a decade so far and I'm not seeing any problems like you're describing.

Maybe you're miffed about the Framework to Core/.NET switch? That was a bit of a doozy but the ecosystem is so much better for it I'd say it was worth it.

[ Parent | on HN ]
Re:.NET 10 by SideburnsOfDoom on Wednesday November 12, 2025 @07:07AM (#45899165)
> the thing you wrote last year doesn't look anything structurally like what you're doing now... all the 6-month-old on-line docs and tutorials aren't only useless, but time wasting.

This is indeed a complete exaggeration.

[ Parent | on HN ]
Re:.NET 10 by ourmandave on Wednesday November 12, 2025 @07:26AM (#45899314)
Sorry, I love .NET and have used it from it's rollout back in 2002.

I'm just fondly remembering the ASP.NET MVC churn or more recently, Azure API whiplash.

[ Parent | on HN ]
Re:.NET 10 by SideburnsOfDoom on Wednesday November 12, 2025 @04:14PM (#45906818)
[delayed]
[ Parent | on HN ]
Re:.NET 10 by to11mtm on Wednesday November 12, 2025 @05:07PM (#45907494)
I get you actually.

MVC churn was real, EF Churn was real, heck NETCORE itself was a (at least warned about) churn, 3.1->6.0 was minor but still definitely a thing [0].

[0] - Now that I'm thinking it out loud, maybe that's why they changed the branding from .NET CORE to just .NET; The churn was more or less 'done'...

[ Parent | on HN ]
Re:.NET 10 by mycall on Thursday November 13, 2025 @06:53AM (#45913812)
I'm only now deprecating a netcore 2.2 API that used a 4.8 framework domain/repository layer. At the time it seems like a good idea and it received automatic security patches.
[ Parent | on HN ]