News for hackers. Stuff that matters.
Re:The optional chaining operator, “modern” browsers, and my... by skulk on Tuesday January 11, 2022 @12:20PM (#29894425)
> 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.

This is the most surprising part of the article. If ChromeOS does not allow the browser to be updated after the hardware has reached end-of-support, I would recommend it to nobody, ever.

Re:The optional chaining operator, “modern” browsers, and my... by easton on Tuesday January 11, 2022 @01:20PM (#29895416)
This has become enough of a problem that Google is working on decoupling the "system" version of Chrome (used for login window, settings, etc) from the browser that users interact with directly on Chrome OS, making it so you can keep using the device safely after its EOL date (which is 6 or 8 years now I think).

Here[0] is a little documentation about it, but if you want to use the decoupled browser, it looks like you can enable it via chrome://flags if you are on a recent version (which OP's mom isn't, and since her device isn't going to get patched I doubt she'll benefit from this).

0: https://chromium.googlesource.com/chromium/src.git/+/refs/he...

Re:The optional chaining operator, “modern” browsers, and my... by krony on Tuesday January 11, 2022 @01:41PM (#29895745)
Reminds me of how we bought a Chromebook in 2016, and specifically got a version that was "planned" to be allowed to run Android apps (which was a new thing at the time).

Fast forward to 2022, and the ASUS C201 support for Android is still "planned" and unsupported. https://www.chromium.org/chromium-os/chrome-os-systems-suppo...

Feels like a big con just to get people to buy chromebooks in 2016 at this point.

Also, a reminder to not trust Google if they "plan" something like the upcoming Chrome "Lacros" decoupling

Re:The optional chaining operator, “modern” browsers, and my... by y4mi on Tuesday January 11, 2022 @02:02PM (#29896097)
my acer chromebook from 2015 got support.

i dont think the fault is entirely with google here, asus shouldn't have marketed it as that, considering your chromebook had an arm processor - great for battery life, but google really only implemented the docker/shell and android support for intel cpus.

really unfortunate though

Re:The optional chaining operator, “modern” browsers, and my... by notreallyserio on Tuesday January 11, 2022 @02:16PM (#29896308)
Ironically, most Android apps are built for arm processors.
Re:The optional chaining operator, “modern” browsers, and my... by y4mi on Tuesday January 11, 2022 @03:02PM (#29897015)
I think the Chromebooks Android support is more like the virtual devices that Android studio creates then actual native installs.

It's been quiet long since I've last I checked it out, but at least at that time the locale was different inside the android apps vs chromeos (including keyboard layout etc) and there was a separate settings app like on any Android devices with dummy values in hardware etc.

It was funny because it let me install Firefox on the Chromebook but it felt more like gimmick then an actually useful feature as a lot of apps just outright didn't work

Re:The optional chaining operator, “modern” browsers, and my... by pmlnr on Tuesday January 11, 2022 @04:46PM (#29898492)
Most android apps are java. They should be built for jvms. The fact that we have java jars that fail because of hardware architecture invalidates java as an idea to me.
Re:The optional chaining operator, “modern” browsers, and my... by zingplex on Tuesday January 11, 2022 @07:33PM (#29900611)
I don't think Android uses a JVM. Android apps are AOT compiled from DEX bytecode.
Re:The optional chaining operator, “modern” browsers, and my... by smrtinsert on Tuesday January 11, 2022 @05:48PM (#29899466)
I have very little faith in their big picture.
Re:The optional chaining operator, “modern” browsers, and my... by captn3m0 on Tuesday January 11, 2022 @01:26PM (#29895512)
This sounds like the same problem that manifested with Android and resulted in Treble.
Re:The optional chaining operator, “modern” browsers, and my... by jrochkind1 on Tuesday January 11, 2022 @02:38PM (#29896671)
This was an eye-opener for me too.

As a web dev, I had been thinking "there's no reason anyone would be running anything but the latest version of Chrome" -- but here's a reason.

Should we be trying to support old versions of Chrome? The author thinks so.

> This is a problem with the people who make that website. They should be making their website’s code more accessible to legacy devices.

I'm not sure how likely that is to happen. Where do we draw the line? Most tools oriented towards helping you do legacy browser support (like caniuse) don't even have UI's oriented toward helping you figure out what version of Chrome is when and where a good line to draw might be. (At what point would the OP author think we could stop transpiling down to ES5? Literally never?)

Just cause I'm curious... Version 76 is what his mom's chromebook had. When did that come out? Looks like July 20 2019. So about 2.5 years ago.

But this does make me re-think what appropriate browser support policy should be... mostly I just have questions not answers though.

The author was so clear that it was the websites fault and they should be supporting this 2.5 year-old Chrome... I'm curious what other HN readers are doing, is anyone testing on or making sure to support this kind of old "evergreen" browsers, and if so how?

Re:The optional chaining operator, “modern” browsers, and my... by jimminy on Tuesday January 11, 2022 @03:21PM (#29897270)
As someone who started doing web development in 2003-2004, I've always aimed for a 5 year support window. This is largely because of how long IE6-IE8 upgrades took for many SMB's and governments to upgrade from in those days.

Back then browsers updated closer to 2-4 times a year, with far lower inertia in how drastic the changes would be. You could learn and mostly remember what features were safe for roughly that period. These days, I tend to look at feature release dates and support on CanIUse or MDN, to see if somethings been in broad use for the past 4-5 years.

Re:The optional chaining operator, “modern” browsers, and my... by jrochkind1 on Tuesday January 11, 2022 @04:04PM (#29897852)
Thanks for response! So are you looking at Chrome (and Firefox) back to 4-5 years past (via caniuse?), and not using something if they don't support it back that far?

(at least ES6 is, generally, in all current browsers (not IE) as of more than 4 years back at this point. But are you delivering ES6 to browsers, or still limiting yourself to ES5?)

Re:The optional chaining operator, “modern” browsers, and my... by zdunn on Tuesday January 11, 2022 @04:48PM (#29898519)
> So are you looking at Chrome (and Firefox) back to 4-5 years past (via caniuse?), and not using something if they don't support it back that far?

I don't think that's whats the author meant, since they mentioned progressive enhancement. The site in question was for making a reservation to volunteer. This could have been written as a simple HTML form and it would have worked on any version of Chrome/Firefox/Safari and most other browsers. Any dynamic feature the site authors wanted to add should have used [feature detection](https://developer.mozilla.org/en-US/docs/Learn/Tools_and_tes...).

You can also use JS modules and `nomodule` script tags to deliver the latest and greatest JS to modern browsers and a compiled ES5 script to older browsers (though that wouldn't work in the case of an older evergreen browser that does support modules)

Re:The optional chaining operator, “modern” browsers, and my... by jimminy on Tuesday January 11, 2022 @06:12PM (#29899781)
These days I look up individual features, and use the date-relative view, to assess how long it's been available. Normally I'll start porting features once they're solid across the main browser set, but with a polyfill or some alternative based on feature detection.

I held off on delivering ES6 native until 2017-2018, and used mainly Bable or sometimes hand written polys up to that point if I wanted to use features from cutting edge. There's some influence from your user-agent analytics as well to determine if there is a meaningful regression to leave people behind.

5 years is just the rough grasp, sometimes the new features are worth integrating sooner if they provide actual functional improvements for users. Generally, syntactic sugar is given less precedence especially when it would negatively impact usability of the product. Saving a few hours for development is far less valuable than saving even a few hundreds of users hours of frustration.

Re:The optional chaining operator, “modern” browsers, and my... by dmitriid on Tuesday January 11, 2022 @05:43PM (#29899393)
> As a web dev, I had been thinking "there's no reason anyone would be running anything but the latest version of Chrome" -- but here's a reason.

And this way of thinking is increasingly a huge problem, as the web becomes not just Chrome-only, but latest-version-of-Chrome-only

> I'm curious what other HN readers are doing, is anyone testing on or making sure to support this kind of old "evergreen" browsers, and if so how?

You'll find both ends of the spectrum on HN. From "we must absolutely have all the latest and greates from Chrome shipped in all other browsers as possible" to "if it's newer than 5-7 years, for the love of god transpile and polyfill it".

I'm more in the second camp. There are several reasons for that:

1. At a previous gig at a large company three years ago IE 11 brought us up to 4 million views a month. While not directly convertible to users, it's still the size of a small country

2. The world in general doesn't run on the latest Chrome. You have a huge amount of devices across the world, and not all of them will be the latest Macbooks Mx or Galaxy/Pixel <whatever the latest version number is>.

Just for Android you'll find that more than half of your users (depending on your target audience) may be running software that's three years and more older: https://www.androidpolice.com/googles-latest-android-version...

Samsung Internet and UC Browser which are very weird versions many versions behind and sideways from mainstream browser engines may be anywhere from ~7% to 50-60% once again depending on your target audience.

Re:The optional chaining operator, “modern” browsers, and my... by jrochkind1 on Tuesday January 11, 2022 @07:02PM (#29900320)
Is someone using a three-year-old Android OS... using a three-year-old version of chrome? Or can an old version of Android still be using a more recent Chrome? I don't actually know how it works!
Re:The optional chaining operator, “modern” browsers, and my... by dmitriid on Wednesday January 12, 2022 @02:31AM (#29903427)
Many Androids stop receiving updates after just two years. I don't know if it affects the browser :)

However, there are also many users who don't update either the OS or the apps (because they don't know what it is, afraid it will break, afraid it will change functionality etc. )

Re:The optional chaining operator, “modern” browsers, and my... by nelgaard on Tuesday January 11, 2022 @08:35PM (#29901194)
It is a trade off. How much did they really gain by using ?.

A year ago I helped a small company with some issues. One was that some people working with them had some problems using their app with older phones. After some investigation it turned out that I just had to replace "let " with "var " on a few lines of javascript code.

I used an an Iphone 4S for the testing and the browser could not be updated.

I you make something that could work on older devices and it is not too much trouble, you should make it work on those devices.

I have a drawer full of old devices that I use for all kinds of things (besides testing) where it is not a big deal that the software cannot be updated.

I do have an old chromebook. It runs Debian sid and has updated browsers.

Re:The optional chaining operator, “modern” browsers, and my... by sangnoir on Tuesday January 11, 2022 @10:28PM (#29901925)
We can stop transpiling to ES5 when a long enough time-window (one you're comfortable with) has elapsed since the last ES5-only browser was released and hopefully your users have upgraded. Additionally, you can check the User-agents in your access logs (or analytics) to see what fraction of your users are still on ES5 browsers.

I think once you've correctly configured your CI transpiler, you wont even have to think about it, so it's a small price to pay, IMO.

Re:The optional chaining operator, “modern” browsers, and my... by sangnoir on Tuesday January 11, 2022 @10:26PM (#29901910)
We can stop transpiling to ES5 when a (window youre comfortable with) has elapsed since the last ES5-only browser was released and hopefully your users have upgraded. Additionally, you can check the User agents in your access logs (or analytics) to see what fraction od your users are still on ES5 browsers I think once you've correctly configured your CI transpiler, you wont even have to think about it, so it's a small cost, IMO.
Re:The optional chaining operator, “modern” browsers, and my... by modeless on Tuesday January 11, 2022 @12:51PM (#29894939)
iOS also doesn't allow the browser to be updated after the hardware has reached end-of-support. In general, Chrome OS devices have 6-8 years of support, while iOS seems to have ~7.

But in the case of Chrome OS this is likely to be fixed soon because Chrome is getting unbundled from Chrome OS, meaning it can be updated separately. This is codenamed Lacros and is in testing now. Devices currently receiving updates are likely to get it. https://www.androidpolice.com/2020/09/12/google-is-separatin...

Also, Chrome OS devices explicitly support unlocking and installing alternative OSes. If you don't like what Google does with Chrome OS you can install Linux or Windows instead and keep using your hardware as long as you like.

Re:The optional chaining operator, “modern” browsers, and my... by core-utility on Tuesday January 11, 2022 @01:31PM (#29895587)
Phones are a bit more of a commodity than laptops/desktops are, I think primarily because of the strong evolution you see in comparison over the same timeframe. A laptop from 7-8 years ago largely still is capable of running the latest software (and most of the time Operating Systems), while an 8 year old phone hardly has the performance to do either with the advancements that have been made.
Re:The optional chaining operator, “modern” browsers, and my... by fartcannon on Tuesday January 11, 2022 @02:27PM (#29896499)
You only think that because that's what we've let transpire. It's a disgrace that I can not use my iPhone or Android phone to easily create new software, only consume. They're more than powerful enough to fully replace most computer usage including software development. But no, we've let them normalize locking the OS, and hiding the file system. Its an absolute disgrace.
Re:The optional chaining operator, “modern” browsers, and my... by skinnymuch on Tuesday January 18, 2022 @09:50PM (#29989328)
Hah I so strongly disagree with your Phil Xbox take. But am nodding along agreeing with a lot of your recent comments. This one especially.

It is absolutely a disgrace. Not even specifically to create software. Not allowing root, the ways of the app stores, the entire UX. It all focuses on consumption and weak workflow. A 13 inch iPad could very easily be a dedicated developer device (and some do get by this way), but it’s such a pain.

Re:The optional chaining operator, “modern” browsers, and my... by eptcyka on Tuesday January 11, 2022 @04:29PM (#29898233)
Locking the filesystem doesn't necessarily mean developing with them is impossible. What is preventing IDEs from working is the inability to execute unsigned binaries combined with the absence of signing binaries locally. And I agree, I too see this as an invitation to fornicate myself, a personal invitiation signed by google and Apple no less.
Re:The optional chaining operator, “modern” browsers, and my... by loosescrews on Tuesday January 11, 2022 @01:44PM (#29895785)
Note that the average price of an iPhone is higher than the average price of a Chromebook.
Re:The optional chaining operator, “modern” browsers, and my... by heleninboodler on Tuesday January 11, 2022 @02:44PM (#29896749)
iPads and phones are different beasts, though. I personally have much lower expectations of my ipad, and one of those fairly low expectations is that the browser should continue working (with the implied, "and be safe to use" that requires security updates) for as long as the device doesn't physically break.

I get that Apple can't be expected to keep developing software for these forever, but I'd be a lot happier if they would transition them to some kind of minimal support where they publish routine OS and security updates for them rather than just abandoning them. They also have this habit of ratcheting up the OS targeting requirements of the SDKs so app builders end up unwittingly building new versions of their apps that exclude old devices unnecessarily. I'm not sure my oldest ipad could install any of its apps again if I uninstalled them, even the ones from Apple.

Re:The optional chaining operator, “modern” browsers, and my... by ryandrake on Tuesday January 11, 2022 @05:46PM (#29899435)
As someone who still has (and uses, offline) his original iPad, I can tell you the App Store is now a barren wasteland on that device. Nobody's app runs on it anymore! So don't delete anything.

It's a disgrace that while hardware is starting to vastly outlast software, somehow we have managed to normalize 2-3 years of software support for hardware gizmos and consider 5 years to be generous. And consumers accept this! 5 years is nothing. I have a PC next to me that I bought 20 years ago, and it still works excellently and runs a relatively recent version of Linux. I last updated my phone only because I had to: It was so "old" that it was dangerous to even connect to the Internet. Still worked wonderfully, made calls, but the manufacturer abandoned it (and me) and stopped supplying security updates. So a perfectly functional phone goes into a landfill. This should be totally unacceptable.

Re:The optional chaining operator, “modern” browsers, and my... by _trampeltier on Tuesday January 11, 2022 @01:40PM (#29895719)
I also bought a new phone for my mom just because, the latest android update was 2017 and some apps did not work any longer, so we bought a new phone. The phone was still in a pretty good shape and the battery too. She just used here phone very rarely.
Re:The optional chaining operator, “modern” browsers, and my... by GloriousKoji on Tuesday January 11, 2022 @03:24PM (#29897308)
> Also, Chrome OS devices explicitly support unlocking and installing alternative OSes.

Not anymore they don't. I recently bought a chromebook hoping to nuke it and install Linux but the bootloader is locked and I can't install any random OS. There's even dedicated linux distros like Gallium OS targeting chromebook devices specifically but if you look at the compatibility chart it's support is very limited for anything newer than 2018. Even crouton compatibility wasn't satisfactory and I gave up and just went full google approved with Crostini.

Re:The optional chaining operator, “modern” browsers, and my... by TheDong on Tuesday January 11, 2022 @04:06PM (#29897891)
> Not anymore they don't. I recently bought a chromebook .. but the bootloader is locked

Every ChromeOS device I know of supports developer mode, and I was fairly sure google mandated it. Which device do you have which does not support developer mode?

Re:The optional chaining operator, “modern” browsers, and my... by GloriousKoji on Tuesday January 11, 2022 @07:08PM (#29900379)
Acer 311 but any chromebook with an Intel Gemini Lake processor has a locked bootloader and bios. Developer Mode can be enabled but the most that gets is installing crouton which is still beholden to booting Chrome OS and using it's kernel.
Re:The optional chaining operator, “modern” browsers, and my... by TheDong on Tuesday January 11, 2022 @10:10PM (#29901804)
Oh, huh, indeed that seems to be more involved than just developer mode.

That one supports CCD, so you can still "root" it, but instead of just enabling developer mode, you also have to connect a cable and go through a slightly more involved process.

Fortunately, it's quite well documented: https://chromium.googlesource.com/chromiumos/platform/ec/+/c...

It's still not fully locked since following the above doc should let you flash your own firmware

Re:The optional chaining operator, “modern” browsers, and my... by modeless on Tuesday January 11, 2022 @04:11PM (#29897965)
You can't enable developer mode? What Chromebook is that?
Re:The optional chaining operator, “modern” browsers, and my... by null_object on Tuesday January 11, 2022 @01:51PM (#29895910)
> iOS also doesn't allow the browser to be updated after the hardware has reached end-of-support.

Just simply not true. Plenty of browsers are still updated for iOS12 and 8-year old hardware like the 2013 iPad Air (which I still use every day)

Edit: getting downvoted - while writing this post on iCab Mobile browser which was updated less than a month ago...

Follow-up: Well I tested the language ‘feature’ in this browser - and though it didn’t crash, it didn’t run the function either. I’d forgotten what a sh*tshow of crappy and unnecessary garbage modern front end JavaScript development was.

Re:The optional chaining operator, “modern” browsers, and my... by modeless on Tuesday January 11, 2022 @01:55PM (#29895958)
Apple has fooled you. Those aren't complete browsers. Those are simply UI shells around the system version of WebKit which cannot be updated or bypassed or replaced. No new web platform features will be added, no bugs fixed, and security holes are not guaranteed to be addressed.
Re:The optional chaining operator, “modern” browsers, and my... by heresaPizza on Tuesday January 11, 2022 @02:18PM (#29896350)
While what you said is true, iOS 12 still received some security fixes, so the total support for the iphone 5s is 9 years and 8 for the 6. Critical bugs shouldn’t be that big of a threat (considering that even up to date phones are colanders.
Re:The optional chaining operator, “modern” browsers, and my... by ksec on Tuesday January 11, 2022 @03:42PM (#29897544)
>Edit: getting downvoted

You are getting downvoted because Webkit Engine is not updated with the browser. In this case iCab Mobile Browser. As noted in other reply it is merely a shell or skin on top of the OS Webkit Engine. Hence you are objectively wrong.

Re:The optional chaining operator, “modern” browsers, and my... by mcguire on Tuesday January 11, 2022 @04:09PM (#29897931)
Technically, I downvoted because

"I’d forgotten what a shtshow of crappy and unnecessary garbage modern front end JavaScript development was.*"

while essentially true, has nothing to do with the question at hand.

Re:The optional chaining operator, “modern” browsers, and my... by rekoil on Tuesday January 11, 2022 @01:46PM (#29895842)
What happened in this article reinforces my belief that devices marketed as "general purpose" devices _must_ allow users to, in some way, run their own software on them "unrestricted" (standard sandboxing of course, mostly the same rules as App Store apps, just none of the application class rules or arbitrary API access restrictions).

In the case of ChromeOS they do allow you to install Linux which satisfies this on paper (and to me, but perhaps not everyone?), however the iPad does not allow this in any way (the App Store, as pointed out by the author, explicitly disallows browsers), and I think there needs to be regulations on makers of devices that are classed as "general purpose computing devices".

Re:The optional chaining operator, “modern” browsers, and my... by erichocean on Tuesday January 11, 2022 @01:47PM (#29895860)
You can install your own browser on your own iOS device, you simply can't distribute it through the App Store.
Re:The optional chaining operator, “modern” browsers, and my... by rekoil on Tuesday January 11, 2022 @01:51PM (#29895922)
Not really, you can only do that for 7 days at a time, unless each device owner pays $99 yearly, and even then there's no simple and obvious way to do it.
Re:The optional chaining operator, “modern” browsers, and my... by LinAGKar on Tuesday January 11, 2022 @01:52PM (#29895935)
No you can't (unless you jailbreak)
[dead]
Re:The optional chaining operator, “modern” browsers, and my... by rekoil on Tuesday January 11, 2022 @01:57PM (#29896001)
> you can install one of the numerous alternative browsers that are available and updated for iOS 12

Those "browsers" are more like skins, they can't actually modify how websites are rendered or how JavaScript is executed. So no, the article is correct, you can't install actual browsers from the App Store.

Fun fact: Because of this fact, for a brief moment in history Google actually purposefully caused Google Chrome on iOS to crash when they detected that JavaScript on a site was attempting to perform a uXSS attack[1], because they couldn't actually stop the attack since that would require modifying WebKit.

[1]: https://bugs.chromium.org/p/chromium/issues/detail?id=841105

Re:The optional chaining operator, “modern” browsers, and my... by LinAGKar on Tuesday January 11, 2022 @02:36PM (#29896638)
Show me an iOS browser that's not just a Safari reskin
Re:The optional chaining operator, “modern” browsers, and my... by null_object on Tuesday January 11, 2022 @01:53PM (#29895943)
> You can install your own browser on your own iOS device, you simply can't distribute it through the App Store.

Or you can use one of the plentiful choices of browser that are distributed on the App Store and still updated for iOS 12.

Re:The optional chaining operator, “modern” browsers, and my... by rekoil on Tuesday January 11, 2022 @01:55PM (#29895962)
All of which run WebKit under the hood and can not implement support for optional-chaining on their own as that is a JavaScript engine thing which they can't touch.
Re:The optional chaining operator, “modern” browsers, and my... by umvi on Tuesday January 11, 2022 @01:36PM (#29895657)
When my ChromeOS reached EoL, I installed GalliumOS (https://galliumos.org/) onto my chromebook. Works like a charm.
Re:The optional chaining operator, “modern” browsers, and my... by judge2020 on Tuesday January 11, 2022 @12:50PM (#29894925)
This is generally because ChromeOS isn't just an OS based on Chrome - Chrome itself is the OS, supported by how the OS portion is just a folder in the chromium/src tree[0].

Edit: looks like there's now an effort to separate them, as the readme says. see [1].

0: https://chromium.googlesource.com/chromium/src/+/refs/heads/...

1: https://chromium.googlesource.com/chromium/src.git/+/refs/he...

Re:The optional chaining operator, “modern” browsers, and my... by ocdtrekkie on Tuesday January 11, 2022 @12:58PM (#29895068)
The irony here is that the best way to buy a device for Chrome is to buy a Windows laptop and install Chrome on it... Google will support it far longer than they'll support their own products.

Chrome support for Windows 7 has been extended into 2023, which is an OS released in 2009.

Re:The optional chaining operator, “modern” browsers, and my... by tragictrash on Tuesday January 11, 2022 @12:53PM (#29894975)
It looks like this has been identified as a problem and is being addressed. It's interesting to see that it has not been fully implemented.

https://9to5google.com/2020/09/14/google-chrome-os-separate-...

> Update 9/14: After nearly five months, LaCrOS has surfaced in a working state on Chrome OS Canary, as spotted by Chrome Unboxed. By enabling the above-mentioned flag in chrome://flags, a new “LaCrOS” app will appear in your app list, first in grey, then in the usual yellow of Chrome Canary.

Re:The optional chaining operator, “modern” browsers, and my... by mc32 on Tuesday January 11, 2022 @12:46PM (#29894858)
It’s odd that today Google (in this case) but others as well, can get away with more than Microsoft did in the late ‘90s but the DoJ doesn’t make a peep.
Re:The optional chaining operator, “modern” browsers, and my... by coldtea on Tuesday January 11, 2022 @12:57PM (#29895062)
Well, in this case they don't get away with anything of the same nature.

Microsoft: abuse market monopoly status () to force and scare OEMs into special bundling deals (*).

() Chrome OS, iOS: not monopoly status - "monopoly for this brand+device" doesn't count, unless the device has the monopoly of its market. Microsoft had aroun 98% of the desktop

(*) Google, Apple: don't do that. And even if they did it, they're not monopolies in laptops/tablets, so they could just as well did it, and it wouldn't be the same legally as what MS did.

Re:The optional chaining operator, “modern” browsers, and my... by emodendroket on Tuesday January 11, 2022 @01:01PM (#29895123)
How meaningful is the distinction, honestly? What are you going to do, buy the tablet that's totally open? Is there one?
Re:The optional chaining operator, “modern” browsers, and my... by powersnail on Tuesday January 11, 2022 @01:48PM (#29895866)
It's a fairly meaningful distinction in the context of grandparent comment which talks about DOJ not pursuing Google/Apple for this specific fault, since the Microsoft case was one about abusing their monopoly position.
Re:The optional chaining operator, “modern” browsers, and my... by emodendroket on Wednesday January 12, 2022 @01:03AM (#29902907)
Sure, it's more that I think antitrust is not really that meaningful a remedy.
Re:The optional chaining operator, “modern” browsers, and my... by jimbokun on Tuesday January 11, 2022 @01:14PM (#29895310)
I don't think "totally open" is an enforceable legal concept, so what do you expect the courts to do to fix this problem?

Anti-trust law is long standing with lots of precedent to work off of, so it had a natural application to the Microsoft case.

Re:The optional chaining operator, “modern” browsers, and my... by newhotelowner on Tuesday January 11, 2022 @01:28PM (#29895540)
Tablet market - One could argue that apple has monopoly in the tablet market, and you can't install any other browser.
Re:The optional chaining operator, “modern” browsers, and my... by coldtea on Tuesday January 11, 2022 @02:26PM (#29896479)
>One could argue that apple has monopoly in the tablet market

They could argue it, but they would be factually wrong. Apple doesn't even sell half the tablets sold every year...

Re:The optional chaining operator, “modern” browsers, and my... by null_object on Tuesday January 11, 2022 @01:43PM (#29895774)
> and you can't install any other browser.

This is totally incorrect. There are a large number of alternatives.

I still use an 8 year old iPad every day, and have an updated version of iCab Mobile running on it, which has given me no problems whatsoever. I’ve certainly never experienced a website that won’t load, despite the age of the hardware.

Re:The optional chaining operator, “modern” browsers, and my... by Shared404 on Tuesday January 11, 2022 @04:46PM (#29898490)
This is like the fifth comment like this I've seen you make in this section.

It is completely false, as noted in replies all over, could you please chill with the spam?

Re:The optional chaining operator, “modern” browsers, and my... by LinAGKar on Tuesday January 11, 2022 @01:56PM (#29895992)
That's not a different browser, that's just a Safari reskin.
Re:The optional chaining operator, “modern” browsers, and my... by otherotherchris on Tuesday January 11, 2022 @12:55PM (#29895016)
ChromeOS currently has a 3% market share. Microsoft had 95% during the end of the Clinton administration.

Google's consumer hostile behavior is kneecapping any chance they have at future market dominance, it's entirely self correcting.

Re:The optional chaining operator, “modern” browsers, and my... by mc32 on Tuesday January 11, 2022 @01:09PM (#29895242)
Much of the case rested on how tightly the browser was woven into Windows —that MS was preventing competition in the browser space (via the strong arming tactics) but the “bad thing” they did was the tight browser integration.
Re:The optional chaining operator, “modern” browsers, and my... by mason55 on Tuesday January 11, 2022 @01:19PM (#29895395)
> the “bad thing” they did was the tight browser integration.

It's true, but it was only "bad" in the eyes of the law because of their monopoly. If Microsoft hadn't had a monopoly then their strong arm tactics would have been fine. No one would care if I went to Dell and said "you can only sell computers with my OS on them if you also include my browser."

In the US you can be anti-competitive if you don't have a monopoly and you can have a monopoly as long as you don't engage in anti-competitive behavior. It's only when you have a monopoly AND engage in anti-competitive behavior that you get in trouble.

Re:The optional chaining operator, “modern” browsers, and my... by jimbokun on Tuesday January 11, 2022 @01:16PM (#29895350)
That was only an issue because it was used as a deliberate tactic to prevent Netscape Navigator from competing with Internet Explorer. Which was challenged because of Microsoft's monopoly position.

Tight browser integration was not illegal in and of itself.

Re:The optional chaining operator, “modern” browsers, and my... by santoshalper on Tuesday January 11, 2022 @01:04PM (#29895170)
I hope you're right. It feels like Google has an awful lot of power over the future of the internet a the moment.
Re:The optional chaining operator, “modern” browsers, and my... by jimbokun on Tuesday January 11, 2022 @01:18PM (#29895382)
Yes, but ChromeOS is a relatively minor part of that power.

Controlling search, Android, Chrome as the dominant browser, and YouTube are much bigger parts of their power over the Internet than ChromeOS.

Re:The optional chaining operator, “modern” browsers, and my... by opan on Tuesday January 11, 2022 @01:57PM (#29896015)
ChromeOS also appears heavily at school where kids are now growing up being forced to use it. (Not going for a "think of the children" thing, more like imprinting)

I think there's a Google Classroom thing as well.

Re:The optional chaining operator, “modern” browsers, and my... by veeti on Tuesday January 11, 2022 @02:16PM (#29896298)
A similar thing happened with the Let's Encrypt root certificate expiration a couple months back. Because trusted certificates can't be updated on EOL devices, otherwise perfectly functional websites and apps just stopped working overnight. What a waste.
Re:The optional chaining operator, “modern” browsers, and my... by rekoil on Tuesday January 11, 2022 @02:39PM (#29896685)
I think you can install root certificates on iOS using .mobileconfig profiles, so this issue should be possible to fix.
Re:The optional chaining operator, “modern” browsers, and my... by spankalee on Tuesday January 11, 2022 @01:21PM (#29895433)
ChromeOS is addressing this with LaCros - a separately installable version of Chrome that runs on top of ChromeOS. The goal being exactly to be able to update Chrome when the underlying ChromeOS can't be updated.

https://www.slashgear.com/chrome-os-to-replace-chrome-with-l...

Re:The optional chaining operator, “modern” browsers, and my... by LocalPCGuy on Tuesday January 11, 2022 @01:13PM (#29895294)
This right here - was about to recommend a ChromeOS device for my father-in-law but this gives me significant pause.
Re:The optional chaining operator, “modern” browsers, and my... by opan on Tuesday January 11, 2022 @01:58PM (#29896028)
Maybe consider a Pinebook Pro instead, depending on needs. It's in a similar class, but without being locked down.
Re:The optional chaining operator, “modern” browsers, and my... by jrochkind1 on Tuesday January 11, 2022 @02:35PM (#29896621)
Interesting machine!

"Due to global electronic components shortage , Pinebook Pro currently out of stock until further notice."

Re:The optional chaining operator, “modern” browsers, and my... by phil294 on Tuesday January 11, 2022 @01:13PM (#29895292)
Same thing with Android - while you can certainly still upgrade your apps, your OS won't, as most manufacturers want you to buy a new phone after a certain period of time (2 years, usually). I really hope to see an EU regulation to put an end to this consumer-hostile behavior some day.
Re:The optional chaining operator, “modern” browsers, and my... by tmvnty on Tuesday January 11, 2022 @03:26PM (#29897339)
This was the exact issue with my parent:

Chrome wasn't updating because their out-of-dated hardware and I had to tell them switch to Firefox "the red fox on globe icon" to use the internet.

This lasted until the day I finally convinced them to buy a new PC.

Re:The optional chaining operator, “modern” browsers, and my... by sokoloff on Tuesday January 11, 2022 @12:38PM (#29894720)
To me, that depends on the length of support for ChromeOS on a piece of hardware. If it’s say 10 years in total and 7 years from date of last sale-as-new, I’m okay with it.
Re:The optional chaining operator, “modern” browsers, and my... by johannes1234321 on Tuesday January 11, 2022 @01:08PM (#29895221)
The really important part imo: We need labelling of products that way. Nowadays "everything" is connected to the internet and I as a consumer have no chance to predict how long I will be able to use a product. The vendor has to give a guarantee and put it in a box (and probably get an insurance so they can't simply close one company and continue under a new name every other week ...)
Re:The optional chaining operator, “modern” browsers, and my... by markstos on Tuesday January 11, 2022 @12:45PM (#29894841)
ChromeOS used support laptops for 5 to 6 years, while now it's 8 years. Meanwhile, the average lifespan of a laptop is 8 years.

  https://www.androidpolice.com/2020/02/07/chromebooks-will-now-get-up-to-eight-years-of-chrome-os-updates/
  https://www.google.com/search?hl=en&q=average%20laptop%20lifespan
Re:The optional chaining operator, “modern” browsers, and my... by sokoloff on Tuesday January 11, 2022 @12:48PM (#29894893)
While I’d like ten, eight is probably good enough for me. I just bought a new Chromebook for $92 all-in (low-end, obviously). At around $1/mo for the length of OS support, that seems fair enough to me. Even $4-5/mo for a nice one would be OK for most people.
Re:The optional chaining operator, “modern” browsers, and my... by ErikCorry on Tuesday January 11, 2022 @12:59PM (#29895090)
It's perhaps eight from when the Chromebook was launched, not from when you bought it at a fire-sale price. Check here: https://support.google.com/chrome/a/answer/6220366?hl=en#zip...
Re:The optional chaining operator, “modern” browsers, and my... by sokoloff on Tuesday January 11, 2022 @01:46PM (#29895828)
Thanks for the pointer to that, which prompted me to go look in Settings:About Chrome OS:Additional Details where retail Chromebooks list their end of automatic updates date. For my device, it's June 2026, so a little under $2/mo for the utility is still well worth it and hard to complain about on a value-for-money basis, but half as much as I thought I was buying, so I agree with a sibling post that that information should be much more readily available to consumers prior to purchase.
Re:The optional chaining operator, “modern” browsers, and my... by ErikCorry on Wednesday January 12, 2022 @07:09AM (#29905268)
That's a very good price for a 2026 Chromebook - lets hope Google gets their shit together and extends the life beyond what is promised.
Re:The optional chaining operator, “modern” browsers, and my... by pdonis on Tuesday January 11, 2022 @04:58PM (#29898669)
Looks like my instinct to avoid Chromebooks like the plague was a good one...
Re:The optional chaining operator, “modern” browsers, and my... by autokad on Tuesday January 11, 2022 @01:15PM (#29895339)
I know, the author was completely wrong. While the web dev did a mistake, it was not as egregious as the manufacturers locking his mom into a corner.
Re:The optional chaining operator, “modern” browsers, and my... by theandrewbailey on Tuesday January 11, 2022 @01:25PM (#29895497)
The dev made a mistake by having a Javascript error totally break the site. Websites should still be functional (even if a bit inconvenient) without Javascript.
Re:The optional chaining operator, “modern” browsers, and my... by vlunkr on Tuesday January 11, 2022 @01:56PM (#29895975)
> Websites should still be functional (even if a bit inconvenient) without Javascript.

I don't see why it needs to go that far. They could have just not used the optional chaining operator, or used a pre-processor if they really wanted to use it.

Very few people are browsing with no JS at all, and they are doing it deliberately. They probably disagree with me, but I don't think anyone should do extra work for them.

Re:The optional chaining operator, “modern” browsers, and my... by berdario on Tuesday January 11, 2022 @03:38PM (#29897498)
It's not about choosing to be

> browsing with no JS at all,

It's about building a reliable product. I've witnessed tons of cases of websites broken due to Javascript. Sometimes they were broken in Firefox, other times they were broken only in some locales...

Often they were not broken forever, a bad release got pushed, and it took some times for the problems to be identified and addressed... but in the meanwhile, a specific part of their website was broken 100% of the time.

If you're building the new Google Maps, sure... knock yourself out with the fanciest Javascript you can find (but even then, I'd set a restrictive CSP, to avoid other script from interfering, and I'd pick something like Elm to make sure that runtime errors are minimized). But if you're building anything else, you should really try to keep it simple (even Gmail still has its plain HTML version)

Re:The optional chaining operator, “modern” browsers, and my... by zdunn on Tuesday January 11, 2022 @04:53PM (#29898592)
It's not extra work. The site in question was for making a reservation. A basic HTML for would have satisfied that requirement and worked completely without javascript. Any additional features could have been built with javascript and the site would be no different to users on modern browsers as the current build, but it would still work on the author's mom's browser.

Progressive enhancement isn't about building sites completely without JS. It's about building resilient sites that work on edge cases like this.

Re:The optional chaining operator, “modern” browsers, and my... by jw14 on Tuesday January 11, 2022 @10:04PM (#29901771)
It is absolutely extra work. You have to test every mode of operation. So to support those with JS disabled (about 1.3% of users according to some quick searches) you have to test with JS disabled. Then you have to test again to make sure your JS workflow is stable.

Every business has to make the choice, but unless I was running a pretty large operation, I'd be willing to ignore 1.3% to put my budget into other things.

Re:The optional chaining operator, “modern” browsers, and my... by pier25 on Tuesday January 11, 2022 @03:34PM (#29897438)
Exactly.

The cost to make a website accessible to everyone is so high that it really only makes sense for critical websites.

Re:The optional chaining operator, “modern” browsers, and my... by bmeski on Tuesday January 11, 2022 @03:48PM (#29897623)
It’s really not if you simply stick to html, css, and a tiny bit of js on the client.
Re:The optional chaining operator, “modern” browsers, and my... by pier25 on Tuesday January 11, 2022 @08:06PM (#29900966)
Unfortunately that approach doesn't work for many (most?) use cases.
Re:The optional chaining operator, “modern” browsers, and my... by bmeski on Tuesday January 11, 2022 @08:23PM (#29901119)
What?

They are literally the 3 client “languages” of the web.

Everything your abstractions/frameworks do is produce html, css, and js.

Re:The optional chaining operator, “modern” browsers, and my... by pier25 on Tuesday January 11, 2022 @10:17PM (#29901855)
What does that even mean?
Re:The optional chaining operator, “modern” browsers, and my... by autokad on Tuesday January 11, 2022 @01:30PM (#29895575)
No. Stop defending bad practice. its conceivable there are new functions that are not backwards compatible. At some point you need to be able to update your browser. its the fact she is locked out from doing that is what puts her in the pickle. Google and Apple made sure she can't get a new browser so that she would purchase a new device. period.
Re:The optional chaining operator, “modern” browsers, and my... by neon_electro on Tuesday January 11, 2022 @01:38PM (#29895691)
Arguing that websites should support the least common denominator of functionality and then progressively enhance for modern functionality is not simultaneously defending corporations' planned obsolescence. Both problems can be solved independently.
Re:The optional chaining operator, “modern” browsers, and my... by null_object on Tuesday January 11, 2022 @01:45PM (#29895810)
> Apple made sure she can't get a new browser so that she would purchase a new device. period.

Just bullshit. There are plenty of browsers being updated and fully compatible with iOS 12.

Re:The optional chaining operator, “modern” browsers, and my... by LinAGKar on Tuesday January 11, 2022 @01:50PM (#29895898)
Not, there isn't, because no one else is allowed to make a browser for iOS. Any other "browser" on there is just a reskin of the built-in Safari.
Re:The optional chaining operator, “modern” browsers, and my... by autokad on Tuesday January 11, 2022 @02:04PM (#29896114)
did you even read the article?