15 ms·
The optional chaining operator, “modern” browsers, and my mom
- ZoomZoomZoom 5y agoThe most ridiculous thing with Apple is that they don't even allow installing OS updates they themselves released to devices they declare obsolete. You can't download updates since Apple no longer host them and there's no option (at least official) to sideload them even if you had the files. This is an utter disrespect for the customers no one should tolerate.
- john-doe 5y agoThe default view of caniuse.com should be “Usage relative”, not “Current aligned”
- andai 5y agoHere's the closest issue I could find: https://github.com/Fyrd/caniuse/issues/4192 https://github.com/Fyrd/caniuse/issues/4192 There's a setting to make it default in "Settings > Default display settings" but I agree it should be the default automatically. I wonder why it isn't?
- deleted 5y ago[deleted]
- john-doe 5y agoProbably to boost awareness and adoption of new technologies, with the downside of effectively boosting awareness and adoption of new technologies over other considerations, like the web backward compatibility.
- jonny_eh 5y agoHere it is for optional chaining: https://caniuse.com/?search=optional%20chaining https://caniuse.com/?search=optional%20chaining +90% of users can use it, which is probably not high enough IMO.
- munchbunny 5y agoFor end user/consumer software, 90% is nowhere near high enough. In b2b/enterprise settings you have levers to help you push that number higher through IT policy, but end users will absolutely attempt to visit your cutting edge 2022 website on the iPad 3 they've used lightly. My rule of thumb has been that if it's an app core to someone's job or life management, it needs to be functional for hardware/software going back 5-7 years, less if it's just entertainment or something.
- jonny_eh 5y agoMaybe caniuse.com should show "age of support" or something like that, to show you the newest possible device you're cutting off by using the feature.
- sundarurfriend 5y agoAlso keep in mind the limitations and biases of the CanIUse stats themselves - last I checked, their data was from StatCounter, and so based on people who visit websites that use the StatCounter service. The country-wise sample sizes [1] make the geographic biases clear - China is pretty underrepresented for example, presumably because Chinese websites don't use StatCounter as much. There may also be other kinds of biases in the data that are not so easily visible. This is not to say that the stats should be disregarded; just that like any other data source, it should be treated as one view of (some of) the data, with its own shortcomings. [1] https://gs.statcounter.com/faq#sample-size https://gs.statcounter.com/faq#sample-size
- skulk 5y ago> 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.
- sokoloff 5y agoTo 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.
- markstos 5y agoChromeOS 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
- sokoloff 5y agoWhile 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.
- ErikCorry 5y agoIt'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#zippy=%2Casus https://support.google.com/chrome/a/answer/6220366?hl=en#zip...
- 5y ago
- titanomachy 5y agoNot sure about the chromebook, but that iPad is probably ~8 years old. I have a laptop that’s older than that, and I’d be pretty annoyed if the internet was irrevocably broken on it. This is an interesting argument for general-purpose computers over specialized, user-friendly ones (iOS, chromeOS). Personally, I’d rather buy my grandma an iPad every 5 years for the rest of her life than try to teach her how to use a general-purpose computer, but that’s not a reasonable solution for everyone.
- OtomotO 5y agoI still have and occasionally use a notebook from 2007. So I totally agree
- JBiserkov 5y agoThis reminds me of a story from 2013. We were developing a web app and kept hearing about a friend of our boss who was having trouble with it in Australia. We assumed it was ping to our small server in Europe. Turns out he was using a very old version of Firefox, but that was the latest one available on his MacBook. Yes, his PowerPC MacBook.
- shuffel 5y agoMozilla cuts off support for macOS releases much too early in my opinion. I'm running macOS 10.14 Mojave which was released in 2018 and it only supports FireFox 91. The latest version of FireFox is 96. I can't find a definitive statement what minimum version of macOS is needed by the latest Firefox, but what they list on https://www.mozilla.org/en-US/firefox/96.0/system-requirements/ https://www.mozilla.org/en-US/firefox/96.0/system-requiremen... is incorrect and/or out of date: macOS 10.12. Contrast that support with Google Chrome, its latest browser works on OS X El Capitan 10.11 from 2015: https://support.google.com/chrome/a/answer/7100626?hl=en https://support.google.com/chrome/a/answer/7100626?hl=en - which is much more reasonable. EDIT: I was wrong. mrpippy pointed out in a reply below that Mojave is still supported by the latest FF release. I was using the FF ESR release which only goes up to FF version 91. Sorry for the noise, and thanks for correcting me.
- programmer_dude 5y ago> 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 don't follow the reasoning here. Why does the onus lie on the web developer and not on Google or Apple?
- akkartik 5y ago"I can’t open this website I always use to make a reservation to volunteer." Regressions are regressions. You don't get to make excuses if you unilaterally changed something for someone.
- programmer_dude 5y agoWhat's the point of releasing new language features if you can't use them? Web-developers don't deserve quality of life improvements but the developers working for Google and Apple do?
- rossipedia 5y agoYou absolutely can. The issue isn't _using_ the optional chaining operator, the issue is that it wasn't compiled down to something that older platforms can understand. Developer quality of life doesn't have to conflict with what's supported on older platforms.
- programmer_dude 5y agoSounds like a good solution to the posted problem. But the device user should be allowed to upgrade their browser and OS too.
- Bilal_io 5y agoSometimes users use older browser because of ignorance, they don't know how to upgrade, or because they don't want to.
- 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.
- assbuttbuttass 5y ago> 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. The article frames it as if the parents are naive here, but it seems like this is 100% right. Mom's chromebook and iPad not receiving updates is a perfect example of planned obsolescence.
- brk 5y agoIs it specifically planned obsolescence, or just case of technology evolving? Do you think Apple or Google, when making the decisions on browser upgrade-ability, anticipated javascript changes that would break common sites and force users to buy new hardware? To me this does not feel like planned obsolescence and feels more like a general case of "technology marches on".
- ugjka 5y agoIf only you could install some other operating system on these devices and load the latest browser or even more!
- _dain_ 5y agoIs there any technical reason why that old hardware can't run the modern browser? I severely doubt it.
- noitpmeder 5y agoIn the case of software updates it _is_ planned obsolescence. However, whether it is planned out of malice or out of cost (I imagine it costs some amount of money to continue to support old hardware) is up in the air.
- elondaits 5y agoNot even. JS developers should know to transpile their code to support users that for whatever reasons (from a long list) cannot run the latest JS version... or stick to truly standard things. The ?. operator was included in Edge, Safari, Chrome and Firefox early 2020. According to caniuse.com, only 90% of users have browsers that support it... but depending on who your audience is, it might be much less (e.g. if you target schools, or government, there might be computers locked in older OSs or browser versions... at least that's the case in my country).
- setgree 5y ago> The internet is for end users: any change made to the web platform has the potential to affect vast numbers of people, and may have a profound impact on any person’s life. Love this. I have an iPhone SE 2020, and if I had my druthers I would downgrade to an even older, smaller phone, but a lot of modern apps are just clearly meant for larger screens, and even its 4.7" screen -- SotA in 2017 -- struggles to display content properly. I'd switch to a dumb phone entirely, but alas, I'm dependent on google maps, guthooks (a hiking app), and especially ride sharing and bike sharing apps. It's a bind.
- WesolyKubeczek 5y agoThere's a reason I keep my websh-t translated by Babel so that it can be used by people with iOS 9. Those people exist, and iPad 4s are built so well that they are damn hard to kill. I'd reconsider if there was a month with no visits from Safari 9 at all.
- sovnade 5y agoCould you install a different browser on the ipad, like firefox? Is there anything preventing the latest version of firefox from installing on an old ipad?
- joshstrange 5y agoAll browsers on iOS use Webkit under the hood so they would all have these issues.
- aspyct 5y agoWe developers are responsible for preventing that kind of obsolescence, and ultimately have the power to have a sizeable impact on bigger issues like climate change, pollution or even people dying in mines. Use boring tech, people.
- deleted 5y ago[deleted]
- chungy 5y agoThe first line of the article is misleading. It's not just about a "crappy laptop", it's about locked-down devices (ChromeOS, iPad) that have had their support terms expire. I suppose that is crappy, but it's not quite the image I'd conjure myself. For various reasons but mainly because I so rarely use laptops, I have a crappy laptop from ca. 2010. It's slow, with a spinning-rust hard disk and an Intel Celeron from its day; it's a miracle it even allowed up to a 4GB RAM upgrade. With a GPU that can barely manage to process a 1366x768 framebuffer needed for the built-in screen, it's an unpleasant experience all around. By all means it's the definition of crappy laptop and that held even when the thing was new. All the same, it has no problem running Debian 11, and both the newest Chromium and Firefox can at least launch on it. It does take half a minute for the browser windows to actually appear, but it works, more or less. The per-site experience after this depends heavily on how much "cool tech" web site developers have opted to use. YouTube is practically unusable even in the tiny video window it displays and 360p videos. Hacker News is perfectly fine. Perhaps bias on my own part, but I would argue that this case is the crappy laptop that's reasonable to optimize for. It may not be pleasant, but for large classes of web sites, it should be bearable to some extent. I'm pretty sure both the Chromebook and iPad mentioned in the article have better hardware specs than my thing, but they're both made by companies that are far too willing to drop support after a short period, leaving users in an insecure status and many of them just don't know why web sites stop working.
- modeless 5y agoChrome OS devices are not locked down in the slightest. You can run any browser you want in Chrome OS via the Play Store or as a Linux app. Furthermore, every Chrome OS device can be unlocked to run any OS you want. You can install Chromium OS, Linux, or even Windows if you like. They are not at all like iPads.
- hannasanarion 5y agoCan your grandma do that? If not, then it is a de-facto locked-down device. It shouldn't take technical expertise to keep consumer electronics usable.
- teawrecks 5y ago> 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. No! This is 100% Google/Apple's fault for planned obsolescence. They should have an option to allow the browsers to update to the latest even if the device is unsupported. You can't expect every website on the internet to test on every old version of every browser that any old device might be stuck on. Where would it stop? Meanwhile, your mom's old browsers are missing important security updates!
- aethertron 5y agoThey don't need to pre-emptively test on everything. Fixing such issues after they're reported would be good.
- teawrecks 5y agoBut that would just increase the number of issues reported over time. It can't scale. When should they stop supporting these devices? If their telemetry shows 1 user on an iPad from 5 years ago, does that mean they need to support it? What about 1 user on an iPad from 50 years ago? Again, where does it end? You shouldn't be running an out of date browser at all, that's a major security risk.
- aethertron 5y agoSupport doesn't need to be perfect. An out-of-date browser should be security-OK for things that don't involve money. Maybe JS needs to get switched off. So sites should work without JS.
- twodave 5y agoOr at least if they're going to end support for a device, give us one last update to open up the bootloader so we can make some use for the thing other than as a paperweight.
- dmitriid 5y ago
- mattnewton 5y agoI wonder if the Chromebook has enough hdd space to make installing debian and chrome latest viable? This is clearly something google should fix by unbundling chrome from the hardware (and it looks like they are going to do so). I agree that this is also just a sloppy job by the website maintainer but I don't expect much from them and I expect a great deal more from apple / google, if only because I give apple / google a great deal more money.
- superasn 5y agoFor all the hate Webpack and Babeljs gets, couldn't this have been prevented if the website was using a transpiler to create a vendor version that would work with old browsers? I reckon whenever I run roll-up on my Vue apps it creates many versions of my app which I beleive are only to automatically take care of such issues.
- gedy 5y agoYeah the recent "omg webpack is so lame, just use es modules", etc puts us back to having to worry about browser differences, complaining about them not updating, etc.
- flanbiscuit 5y agoI was thinking the same thing. If I scaffold a new React App using Create React App it comes with browserslist[1] which handles setting the target browsers versions that babel will transpile to. If you never change the defaults then the production targets are: ">0.2%", "not dead", and "not op_mini all". I was wondering if these defaults would have prevented this problem in the story from happening. If we run this: npx browserslist ">0.2%, not dead, not op_mini all" We get this list: and_chr 96 and_ff 95 and_uc 12.12 android 4.4.3-4.4.4 chrome 96 chrome 95 chrome 94 chrome 93 chrome 92 edge 96 firefox 95 firefox 94 ie 11 ios_saf 15.2 ios_saf 15.0-15.1 ios_saf 14.5-14.8 ios_saf 14.0-14.4 ios_saf 13.4-13.7 ios_saf 12.2-12.5 opera 82 opera 81 safari 15.1 safari 15 safari 14.1 safari 14 safari 13.1 samsung 15.0 From that list it looks like the oldest Chrome supported is 92 and oldest supported Safari is 12.2-12.5 In the post, the versions the mom was stuck with were: - Chrome 76 (released July 30, 2019[2]) - iOS Safari 12.?? (originally released 2018, last update 2019[3]) So using Create React app this probably should have at least worked in iOS Safari. So this brings up the question of how far back should we support? Chrome 76 and iOS 12 are only a few years old (2018-2019). According to caniuse[4], Both Chrome 76 and Safari 12.1 have a usage of 0.07% so in order to support it you would need to change the ">0.2%" to ">0.06%". If your build process is already setup to use Babel+BrowsersList then it should be an easy fix of just changing values in the array and it should come at no cost to your development experience. 1. https://github.com/browserslist/browserslist https://github.com/browserslist/browserslist 2. https://en.wikipedia.org/wiki/Google_Chrome_version_history https://en.wikipedia.org/wiki/Google_Chrome_version_history 3. https://en.wikipedia.org/wiki/Safari_version_history https://en.wikipedia.org/wiki/Safari_version_history 4 https://caniuse.com/usage-table https://caniuse.com/usage-table
- pickpuck 5y ago> They should be making their website’s code more accessible to legacy devices. If there's an iota more work involved, the analysts have no reason not to defer to analytics. Anything less than ~1% gets dropped. So there goes your ES5 build. "Accessibility" in the screen reader sense is additional work done to support a low-usage audience, but because it has legal implications it has much more weight. I guess it would take someone using older tech winning in court for this to be given greater consideration. But that seems unlikely because people who use older tech are not a protected class.
- brainlessdev 5y agoA friend lent me a 2017 iPad that she's no longer using. I wanted to download Spotify, but couldn't, because I needed a newer version of iOS. The device does not get a new version of iOS, so I tried Safari to see if the web client works. Spotify's web client does not work on that version of Safari. So I tried downloading Firefox and Chrome, but I can't because they no longer support my version of iOS. So I looked for a way to download older versions of apps (Spotify, or an older version of Firefox or Chrome on which Spotify would still work). As it turns out, there's a way: you first need to "purchase" the app you're interested in on a newer device that supports the latest version. Then, you can log into your older device and download an older version of the same app. That means there's a way for me to run an older version of an app that works on my iPad, but nah, I need to first get a newer device and "purchase" it there. My conclusion: the onus is on the device manufacturers to not arbitrarily restrict their users. Jim Nielsen's mom's iPad is perfectly capable of opening that website, but its manufacturers are limiting it artificially.
- javajosh 5y agoWhich reminds me to ask - is anyone making a custom OS for iDevices yet? Something like Graphene for iOS? I know about Asahi Linux, but that's for M1 laptops, AFAIK. (Because the "right" solution here is clearly to ditch the OS and install something Linux-y, and then whatever software you need, including recent Chrome). Same question for ChromeOS devices.
- jeroenhd 5y agoThere are ongoing attempts at running Android on old iDevices, but I doubt they'll ever be as good as custom roms on normal Android hardware.
- goda90 5y agoIt gets worse. Even if you could download an old version of Firefox and Chrome to your iOS device, they'd have the same problem as Safari, because Apple bans third party browser engines. Firefox and Chrome for iOS are essentially wrappers on a Safari core.
- jopsen 5y agoJust my personal opinion, but designing websites to support old browser versions is not the solution. Such old browsers probably have known security vulnerabilities. Maybe find a new OS? Seems sad that old devices can't keep working.
- waynecochran 5y agoI am old enough to remember the manta of "backwards compatibility" from the 1980's. It was the advent of the web that eventually led to "release early / release often" and damn any concern about breaking old stuff. If it was not for Linus enforcing "user space" backwards compatibility in the kernel, Linux systems would have (un)planned obsolescence at the kernel level.
- deleted 5y ago[deleted]
- ciupicri 5y agoThen why should Javascript evolve, if no one is going to use those features because of backwards compatibility?" Also take note that even Linux dropped support for i386 around 2012.
- waynecochran 5y agoThere is probably some happy medium between backwards compatibility and deprecating old behavior. JS programmers are a little too ADHD for me and create a lot of broken crap. Linux dropping support for an old machine is not the same as changing the kernel API -- my old programs that ran on an i386 will still run on a more modern machine (perhaps recompiled).
- yawnxyz 5y agoha, this reminds me of building a site that was used by gov't types (FDA, NIH, CDC) and I kept getting questions about why the site didn't work. Turns out I'd forgotten to test the site on pre-Edge / IE browsers, which apparently come with very old versions on gov't computers. Maybe that's not a problem anymore, because of the Edge update? Honestly don't know... haven't gotten those emails in a while.
- Flimm 5y agoThis blog post prompted to look for ways to display a friendly error message to the user, explaining the issue and that upgrading the browser may help. This is what I found: https://stackoverflow.com/a/70671657 https://stackoverflow.com/a/70671657 I would also like to display a friendly error message to the user if I resource fails to load because of a 404 or because of network issues. This is the only solution I found: https://stackoverflow.com/a/64243346/247696 https://stackoverflow.com/a/64243346/247696 Of course, I don't think this is the whole solution. But it's something we can do without waiting for browsers to get updated.
- masklinn 5y agoThere are two issues with that: 1. the error message will not be helpful or actionable, instead of the website not working it'll be telling the user to get lost 2. google can break it at any moment with no notice (others as well, but google seems much more aggressive in their "deprecation"), they already removed (then reverted because of just how much it broke) cross-origin alerts
- ape4 5y agoWhy not mail the website and let them know about this. Maybe other people are having the same problem.
- jimmyvalmer 5y agotldr; test your junk on old browsers.
- z3t4 5y agoUpdate the script via dev tools and cache it for 10 years. Or install LinuxFirefox on the Chromebook
- slmjkdbtl 5y ago> my Mom had trouble volunteering and participating in her local community because somebody shipped the optional chaining operator in their production JavaScript. Is there a solution tho, instead of sticking to absolute no new browser features when it's not 100%? What if the browser pulls always compatible bytecode from server instead of pulling javascript text code?
- p1mrx 5y agoI like using the term "software-defined garbage" for this scenario: the hardware is fine, but software sends it to the landfill. One solution is to only buy hardware that's capable of running a generic Linux distro after the manufacturer abandons it.
- matt_heimer 5y agoDo polyfill/transpiling proxy servers exist? I'm thinking along the lines of an addon for squid or similar that would leverage babel to add polyfills and js transpiling. Might require per-site rules but shouldn't something like this be possible?
- jabbany 5y agoI'd imagine someone could build a Chrome extension to do this as a fully client-side solution... i.e. Grab all the scripts on a site, recompile for something like an ES5 target, and then replace them with the locally compiled scripts. The issues are probably rare enough though that there is little motivation to actually do this.
- 1ris 5y agoWhen CoffeeScript came out, i thought the course of action was obvious: Never update the JavaScript language again, and update CoffeeScript and similar languages. Just for the sake that javascript will have to be backward-compatible for ever it seems such a bad idea to change it at all, except maybe for thing that make it a better compiler target. This is of course not what happened. Stories like this make me think that this is what should have happend, tho.
- azangru 5y ago> 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. And here is me, a web developer, thinking that using a feature supported by the latest versions of all major browsers should be fine... I don't know what a proper strategy should look like; but it's hardly a case of "progressive enhancement" that the author is talking about. You might — if the functionality of the site allows — progressively enhance from no js to full js; but you can't progressively enhance from old js to modern js. One could, of course build different bundles with different javascript targets; but how many such targets should one have? How many legacy browser versions would the author want web developers to support?
- zdunn 5y ago> but it's hardly a case of "progressive enhancement" that the author is talking about. This is definitely a case of progressive enhancement. If the site had started out with a basic form, it would have worked on the referenced devices/browsers when the javascript broke. > but how many such targets should one have? 2. You should have your main script which can have the latest features and compile it down to ES5, which will work in nearly every browser. Compiling to ES5 is one of the easiest web development tasks to automate so laziness isn't a valid excuse. Just using this technique of ES5/ESNext would support nearly every legacy browser/version.
- azangru 5y ago> and compile it down to ES5, which will work in nearly every browser And how do you load it, as opposed to the modern bundle? I've heard about the script nomodule technique; but that would become less and less relevant as more and more browser versions start being able to load and execute ES6, but not ES_current_year.
- zdunn 5y agothe es5 build will reach less and less users over time, but it has no cost for other users or even the developer. Load it with a script nomodule tag and you always have a JS fallback that covers weird edge cases like the one described in the article. And building with the right HTML foundation, means you have a fallback for any breaking javascript, that will cover even more edge cases.
- mrkramer 5y agoImagine trying to write your online exam and this happens.
- shadowgovt 5y ago> 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 What is their incentive to do so? Because their incentive to not do so (by taking advantage of new features) is easier-to-write and easier-to-maintain sites. Losing X% of users (where those users are using old browsers) may be worth avoiding the risk of having your site crash badly when a dependency doesn't materialize (because without optional chaining you're exhaustively checking all those could-be-undefineds by hand). ... all of that having been said: for my money, the best solution is to support both by avoiding "bare-metal JavaScript" like the plague. Use TypeScript and set your compilation target to an old ecmascript version. Of course, then your site is larger because of polyfill for features a modern browser would understand natively... Everything is trade-offs.
- Bilal_io 5y agoI think one of the solutions to this is for JavaScript frameworks to evolve and be able to support both JS and no-JS. This way any user can run a website whether they're using an old browser or a modern browser where they choose to disable JavaScript
- pier25 5y agoPersonally, I never use a feature in production which isn't at least 5 years old. I'm barely starting to use CSS vars now.
- bmeski 5y agoI’ve seen the transition occur in my company where DX is trumping backwards compatibility, “simplicity”, and inter team cohesion. If you can’t bother to write the if statement that guarantees backward compatibility and follows a defined standard in use for almost 20 years, you are a horrid engineer IMO. This is why there’s a general trend toward all things becoming complicated, brittle, and shitty.
- duderific 5y agoHopefully nobody is writing if statements in code to handle backwards compatibility. That would be terribly unmaintainable. This should be handled at the compiler level. In javascript world, it is fairly simple to use Webpack or the like to target whatever browser versions you wish to support. If you're not using a compiler, you should definitely not use the latest and greatest features, unless you are well aware that you will not be supporting older browsers.
- bmeski 5y agoThat’s literally how all polyfills work. They first check if the thing is there, and if not then implement it. And in this case you can simply do an if statement with (first && first.second && first.second.third) My point being, writing one long line is how the language inherently works. Use that instead of the new feature that only ships in new browsers. I’d still be upset if one of my teammates added an entire bundling system so they can simply write fewer lines for such simple menial aspects of the code. Forest for the trees.
- omgitsabird 5y agoI see this issue happen from time to time when including dependencies that are not transpiled. The "distribution" assets of many packages target ES5 or ES6, but every now and then I run into issues introduced by packages that skip transpiling completely. This often results in problems when using popular "zero config" build packages, as they commonly skip transpiling dependencies in the node-modules directory by default.
- quag 5y agoI have a first gen iPad. Due to lack of software updates or the option to run another OS, I am using it as a clock. It’s a real shame. I’d love to be able to use it for something else.
- thot_experiment 5y agoI think in the context give this is a fair point, but a counterpoint: I code because I enjoy coding. I'm going to code in whatever way makes me happiest. I don't see any obligation to change what I'm doing in order to make things I write more accessible. The default assumption is that nobody ever sees my software at all. If I publish then it's all upside. If you don't like microtonal jazz don't listen to microtonal jazz, if I'm classically trained that doesn't mean I have to play stuff that's accessible to you.
- sombremesa 5y agoThis seems like "IT-style" troubleshooting and fixing, and even then it seems half-hearted. Can't you install other browsers on iPad? You could also install extensions like stylish on Chrome and fix it therein. You could try blocking the CSS file from loading. [0] Sure, we can prioritize shitting on the people who made the site, or Apple, or Google, but then your mom continues to have this issue. Shouldn't fixing that be the first priority, even if it involves some hacks? [0] https://stackoverflow.com/a/17892877 https://stackoverflow.com/a/17892877
- matt_heimer 5y ago> This seems like "IT-style" troubleshooting and fixing, and even then it seems half-hearted. Can't you install other browsers on iPad? iOS devices limit browsers to only using the Safari engine so any installed browsers will have the same limitation. > You could also install extensions like stylish on Chrome and fix it therein. You could try blocking the CSS file from loading. [0] The chaining operator is a JavaScript enhancement. Sure, you could block the JavaScript but considering the site doesn't work when the JavaScript fails I don't think blocking JavaScript will fix the site. An extension, like https://chrome.google.com/webstore/detail/resource-override/pkoacgokdfckfpndoffpifphamojphii?hl=en https://chrome.google.com/webstore/detail/resource-override/..., that is similar to the dev tools local overrides might let you fork the site's JS files. But that isn't a maintainable approach.
- spixy 5y agoWell that´s what you get by using locked OSs.
- vldr 5y agoWould installing chrome, firefox or some other browser through google play work here? It'd be a hack, having a special mobile browser for just that site, but still