3 ms·
There's an opportunity cost to supporting older versions. Sure, there's always going to be a small group of people who are happy with what they currently have
by melling 12y ago
There's an opportunity cost to supporting older versions. Sure, there's always going to be a small group of people who are happy with what they currently have but most people are happy moving forward.
If there's a big enough market, perhaps some company will backport the security fixes. How much are you willing to pay? Another option is that you could volunteer and start the fork.
Of course, there's that other problem where developers are only going to support the latest browser.
- walterbell 12y agoA functional subset would not be a fork. If users were given a choice, we would find out which version they considered best aligned with the brand.
- melling 12y agoYou aren't being clear. Do you think that older code that gives older functionality doesn't ever get changed? Patches will have to be created, etc. It's not trivial work. And as I mentioned, web developers aren't going to support the older CSS/HTML/JavaScript in your older browser.
- walterbell 12y agoLack of clarity was due to sibling comment. Repeating here: an option is to patch the current code to remove unwanted new features. This provides users with current features, e.g. CSS/HTML/JS and security fixes, a "minimal build" of the browser.