3 ms·

The difference here is that those mainframes aren't used by people to interface with the internet as a whole. People shouldn't be building things in web techno

The difference here is that those mainframes aren't used by people to interface with the internet as a whole. People shouldn't be building things in web technologies if they aren't willing to keep up with them, which isn't that hard. Unless your web app is poorly designed (i.e. reliant on browser-specific bugs or proprietary features), then an evergreen browser shouldn't be a major concern. If your crap is so mission critical that this is still a concern, then web technologies are entirely the wrong stack to be working in.

dmitriid 8y ago
Chrome is evergreen, right? Oh, wait, it regularly drops or destroys features that people rely on (often with no warning). And IE10/11 are not that old. When people were developing for them they were current. Just because you've never developed software that needs to be supported for ore than two months, doesn't mean no one does. > If your crap is so mission critical If it's mission critical, it's not crap. Crap is stuff that is "not hard to keep up with the web technologies that change every two months".