Bug with a double question mark

Hi, I found a bug with a double question mark “??” (opts.mode ?? 1)

Android 8/9 - uPlot.iife.min.js msg:“Uncaught SyntaxError: Unexpected token ?”, line:2, col:15438, stack:“SyntaxError: Unexpected token ?”

function uPlot(opts, data, then) { const self = { mode: opts.mode ?? 1, };

[leeoniya]

i guess it’s that time of the year to have “that conversation” again.

@denyaalt first, please understand that i appreciate the issues you have opened in the past here, which have allowed me to improve the project for you and for others.

with that said…

There are many users who have old smartphones. It is very bad practice to add features that do not work on older smartphones…

your contributions to open source appear to pretty much end there.

• you pay nothing to use uPlot
• you have contributed no code to this project
• your public profile shows you maintain no open source projects (never mind several high profile ones), nor provide free support or bug fixes to any others.

however, you seem to have a very strong opinion about how i should run uPlot and what browsers i need to support. that’s an amazing lack of perspective, and, frankly, respect. before you lecture me about supporting old tech, perhaps you can first finish working on https://github.com/leeoniya/uPlot/issues/474, or pick up another open issue here (just kidding, of course, i know this won’t happen). i maintain this project solo, i have 3 sponsors that total perhaps $10/mo, for a lib used by numerous multi-million $ businesses that pay me [drum roll]…$0. nice gig, right?

let’s talk about old browsers.

where in uPlot’s readme, demos, docs, or source code do you see any statement about browser support? i’ll save you some time: nowhere. the fact that it works at all in anything older than browsers released 6 months ago can be considered pure luck. as a single human being, with a finite amount of time, i’m not about to start testing uPlot in every fly-by-night version of every browser on every platform. your 2015 TV has some built-in browser based on IE8 that will never be updated? that’s truly unfortunate, but definitely your problem, and not mine.

There are many users who have old smartphones.

really? https://backlinko.com/browser-market-share

maybe, some of them should pay me to support them 🤷

i don’t deliver uPlot to end users, i deliver it to developers. if your users need old browser support, guess whose job it is to ensure that your code and your dependencies run through Babel with specific browser targets. the answer may not surprise you!

so, for the record:

uPlot runs in browsers that i can reasonably test and have a significant market share <today>. this typically means several prior versions of evergreen browsers, which are updated and fixed continuously. literally anything else may or may not require polyfills and/or Babel. if you have specific browser targets, it’s on you to guarantee this promise to your users.

[denyaalt]

Excuse me please… I just wanted to suggest not to use the new ES2020 features that we can easily do without…