4 ms·

It's not far off. We got some syntax niceties and 5 slightly different and conflicting ways to concatenate .js files from different directories a.k.a packages.

It's not far off. We got some syntax niceties and 5 slightly different and conflicting ways to concatenate .js files from different directories a.k.a packages. Apart from standardizing some things (doesn't hugely matter for electron since it's the only target) and getting async - what has really changed?

paulddraper 2y ago
Modules, iterators, async/await, localization, proxies, regex features, Promises, date functions, generators, classes, destructuring, WeakMap, strict mode, private members, BigInt, and a hundred other things. Check out: https://compat-table.github.io/compat-table/es5/ https://compat-table.github.io/compat-table/es5/ https://compat-table.github.io/compat-table/es6/ https://compat-table.github.io/compat-table/es6/ https://compat-table.github.io/compat-table/es2016plus/ https://compat-table.github.io/compat-table/es2016plus/ https://compat-table.github.io/compat-table/esintl/ https://compat-table.github.io/compat-table/esintl/ --- Not to mention that fact that Teams is actually written in TypeScript (tho compiled to JavaScript).
- viraptor 2y ago
  I see really only: strict mode, weakmap, bind, typed arrays, maybe spread. (+ async mentioned earlier) The rest as far as I can see can be either written as your own function or babel-style compilation. Sure, today's code would be nicer/shorter, but... the language itself really didn't change that much, just how we use it / what we expect from it.
  - paulddraper 2y ago
    > babel-style compilation "It's not a different language, because you could have another language compile to it."
    - viraptor 2y ago
      This has been the situation for years though. Only recently did we get reasonable native support for most new standards by default. Babel compilation down to IE level was really common just few years ago. Most of the "modern JS" stuff was based on that idea. Teams was released before even the modules existed in the browsers.
- mhio 2y ago
  Also https://node.green/ https://node.green/ which lays out features in one big list
mhio 2y ago
You could maybe use that argument in 2014 but writing js now is a fundamentally different experience to what it was 10 years ago, let alone 25.

paulddraper 2y ago

Modules, iterators, async/await, localization, proxies, regex features, Promises, date functions, generators, classes, destructuring, WeakMap, strict mode, private members, BigInt, and a hundred other things. Check out: https://compat-table.github.io/compat-table/es5/ https://compat-table.github.io/compat-table/es5/ https://compat-table.github.io/compat-table/es6/ https://compat-table.github.io/compat-table/es6/ https://compat-table.github.io/compat-table/es2016plus/ https://compat-table.github.io/compat-table/es2016plus/ https://compat-table.github.io/compat-table/esintl/ https://compat-table.github.io/compat-table/esintl/ --- Not to mention that fact that Teams is actually written in TypeScript (tho compiled to JavaScript).

viraptor 2y ago
I see really only: strict mode, weakmap, bind, typed arrays, maybe spread. (+ async mentioned earlier) The rest as far as I can see can be either written as your own function or babel-style compilation. Sure, today's code would be nicer/shorter, but... the language itself really didn't change that much, just how we use it / what we expect from it.
- paulddraper 2y ago
  > babel-style compilation "It's not a different language, because you could have another language compile to it."
  - viraptor 2y ago
    This has been the situation for years though. Only recently did we get reasonable native support for most new standards by default. Babel compilation down to IE level was really common just few years ago. Most of the "modern JS" stuff was based on that idea. Teams was released before even the modules existed in the browsers.
mhio 2y ago
Also https://node.green/ https://node.green/ which lays out features in one big list

mhio 2y ago

You could maybe use that argument in 2014 but writing js now is a fundamentally different experience to what it was 10 years ago, let alone 25.