Комментарии:
Google you inspiring me so much.
ОтветитьJavaScript now is overtaking Python.
ОтветитьSo many new things coming to JS! I am excited.
ОтветитьJavaScript is the future woop
ОтветитьCan we get statically typed in js ?
ОтветитьI love how the extensive know-how of building browsers acquired from Internet Explorer is now properly propagated to Edge. I particularly like the lack of support of any modern JS features and the weird CSS bugs. Do you plan to add an experimental flag to Chrome to bring us the Internet Explorer experience we have all grown to love?
Ответитьnice, finally I can multiply in JS!
ОтветитьMuch respect to presenters for listing all supported browsers each time and not just stating the obvious "All browsers except Edge"
ОтветитьFinally we'll have regex look-behinds... for christ's sake!!!
ОтветитьAbout classes, JS use a poor level classes structure, why not implement the current specification in ECMA 4th
Ответить...defaultSettings is ugly syntax. Javascript is becoming Perl. Why not just use Perl then. Add async to Perl, and bam call pa programming language to kill javascript.
ОтветитьUse the platform, I repeat, use the platform :)
ОтветитьI want to know JS but i am bad at solving logic problems 😑
ОтветитьPrivate properties in JavaScript. Oh my god! I can't believe I will be alive to see this.
ОтветитьWhy, the hell, `finally` word (in try-catch), but not 'done' as in promise...?
ОтветитьBuild the future web but don't forget: Googlebot is using Chrome v41
ОтветитьJS now has Perl style Regex Matchers
ОтветитьWoah... I just hate how all browsers ship things slowly.
ОтветитьFinally JS is getting lookbehind :D
ОтветитьWe're on the bleeding edge here folks. Readable regular expressions. Who'd have thought that would ever have happened.
ОтветитьI'm so tired of hearing people saying that async makes code cleaner... It is not! Is just that you are more used to it, you are so C-like biased that you can't even understand any other syntax.
ОтветитьToo Cool! Great Work
Ответитьfinally JavaScript will be the same both for the server and the browser!!!
ОтветитьVery cool staffs are coming! amazing..
Ответитьhave a question about recommended to use babel -env to transpile to specific browser version
say that i end up with two js file, one that support new js syntax natively (for latest supported browsers), one that transpiled the js
what is a good way to determine which one to serve??
do i write both in my script tag?
Finally Microsoft is doing a great job.
ОтветитьCoooool !
ОтветитьI don't know which version of Node.js they are referencing but with Node.js 10.4.0 "BigInt" is supported:
$ node
> console.log(BigInt(1) + BigInt(2)) // 3n
I always use Babble to transpile code for Edge.
Ответить阿三这么多 怪不得bug这么多
ОтветитьI don’t want to transpile my code, but some browsers are lagging behind the times 🐌
ОтветитьLOL @ Edge, just stop trying Microsoft. We've endured enough suffering with IE.
ОтветитьNothing we need whatsoever, only bad programmers always want more syntax. The only feature we needed were native module loading and tail recursion. I hope they dont make of Javascript such a Frankenstein language like C# with a new language feature like every 10 minutes.
ОтветитьYea... interlacing in 2018... quite modern....
ОтветитьV8:
ОтветитьIE Support is as bad as it always has been. Pathetic.
ОтветитьYeah, 2019 there are no more edge/opera icons. Emm..
ОтветитьAko neme vrtat na rabota vo geterym vo prilep javno hese ot kazam od gogel poradi predastvo
Ответить