This presentation gives an overview of cutting-edge JavaScript development techniques to build modern web and Node.js apps. Discover which features to expect in Chrome and Node.js soon, how the V8 engine optimizes for them, and how to improve real-world performance and stability on the Web and in Node.js.
Presenters:
• Mathias Bynens https://twitter.com/mathias
• Sathya Gunasekaran https://twitter.com/_gsathya
More info:
• https://developers.google.com/web/updates/tags/javascript
• https://twitter.com/v8js
Rate this session by signing-in on the I/O website here → https://goo.gl/RZMpqG
Watch more Chrome and Web sessions from I/O ’18 here → https://goo.gl/5fgXhX
See all the sessions from Google I/O ’18 here → https://goo.gl/q1Tr8x
Subscribe to the Chrome Developers channel → http://goo.gl/LLLNvf
#io18
Original source
32 responses to “Build the future of the web with modern JavaScript (Google I/O ’18)”
Yeah, 2019 there are no more edge/opera icons. Emm..
IE Support is as bad as it always has been. Pathetic.
Google appears to be married to the Democratic political party.The software development community desperately need Google to embrace DIVERSITY. Please Google, commit to diversity and promote the Republican agenda more often. This means promoting "personal freedom", "personal accountability", "smaller government", "equality of opportunity", "not equality of outcome", "equity", "social justice". Please Google, transform your archaic organisation.
V8：
Yea… interlacing in 2018… quite modern….
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.
LOL @ Edge, just stop trying Microsoft. We've endured enough suffering with IE.
I don’t want to transpile my code, but some browsers are lagging behind the times 🐌
阿三这么多 怪不得bug这么多
I always use Babble to transpile code for Edge.
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
Coooool !
36:00 that's a nice python feature javascript deserved
Finally Microsoft is doing a great job.
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?
Very cool staffs are coming! amazing..
finally JavaScript will be the same both for the server and the browser!!!
Javascript is everywhere. #Gyanuniversity
Too Cool! Great Work
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.
regexp .. sugar sugar sugar .. and of course its not supported for non chrome browsers. Pls just provide PCRE. And thanks for otherwise cool stuff. Rly mjs and class fields is a good.
We're on the bleeding edge here folks. Readable regular expressions. Who'd have thought that would ever have happened.
Finally JS is getting lookbehind 😀
I don't like using a different file extension, just to use modules.
Woah… I just hate how all browsers ship things slowly.
JS now has Perl style Regex Matchers
Build the future web but don't forget: Googlebot is using Chrome v41
Why, the hell, `finally` word (in try-catch), but not 'done' as in promise…?
Private properties in JavaScript. Oh my god! I can't believe I will be alive to see this.
I want to know JS but i am bad at solving logic problems 😑
Use the platform, I repeat, use the platform 🙂
…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.