Old vs New JavaScript – HTTP203




Jake and Surma look at the modern JS & web features we take for granted.

Subscribe to the channel! → http://bit.ly/ChromeDevs1

Watch more HTTP203 → http://bit.ly/2sPq2LB

Listen to the HTTP203 podcast for more content! → http://bit.ly/2Kryv2y
Itunes → https://apple.co/2IQagG6

Original source


40 responses to “Old vs New JavaScript – HTTP203”

  1. Prototypical inheritance is a class system. Car is a class, and c = new Car() is an instance of a car.

    ES6 classes don't change that. There's still an object with a prototype, and those methods still exist on that prototype. It's "merely" synaptic sugar. I think it's very useful sugar, but it doesn't actually change the mechanics of classes.

  2. Is there a reason for the non-oneline solution (Car.prototype = Veichle.prototype) at 2:35? I'm thinking as the prototype still refers to the Veichle prototype in your example. 2:57 also seems a bit odd since it's still all prototypical inheritence under the transpiled hood.

    Don't get me wrong, I love the new synax sugar. I just find that this video could be a bit confusing for people that think they are "free" from prototypes just because of the new syntax sugar. I also don't think you should dismiss prototypes as being old and qwerky, as they do enable you to do a lot of cool stuff during runtime.

    This video could probably be more useful if our transpile target was WebAssembly rather than es3/es5.

  3. Great episode, but the talk about prototypical inheritance is weird. They were talking about it like it's a weird bygone language trait that we would all rather forget…. Javascript is a prototypical language, and classes are just syntactic sugar over prototypes. Which is why I don't use classes and stick with prototypes, because I like the syntax, it shows me what is actually going on, and has performance benefits in certain circumstances. That is when I do OOP in JS, which is not that often nowadays.

  4. I think it's gonna be another 5 years until `el.animate` is well supported, future generations will have to suffer trying to implement programmatic CSS animations. The thing I'm most excited (and will probably be better supported than web animations) is OffscreenCanvas.

  5. Thanks Jake and Surma. Very excited to know about the clean way of the FileReader part. So I have a question about this one: Does Response just apply to readAsArrayBuffer() and readAsText() of FileReader, how about the readAsBinaryString() and readAsDataURL()?

  6. i just bypassed all that inheritance stuff completely .. never used it, mainly because i never saw an example that demonstrated real world application/benefits … ill show myself out

Leave a Reply