Server-side code is definitely not my thing so Node has always made me nervous. I can talk about how it works in the abstract, but actually using it has intimidated me. I delayed learning Node until the last minute.
But as I started playing with Node, something funny happened: understanding it turned out to be easy!
I’m not saying that it was so easy that I’m now a Node guru. I had to grasp Node’s event loop, its handling of server modules and gain a basic understanding of the how servers work in general. And I still have more to learn.
I need to be clear about something before I go on: I AM NOT BAD-MOUTHING JQUERY!!!! jQuery is awesome! I think you should use it and don’t see myself doing any future web projects without it.
Here’s the list:
Already implied in this post but it bears a deeper examination. Let’s look at this list:
What You Know After Learning Just jQuery
Now, let’s look at this list:
- jQuery UI
- jQuery Mobile
- How to create jQuery plugins
- How to create Node.js modules
- ECMAscript 5
- HTML5 Canvas API
- Geolocation API
- Web Workers API
…you get the idea.
Modernizr objects) and that these objects have methods (like jQuery’s
.ajax() method and Modernizr’s
addThis() method). Also, knowing how to work with closures and callbacks is key to using many of these scripts and frameworks to their fullest.
The most obvious example here is adding, removing and manipulating DOM elements with things like
cloneNode and document fragments. jQuery can help with these things but browsers can do them natively and more efficiently.
Think I left some reasons or resources out? Feel free to comment. AND NO SPAM!! I know what it looks like.