Wow! I can’t believe 2013 is coming. It seriously feels just the other day when I sat down and wrote my 2011 year in review…
Thinking back, 2012 is probably a more average year. I don’t feel like anything new and major really happened in the industry that I was a part of. However, in my personal life, I welcomed my third child in late October – hence the lack of website updates since I’ve been extremely busy with my growing family. (more…)
This is a quick follow up to yesterday’s post on Node.js Versus Apache2: Bare Bones Test where I performed a straight HTML test of Node.js tutorial versus Apache. With my recent switch to Nginx, I thought it prudent to perform this exact same test swapping out Apache for Nginx. The results are much more interesting to yesterday’s since there is no total destruction (sorry for the spoiler if you didn’t read yesterday’s article).
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.
This might be a boring refresher for some people; however, I think it’s important from time-to-time to go back and visit the basics. CSS can provide a lot of power to a web developer (or designer), but when used improperly it can cause a lot of headaches.
When using CSS, like doing on development, it’s important to stop and think about what you are doing and more importantly, what’s the easiest way to accomplish it!
Let’s start with understanding the acronym behind CSS – it stands for Cascading Style Sheets. Cascading, being the very important word to understand. This means that the base styles you define will carry throughout (or cascade) all of your design unless a specific style is overridden.
I’m going to begin by demonstrating how I typically begin creating a style sheet.
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.