This week, Paul & Jake talk about the future of JavaScript: ES6 and beyond.
Watch more HTTP 203 here: https://www.youtube.com/watch?v=Hy6wceqkxvA&list=PLNYkxOF6rcIAKIQFsNbV0JDws_G_bnNo9
Subscribe to the Chrome Developers channel here: https://www.youtube.com/user/ChromeDevelopers/
Original source
17 responses to “The Future of JavaScript – HTTP203”
Sun protection, guys!
i use self = this, so when i use self it will us previoues 'this' context instead of the context where im calling it
ES8 rulez !!
self = this is my favorite…
Typescript and typing does give a lot of advantages in respect to tooling during development.
YES OMG YES! var that != this… give it a decent name! finally someone else singing the same song! I didn't mind, bind in certain places but can get messy ~
I disagree with TypeScript compiler producing unreadable code. It generates more readable JavaScript then Babel imo.
Hoodies by the beach where people are sunbathing? I'm confused. 😃
I don't think it's fair putting TypeScript in the same box with CoffeeScript. TS compiled into readable JS, it also has a lot of ES6/7 features already supported and types are optional. It's essentially JS, no need to learn a new language for JS devs.
1:17 the inaudible part is 'Traceur', a compiler.
Finally found! Love the captions too, btw. You make a wonderful work guys, thanks!
AHHH, this is where you guys are now hiding.
can def tell this wasn't recorded in blighty 😝
lol `var that = this`, `var jakey = this` !!! :)))
I can only assume gwt is all old fashioned now. Nobody mentions it anymore. Transpiler?
Babel is cool and I use it. However, I disagree with you two about the new class syntax. Not because I want to use prototypes, but because I think classes are the wrong direction for the language entirely, regardless of syntax. They provide no data hiding and they encourage inheritance, a language anti-pattern in my option (I always prefer composition). Since Javascript is now the world's most popular language, the constant pushes to make Javascript more comfortable for Java programmers makes no sense. Java should be making Javascript programmers more comfortable.
I'm glad I'm not the only one who has that same reaction when I see Coffee. Great video!