I think .NET and C# are moving too fast and focussing on the wrong things. Lets talk about it.0:00 The debate about .NET and C# moving too fast1:26 .NET's bi...
Yes, that’s his point. That if you’ve released your app close to the end of the period, then you’re forced to upgrade your app right away, even just to keep getting security patches, on top of any bugs you might already be trying to get on top of with your newly released app. Other systems have a longer support period and you wouldn’t be faced with that.
If you look at LTS dates, 6 overlaps 8 by a year. And when it comes to patches, there are two scenarios. One is framework dependant app where you don’t have to do anything. And there is self-contained where you have to update the app - but how else would you patch it - this is the same for every app out there, isn’t it?
Yes, that’s his point. That if you’ve released your app close to the end of the period, then you’re forced to upgrade your app right away, even just to keep getting security patches, on top of any bugs you might already be trying to get on top of with your newly released app. Other systems have a longer support period and you wouldn’t be faced with that.
If you look at LTS dates, 6 overlaps 8 by a year. And when it comes to patches, there are two scenarios. One is framework dependant app where you don’t have to do anything. And there is self-contained where you have to update the app - but how else would you patch it - this is the same for every app out there, isn’t it?