JavaScript Patterns for 2017 – Scott Allen




The JavaScript language and ecosystem have seen dramatic changes in the last 2 years.
In this sessions we’ll look at patterns for organizing code using modules, talk about some of the pros and cons of new language features, and look at the current state of build tools and build patterns.

Original source


12 responses to “JavaScript Patterns for 2017 – Scott Allen”

  1. I was always told to write my programs so that variable names and function declarations where as descriptive as possible to what the underlying behavior is doing so that it was as easy as possible for the human to understand what was going on… since these abstractions aren't adding anything that wasn't already there, I would argue they are trying to do the exact opposite… obviously not everything in this talk fits into what I'm referring to, like async/await is something that adds what wasn't already there but stuff like => or …!!data ? data : {default:true} aren't adding anything new, its just an abstraction of what could've been written in the same Javascript you learned in the first two weeks. If you prefer condensed reading, perhaps chunk up your code into a function or get a better editor that helps with condensing code instead of trying to evolve Javascript into a different language. To be completely honest, I think the philosophy should be that, if you're using abstractions that don't add anything new, you're considered a less ideal programmer.

  2. this was a really good talk, this guy is clear and concise on the point, unlike all the other JS ninjas who are just talking too fast and rambling on and on ….

Leave a Reply