code::dive 2017 - Douglas Crockford - The better parts

[@pythooonuser2233]

One of the best talks ever.

[@alexnezhynsky9707]

Don't agree with arrow funcs. What doesn't he like about them? That you need to wrap them with () to return an object? Or that they're always bound to the same scope? I think both are fine, just need to be kept in mind, like any other feature caveats are.

[@Ursacke]

Since he already supports destructuring and the ellipsis operator, I'm guessing that he doesn't just dislike "shortcuts" out of hand. I think he dislikes arrows for the same reason he dislikes var: Because it can do things differently to how it really looks, and because of this we have to be guarded about them. Yes, we can learn what those things are and pat ourselves on the back for being clever little programmers, but maybe it's better just to keep things simple in the first place.

[@gxd4b1]

Try attaching an arrow function as a method to an object ... then see if your 'this' refers to the object ... It wont, it will point to the global object, and as an added bonus, arrow functions cant bind to a specific object. In short there are some things arrow functions cant do, but the 'function' keyword can do everything.

[@josephgarronegj]

Arrow functions are much more than just a shortkut. They free the language from the bind/apply nightmare.

[@josephgarronegj]

And using forEach instead of for ? You can't break a forEach loop and iterating this way make the code look like the iterating function is a callback...

[@FrankFang1990]

Just don't use *this*, then there is no need to bind *this*.

[@josephgarronegj]

Why should I stop using it? It's a verry usefull abstraction. If Douglas Crockford said he stop using *this* I assume it is because without arrow functions you need to bind the context everywhere.

[@abdulwarris]

Its just work well as callback but pty suck as object methods. Can’t be used as constructors & generators. Read more on MDN sites

[@josephgarronegj]

It seem obvious to me that arrow functions are not the right tool to use when you implement prototype methods or constructor. It does not mean they suck, just that they are not just an alias for not having to tipe "function", they serve a specific purpose.

[@AS-zw4lk]

Hipsters love Farts! Haha Like Marshall McLuhan said - we move forward looking in the rear view mirror. How painful were the browser war years - it's pretty clear that even when something better comes along its success depends directly on its rate of adoption - and that means getting the biggest players on board - who also have the most to lose with big investments in the status quo. First we define our technology and then it defines us! Why are we still typing Code?

[@AS-zw4lk]

I appreciate the content but I would change the typeface used in your presentation - mixed cases only act as a communication barrier given the topic of the discussion. We could just call it an unecessary source of confusion. I am surprised.

[@kylechurch6296]

I've gotta stop reading KZbin comments.

[@christiandasilva3590]

this is more or lessthe same content as his nordic.js talk from 2014. He didn't even update the content in 3 years?

[@gyurilajos7220]

When you get to a deep understanding that does not need updating. It is goldilocks.

[@gyurilajos7220]

The best thing about JSON is that it cannot be updated. A thing of beauty a joy forever enduring a stable foundation

[@serenity_zero]

1:11:04 Douglas' musings on "the next language" sounds to me like Erlang/Elixir ;)

[@johnhammer8668]

Nice Talk. But "Dont make bugs". Is it even possible ?.

[@alexnezhynsky9707]

I think you can make less bugs. But even OS'es have bugs. It's just human nature.

[@adrianoldchannel2494]

JavaScript is awesome why didn't they killed it dead. !!!! It's so koool

[@eacasanovaspedre]

I do not agree with most of what he said. Starting with the language, JavaScript is a very bad language for developing applications.

[@simoneast7]

I think it very-much depends on the kinds of applications you’re developing. The asynchronous event-driven nature of JavaScript has allowed for significant performance increases in high-traffic server applications (compared with say PHP, ASP.NET, Ruby, etc.) - and yes, a few other languages have since improved in this regard, but JavaScript (and Node.js) are still excellent performers in this regard.