News for hackers. Stuff that matters.
Re:ECMA TC39: “SmooshGate” was officially resolved by renami... by baybal2 on Thursday May 24, 2018 @02:44AM (#17141591)
>Wouldn’t it be possible to introduce a versioning mechanism, similar to strict mode, where you could opt in to a newer version of JavaScript?

Some people in web standards community and dotcoms will protest. There are big believers in "Live version"

It is very sensible thing to do, but you need to kick these people out of committees. Despite the numerous attempts, none has succeeded at that yet.

Re:ECMA TC39: “SmooshGate” was officially resolved by renami... by zaarn on Thursday May 24, 2018 @03:49AM (#17141921)
I would love that too.

HTTP has versions. IP has versions. A lot of APIs have versions.

Why? Because sometimes you want a new feature but the current API does not support it. So you break it and make a new one, keeping the old intact.

I can already tell my webbrowser which HTML version I use. That should and can be extended further.

Similarly it would be great if I could tell my webbrowser "Use compatibility level for 2010-2019" or "Use compatibility level 2000-2010".

Re:ECMA TC39: “SmooshGate” was officially resolved by renami... by baybal2 on Thursday May 24, 2018 @04:32AM (#17142159)
>Because sometimes you want a new feature but the current API does not support it. So you break it and make a new one, keeping the old intact.

This is how things should work. But other than impossible to remove proponents of hardcore live versioning, there are even more proponents of "Keeping 20 years old websites intact without changing a single line of code." So a valid JS 1.0 must still also be a totally valid ECMAScript 2017.

Those believe that it is somehow physically possible to engineer the language parser that it use some extremely sophisticated lexic tools to guess what version of JS something the code refers, those also are the proponents of "lets guess the api version by counting the number of arguments, and if we need a new one, we just add one more"

This is bad.

Why such people can't be taken down from standard committees? One of reason that people close to web standards making process don't want to discuss is that "tech/corporate strategists" at top dotcoms misguidedly believe that by making web standards an impossibly complex to implement thing, they can prevent appearance of newcomers to the browser market, thus making browsers a moat for competitors to drown in.

As Joseph Stalin said - "In a democratic society, the people who rule are not the ones who vote, but ones who count those votes." Those corporate appointees surely share this ideology - Ones who control the Internet business are not companies who run websites, but ones who write browsers to browse them: want to kill an advertising supported website? Put them into Google's secret bad websites list; want to displace a credit card processing competitor? Ban him from using the credit card API to which the browser is locked; want to kill a legal video streaming website? Deny him rights to DRM extensions in the browsers; and like this for all and everything.

Re:ECMA TC39: “SmooshGate” was officially resolved by renami... by zaarn on Thursday May 24, 2018 @04:47AM (#17142228)
>Those believe that it is somehow physically possible to engineer the language parser that it use some extremely sophisticated lexic tools to guess what version of JS something the code refers, those also are the proponents of "lets guess the api version by counting the number of arguments, and if we need a new one, we just add one more"

You don't need that luckily, we have DOCTYPE to tell us something about the version of a document.

A simple `<!DOCTYPE html js2018>` would be sufficient IMO though it might break older browser (but honestly, screw everyone still using IE8)

On the other hand we have WASM now and once we get proper integration into browser I imagine things might get better.

Re:ECMA TC39: “SmooshGate” was officially resolved by renami... by olavk on Thursday May 24, 2018 @06:02AM (#17142558)
It doesn't matter who you put on a committee - if a web standard break a significant number of sites then browser vendors will simply not implement that standard. If they did, users would stop using that browser. Why would anyone use a browser which does not render certain websites, if another browser (even a previous version) do?