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”
Thank you for presenting the well understood OOA/OOD concepts in rudimentary JavaScript ecosystem. Computer Science educators should take note.
About the ../../eternity of dot dot slash, instead of doing that you can leverage native node modules like process, path, and __dirname
2017 managing JS dependencies… still kind of a mess
surprise surprise, am I right?
Given how you're basically using Gulp as a proxy to CLI, you might try just using npm scripts instead.
I had no idea the class keyword doesn't hoist. Good to know.
Pure magic. Typical Alan Rickman…
Great! Filled in many loose ends for me.
Really good talk!
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.
How many of these patterns and frameworks are y'all gonna have to learn before you admit that JavaScript is the porblem?
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 ….
webpack 2 is out, btw. (the video features webpack 1, which has some incompatibilities, like 'loaders' instead of 'rules')