5 ms·
If your app lives in a vacuum I don't see why you'd ever need to upgrade the framework. If it doesn't then the code you wrote yourself will eventually break as
by mrits 3y ago
If your app lives in a vacuum I don't see why you'd ever need to upgrade the framework.
If it doesn't then the code you wrote yourself will eventually break as the rest of the world advances their APIs and standards.
Even a website written in pure HTML and put up on a small linux server a decade ago would have rendering issues as well as probably not allowed past browsers or corporate firewalls due to older SSL libraries.
- unoti 3y ago> If your app lives in a vacuum I don't see why you'd ever need to upgrade the framework. Unfortunately the only apps that live in a vacuum are embedded apps not connected to the internet. We should all be monitoring our dependencies for security upgrades. Eventually even a stable framework like Django goes out of long term support. I wrote a Django app in 2008 that is still in heavy use today and at some point had to go through and upgrade to a new major version. It wasn’t a breeze, it took me a few weeks. To leave the app live on that 10 year old version would have been irresponsible for security reasons. The only apps that live in a vacuum are embedded apps, like the one in a vacuum cleaner.
- mrits 3y agoThe vacuum gets power from an electrical network that is also fully capable of transferring structured digital information as well. My point is that your own code will also break if you don't keep it maintained for all practical purposes.
- dalke 3y agoMy static pure HTML+CSS site is nearly 20 years old and renders just fine in modern browsers. It's so old it has no https interface. I do depend on my hosting provider to keep Apache and FreeBSD up to date, if only for security reasons.
- mrits 3y agoYeah, that was my point. You couldn't get to non https sites in a lot of situations