undefined | Better HN

0 pointsjiggawatts4y ago0 comments

This wouldn't matter so much except that Microsoft completely broke all backwards compatibility for ASP.NET web applications. There's no "wizard" upgrade.

I'm working on migrating an ASP.NET 4.0 application right now, and it's basically stuck in the past.

Physically, yes, it could be updated by the developers to work on .NET 6.0, but no manager will ever fund this. They don't understand the benefits, and no amount of explanation will justify this effort in their minds.

So Microsoft basically stranded their customers on an iceberg floating away from the shore that is very slowly, almost imperceptibly melting...

0 comments

kinjba114y ago

This. In many ways .NET Framework is to .NET Core/6 as Python 2 is to Python 3. The new stuff is all phenomenal, truly. But there are mountains of code running right now, responsible for billions of dollars of economy, still being maintained and added to, that will never be ported to the new. One wonders how our young industry of software development will evolve into the future, how many COBOLs are being created as we speak. Old cars, planes, bridges, buildings and roads eventually stop working and break down, but code is code. Or is it?

kumarvvr4y ago

> but no manager will ever fund this

Looks like the way to convince them is to tell them we will be moving to a <gasp> microservices <gasp> based stack and slowly start building the services on modern stacks (and gRPC)

DeathArrow4y ago

>Looks like the way to convince them is to tell them we will be moving to a <gasp> microservices <gasp> based stack and slowly start building the services on modern stacks (and gRPC)

We did just this at the company I work for. We are replacing an old monolith with modern architecture.

jiggawattsOP4y ago

I mentally translate "modern" to 0.3.54 build 72 alpha.

j / k navigate · click thread line to collapse