4 ms·

What do you mean by "the underserved billions of the world without the latest year's smartphone"? Sure, there is a small set of people who choose not to run JS

What do you mean by "the underserved billions of the world without the latest year's smartphone"? Sure, there is a small set of people who choose not to run JS, or use something like lynx that doesn't support it, but almost every browser version released in the last 20 years, certainly all the graphical ones, have by default good enough JS support to gather basic statistics and send them back to the server.

superkuh 3y ago
Look at collector.js, in the first dozen characters it's already using ECMAScript 6 standards like promises. At the very least you need to change that "last 20 years" to the last 5 years.
- reissbaker 3y ago
  Promises have been supported since 2014 in both Chrome for Android and Safari on iOS. Even pretty old phones generally run web browsers more recent than that — and that's not "the last five years," that's nearly twice as long.
  - superkuh 3y ago
    If you are going by the dates that Google and Apple browsers supported it for the first time. But if you tried to use ECMAScript 6 features back in 2014? Hah! The support would not be there. 5 years is a realistic number.
    - reissbaker 3y ago
      You argued that using these features today blocked "billions" of people using old smartphones. Promises have been supported by smartphone browsers for over nine years. I do not think that using promises today prevents anywhere near billions of people from running your code, nor do I think that "5 years is a realistic number" for a feature that has been supported for 9. We're discussing whether using promises today impacts a significant number of web users.
- arp242 3y ago
  I get what you're trying to say, but a lot of these ES6 things have been supported for longer than you'd think a while now, and are near-universal. Near-universal: not universal. But people still running very old devices or browsers are not going to have a fun time on many sites regardless, and WebGPU is not likely to be used casually on random sites: it will be used for the same stuff that WebGL and canvas is today: mostly for special-purpose things like games, some visualisations, etc. – the sort of stuff that very old and slow devices will have trouble with in the first place.
  - account42 3y ago
    > it will be used for the same stuff that WebGL and canvas is today So for fingerprinting, got it.
- roqi 3y ago
  > Look at collector.js, in the first dozen characters it's already using ECMAScript 6 standards like promises. According to caniuse, promises are supported by Chrome since v33, by Edge since v12, by Firefox since v29, and by Safari since 7.1. https://caniuse.com/promises https://caniuse.com/promises Both Chrome 33 and Firefox 29 were released in 2014.
  - littlecranky67 3y ago
    You are gently omitting IE which doesn't have this at all. Doesn't matter when others were released, at that time IE had a market share that was non-neligible.
deleted 3y ago
[deleted]

superkuh 3y ago

Look at collector.js, in the first dozen characters it's already using ECMAScript 6 standards like promises. At the very least you need to change that "last 20 years" to the last 5 years.

reissbaker 3y ago
Promises have been supported since 2014 in both Chrome for Android and Safari on iOS. Even pretty old phones generally run web browsers more recent than that — and that's not "the last five years," that's nearly twice as long.
- superkuh 3y ago
  If you are going by the dates that Google and Apple browsers supported it for the first time. But if you tried to use ECMAScript 6 features back in 2014? Hah! The support would not be there. 5 years is a realistic number.
  - reissbaker 3y ago
    You argued that using these features today blocked "billions" of people using old smartphones. Promises have been supported by smartphone browsers for over nine years. I do not think that using promises today prevents anywhere near billions of people from running your code, nor do I think that "5 years is a realistic number" for a feature that has been supported for 9. We're discussing whether using promises today impacts a significant number of web users.
arp242 3y ago
I get what you're trying to say, but a lot of these ES6 things have been supported for longer than you'd think a while now, and are near-universal. Near-universal: not universal. But people still running very old devices or browsers are not going to have a fun time on many sites regardless, and WebGPU is not likely to be used casually on random sites: it will be used for the same stuff that WebGL and canvas is today: mostly for special-purpose things like games, some visualisations, etc. – the sort of stuff that very old and slow devices will have trouble with in the first place.
- account42 3y ago
  > it will be used for the same stuff that WebGL and canvas is today So for fingerprinting, got it.
roqi 3y ago
> Look at collector.js, in the first dozen characters it's already using ECMAScript 6 standards like promises. According to caniuse, promises are supported by Chrome since v33, by Edge since v12, by Firefox since v29, and by Safari since 7.1. https://caniuse.com/promises https://caniuse.com/promises Both Chrome 33 and Firefox 29 were released in 2014.
- littlecranky67 3y ago
  You are gently omitting IE which doesn't have this at all. Doesn't matter when others were released, at that time IE had a market share that was non-neligible.

deleted 3y ago

[deleted]