The Optional Chaining Operator, “Modern” Browsers, and My Mom

• caniuse

  387 5,500 9.5 JavaScript

  Raw browser/feature support data from caniuse.com

  Here's the closest issue I could find: 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?

• galliumos-distro

  145 345 0.0

  Docs, issues, and artwork sources for GalliumOS

  

• SurveyJS

  surveyjs.io

  sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• browserslist

  55 12,683 7.8 JavaScript

  🦔 Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-preset-env

  

  - 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

  2. https://en.wikipedia.org/wiki/Google_Chrome_version_history

  3. https://en.wikipedia.org/wiki/Safari_version_history

  4 https://caniuse.com/usage-table

• OpenCorePkg

  185 12,716 9.2 C

  OpenCore bootloader

  

Suggest a related project