In a previous article that I wrote earlier this year, I talked about eliminating project dependencies that needed to be installed globally, such as Grunt, Gulp, Browserify, WebPack, etc. Of course, I didn’t argue for eliminating these packages, just replacing the -g flag with a --save or --save-dev flag when installing them with npm install and then using npm scripts to execute the binaries. Well, there’s more…
Take a look around. Notice anything different? Yes, the theme has changed! That’s the obvious thing, and it’s actually going to change again, hopefully some time in the next few months. There’s a lot of work being done behind the scenes for this site, so let’s take a look.
It’s been months since I’ve given you all any content here. I’m trying to break that trend, but it will be a while and will take some major changes in order to start writing regularly again. This post isn’t even a full post. Rather, it is an announcement to bring your attention to a post I wrote elsewhere.
Most browsers have a bug that isn’t really a bug. In fact it was purposely put there to make your simpler, but if you (or someone else writing the HTML code) do something in the right (read “WRONG!”) way, it could completely blow up. Specifically, if you assign your input tags a name or id attribute of “action” or “submit”, you can cause some very well hidden bugs.
Promises are currently the best tool we have for asynchronous programming and they appear to be our best hope for the forseeable future, even if they’ll be hiding behind generators or async functions. For now, we’ll need to use promises directly, so we should learn some good techniques for using them right now, especially when dealing with asynchronous operations on collections, whether they happen in parallel or sequentially.