Reply to post:

Microsoft's .NET Core 3 is almost here, which means time to move on from .NET Framework

DropBear

I'm not particularly familiar with VS specifically but we live in a post-fixing-bugs world, don't you know. The current MO is to just move fast and when (not if) you break things just keep adding enough new bugs until the old one gets superseded naturally all on it own. And if in spite of your best efforts the code ever shows signs of stabilizing just declare it obsolete, abandon it, and rewrite everything using the latest even more bug-ridden tech, from scratch. Repeat as many times as needed, but long before you reach anywhere near feature parity with the old version. We live in a world of continuously improving software, where "better" is defined as "never mind the loss of features and stability, feel that Nightly goodness!".

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon