3 ms·
> No new ChromeOS meant no new Chrome which meant stuck at version 76. > But what about the iPad? I discovered that my Mom’s iPad was a 1st generation iPad Air
by bee_rider 5y ago
> No new ChromeOS meant no new Chrome which meant stuck at version 76.
> But what about the iPad? I discovered that my Mom’s iPad was a 1st generation iPad Air.
> “But what was the culprit in the website,” you ask? After opening the developer tools on the Chromebook and looking at the console, I discovered the website authors were shipping JavaScript that used the optional chaining operator (?.), an unsupported syntax in older browsers that caused the entire website to fail.
[...]
> This only reconfirmed my parents’ belief that device makers deliberately make things go out of date so that you have to go buy new hardware every couple of years.
> I wanted to try and explain to my Mom that, while true for many native applications, browsers shouldn’t go out of date so easily because of hardware. “This isn’t your problem Mom. You should’t have to go buy new hardware. This is a problem with the people who make that website. They should be making their website’s code more accessible to legacy devices. Just because you don’t have a browser that can run ECMAScript 2020, you should still be able to access and use this website.”
I mean, it's been supported since 2020 in both Firefox and Chrome.
I can see a good argument for ensuring that websites will run with no javascript whatsoever as an accessibility feature. I mean, I think at least that plain text is easier to handle for screen readers most of the time. But I don't see any obligation to support 2 year old browsers, what other updates is a 2 year old browser missing? Seems insecure.
Should the 9 year old iPad air still be supported with new browser versions? Maybe. 9 years seems beyond the norm. It would be nice if devices were required to be opened up after they lapsed into an unsupported status.
- lolinder 5y agoI'm all for not bending over backwards to support a 10-year-old browser, but 2 years is a really tight support window.
- bee_rider 5y agoIt is software. It can be updated over the internet. People should run up to date browsers.
- mauricioc 5y ago> So I looked at the version of Chrome on my parent’s computer. Version 76! I knew we were at ninety-something in 2022, so I figured that was the culprit. “I’ll just update Chrome,” I thought. > Turns out, you can’t. From what I could gather, the version of Chrome was tied to ChromeOS which couldn’t be updated because of the hardware. No new ChromeOS meant no new Chrome which meant stuck at version 76.
- bee_rider 5y agoThe blame here falls on Google, not the website developers.
- lolinder 5y agoIt falls on Google and the website developers. It's up to Google to allow people to update their software. It's up to the website developers to recognize that the reality doesn't always match the ideal and to develop for the reality.
- bee_rider 5y agoI disagree, Google and Apple are the ones that have locked these devices down. They have the keys and the technical abilities -- they have an obligation to keep them up to date or unlock them. There might be a business rationale to bend to reality, but no obligation. In this case it appears to be a volunteering organization, so I guess they might not be as motivated to solve niche problems.
- deleted 5y ago[deleted]
- simion314 5y ago>it is software. It can be updated over the internet. People should run up to date browsers. There are 2 issues 1 some hardware is locked, you can run what you want on it, it must be approved. In the TFA is is cearly shown that it was impossible to run a new browser version. 2 since is just software as you said, I assume the developers could install some software and have the JS transpiled to a more compatible version or popup a message if the user does not use latest Chrome or Safari and send them away. Maybe search engine should check this websites in an older browser engine and remove SEO points, also try the website with JS off and if you get nothing, no text that you need JS also remove points.
- _dain_ 5y ago>Should the 9 year old iPad air still be supported with new browser versions? Maybe. 9 years seems beyond the norm. Why shouldn't it? It's a perfectly usable device. Why should it have to go to landfill?
- frumper 5y agoIt doesn't need to. The website developer chose to use new language features that older devices aren't likely to support. If your website needs users to upgrade their OS or browser to use it, then you should be comfortable with some people not being able to use it.
- bee_rider 5y agoI mostly object to the article which seems to be pretty explicitly pointing the finger at the web developer, for using 2 year old, standard features of their language. There's a problem between the user and the device manufacturer here. A decade seems like a long time for first-party support but as I said in the sentence immediately after the one you quoted, a device should be required to be opened up when it is no longer supported.
- pph 5y agofirefox-esr on Debian is currently on Version 78esr [0], which is 1½ years old by now [1]. [0] https://packages.debian.org/search?keywords=firefox-esr&searchon=names&exact=1&suite=all§ion=all https://packages.debian.org/search?keywords=firefox-esr&sear... [1] de.m.wikipedia.org/wiki/Versionsgeschichte_von_Mozilla_Firefox (the English page is useless for historical release information)
- Karellen 5y agoThat's not quite correct. That is the version in the most recent point release of Bullseye (11.2). But the version currently in bullseye-security, uploaded on Dec 19th, is ESR 91.4.0. (stable-sec: 91.4.1esr-1~deb11u1) That's from the upstream release dated Dec 7th(/16th?) which is the current upstream ESR release. https://tracker.debian.org/pkg/firefox-esr https://tracker.debian.org/pkg/firefox-esr