I’ve written a few recent articles on Node.js, mostly to familiarize myself with the effort involved in creating basic applications with it. I have yet to use it in production, mostly because I’m just not sure how ready I am to use it on a large project…
I have been quite curious with performance compared to the standard tools that I’ve used forever and ever. In the following article, I’m going to do some basic comparisons between Node and Apache2 performance.
With my recent endeavours into Node, I thought that taking a fun article like this one – CakePHP 2-0 Ajax Pagination WITHOUT The Pages – would be a really fun experiment to see how difficult it would be to accomplish in Node.
At the end of the day, the logic is still the exact same, retrieve the items, determine the max length, calculate the number of pages, and then perform AJAX as well scroll down to fill in more content as-needed.
Leveraging the Express API and Jade templates, this is quite painless to implement into Node with jQuery template.
After my first article on Node – My First Node Application – I setup and installed the Node server as well as the Express add-on package. In today’s article, I’m going to expand on that by creating actual output. In my research and comparison, Jade templates look quite nice.
Let’s be honest, anything that can simplify the mundane typing of HTML code and let me output my content faster is a win-win in my books!
Let’s get started.
I have the unique pleasure of being a technical reviewer for an upcoming book by a former co-worker of mine. Since it will be his second book on Node (his first being a co-author of Node Up and Running), I thought I should probably get a feel for using Node. I’ve of course read some of the documentation and have a thorough understand of JavaScript already, as well as event driven programming – working on some very large MMO projects.
I thought I would share how easy it is to really and truly get up and running with Node.
I truly enjoy the finer things in life. For example, if I’m going to eat a steak I don’t want some fatty low grade piece of meat. I would much rather (in this case, spend the additional money) to get an AAA grade of meat. The taste is worth it.
The same is true with development; the Twitter Timeline is “nice”, but I personally don’t want a linear, scrollable representation of my Tweets! I want the AAA grade where in this case it just takes a little bit more time instead of money… As you can see above, my Tweets are sliding in and out every 7.5 seconds. Once it cycles through my latest 10, it restarts again.