Node is proven but it is also very new. It is in its most critical phase of achieving mass adoption right before it is fully baked. This means complexity is at its highest level, right when the contribution payoff is at its lowest. In other words, most developers are not motivated enough or skilled enough to move it forward.
With power comes responsibility. You can read Hammer’s open letter about the responsibility that comes with choosing a young technology. Dear CEO (of a node-powered corporation)
I’m looking forward to following the development of this project.
The robots.txt was first officially rolled out 20 years ago today! Even though 20 years have passed, some folks continue to use robots.txt disallow like it is 1994
This document covers how to use browserify to build modular applications. You can use browserify to organize your code and use third-party libraries even if you don’t use node itself in any other capacity except for bundling and installing packages with npm.
If you’ve been wanting to get started with Browserify or need more in-depth guidance, this is the most useful guide to Browserify: substack/browserify-handbook
With more than 2000 published titles and $400,000 awarded through their Open Source Project Royalty Scheme under their belt, Packt Publishing is celebrating their 10 year anniversary.
To celebrate, eBooks and Videos are $10 each until July 5th 2014.
More information is available at: http://bit.ly/1nYPeTw
This could be quite useful. Check out JSNice
Even something as simple as a dropdown menu or a bar graph can introduce usability problems. From a slide out menu disappearing when a user’s mouse moves a few pixels too far, to requiring NASA-like levels of precision to mouse over the right element…
This is a great presentation from JSConf2014 exploring algorithms that solve user interface problems.
Today I want to share with you some pain and thoughts on current state of npm packages and node_modules folder in your application root. Most of the times npm packages is declared as dependencies of your app in package.json and installed every time you need them.
Did you know that you can build your own CSS preprocessor with Node.js libraries? They can be used alongside established preprocessors like Sass, and are useful for defining tasks beyond preprocessing.
— Nicolas Gallagher
Find out more in this article: