They're shipped to stable Chrome (and many Chromium embedders enable them too).
-
-
Odgovor korisnicima @slightlylate @Rich_Harris
As the person who runs standards for Chrome, can you please explain how the fuck a non-standard feature got shipped to Stable Chrome?
0 proslijeđenih tweetova 32 korisnika označavaju da im se sviđa -
Odgovor korisnicima @AdamRackis @Rich_Harris
We often lead, balancing risk/reward rather than demanding a particular point in an arbitrary process. https://www.chromium.org/blink/launching-features … Leadership is rather the point of having an engine team, after all.
0 proslijeđenih tweetova 4 korisnika označavaju da im se sviđa -
Given that chrome has a near monopoly don't you think you should maybe not ship something as stable before other browsers have it to not reinforce the monopoly?
0 proslijeđenih tweetova 13 korisnika označava da im se sviđa -
Odgovor korisnicima @hrmny_ @slightlylate i sljedećem broju korisnika:
FWIW this is how the web has ALWAYS evolved. Almost all APIs we use today we're shipped in the dominant engine prior to a standard being ratified (IE, Netscape, WebKit, now chromium). JavaScript language is a notable and impressive counter-example.
1 reply 1 proslijeđeni tweet 3 korisnika označavaju da im se sviđa -
Odgovor korisnicima @RickByers @hrmny_ i sljedećem broju korisnika:
It isn't, tho. NN 2 unilaterally added livescript. MSFT copied and forced standardisation at ECMA. Same as it ever was.
1 reply 0 proslijeđenih tweetova 3 korisnika označavaju da im se sviđa -
Odgovor korisnicima @slightlylate @RickByers i sljedećem broju korisnika:
Surely Rick meant modern JS, ie ES6 and beyond, when he noted how impressive the JS standardization was? I've sadly not been in web dev long enough (originally a boring, corporate .net dev) to even know what you're referring to -- LiveScript? Did you just make that up? ;)
0 proslijeđenih tweetova 2 korisnika označavaju da im se sviđa -
Odgovor korisnicima @AdamRackis @RickByers i sljedećem broju korisnika:
Modern JS evolution has been a disaster -- and I say that as someone who has pushed the boulder up the hill as much as anyone. We introduced the stages model after some of the worst, but still not on productive footing.
0 proslijeđenih tweetova 6 korisnika označava da im se sviđa -
Odgovor korisnicima @slightlylate @RickByers i sljedećem broju korisnika:
Can you explain more why modern JS evolution has been a disaster? Decorators have gone ... poorly. I understand some bad actors (I've heard rumors possibly at Google) have at times torpedoed it with bad intent. But other than that ... I see a huge success. Where do you differ?
1 reply 0 proslijeđenih tweetova 1 korisnik označava da mu se sviđa -
Odgovor korisnicima @AdamRackis @RickByers i sljedećem broju korisnika:
I see the full balance sheet (which you don't) of time invested for progress delivered. TC39 is bad value. Decorators. Promises. Cancellation. Classes. Intrinsic subclassing. Decorators. Many, many aspects of modules. All many, many years late...and we aren't even to types yet.
1 reply 0 proslijeđenih tweetova 5 korisnika označava da im se sviđa
Years late? By whose schedule? Those features had *many* competing visions, and achieving consensus was fucking hard. But most got done, with outstanding results. I'm most sympathetic to Promise cancellation. The ideologues surrounding anything Promise-related are the *worst*
-
-
Odgovor korisnicima @AdamRackis @slightlylate i sljedećem broju korisnika:
It's unfortunate because this is all opinion, but I can't help but agree with Alex that the rate of change of JS to adopt completely needed features like Observables, Promise Cancellation, decorators, static/private/ class fields has been slow compared to other langs.
0 proslijeđenih tweetova 2 korisnika označavaju da im se sviđa -
Odgovor korisnicima @mikesherov @AdamRackis i sljedećem broju korisnika:
And when you look at it, everyone on TC39 is trying their best and doing a great job, and we do have progress, but as a procedure wonk I can't help but blame the need for *complete consensus* for the pace of change in the language.
0 proslijeđenih tweetova 6 korisnika označava da im se sviđa - Još 19 drugih odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.