6 ms·
You are clearly thinking about smaller projects. Larger projects can't survive a "stop the world" / "go async" migration. So, what do people do, they use GetAw
by osigurdson 3y ago
You are clearly thinking about smaller projects. Larger projects can't survive a "stop the world" / "go async" migration. So, what do people do, they use GetAwaiter().GetResult knowing it is bad.
I was responsible for one of the largest .NET to .NET core migrations in history (3M LOC). Not a good time to also make everything async "while you are at it".
- hnthrow289570 3y ago>You are clearly thinking about smaller projects. Yes, because that's the majority. You will probably not see another major upgrade from .NET to new-shiny-thing in a decade or more, so you may as well take the extra time to do things right for .NET now, even for the largest projects. There have been multiple LTS's to target, and once you are over the initial Framework -> .NET "hurdle", upgrading from there should be much easier. >Larger projects can't survive a "stop the world" / "go async" project. I don't know how it would be fatal unless the company doesn't want to give you the time for it - either because it doesn't make financial sense or they haven't been convinced. .NET is certainly one of the easier languages to refactor with confidence. If it will never make financial sense, then I guess it'll go on to join the still-running COBOL projects, but that's an outlier.
- SirMaster 3y agoIsn't Visual Studio 2022 still written in and running on .NET Framework? Even Microsoft can't manage to migrate it to modern .NET.
- osigurdson 3y agoI think it is mostly C++, no?