Behind the computer science chatter about event-driven access to web servers as opposed to thread-based access and figuring out why JavaScript engines are so hot, here are some basic reasons why Node.js is hot and what it allows programmers to do.
It’s easier. It’s built to run in JavaScript, which has a huge developer base and has a warm and fuzzy community. Never underestimate the power of familiarity and friendliness.
It’s faster. We’re impatient people, as Facebook’s continued efforts to shave microseconds off load times illustrates. So, in addition to all the hardware used to speed up our servers, we’re optimizing our code not just in the application, but at the server to make things load that much faster. Much like Ajax offered a better browsing experience, Node.js offers a better web-serving experience.
It’s scalable. If you’re building a successful consumer-facing business, you’re going to eventually need a lot of servers (or a cloud provider with a lot of servers), and so whatever you plan to run on those has to be able to handle a massively distributed environment. Node.js does, which gives it an edge.
What are you building your startup or next application with? Have you given much thought about how you'll scale your solution? I ask because I see so many applications built on the wrong programming platform because the founder took the word of someone "married" to a particular programming language or given bad advice from some econ dev org. Before they know it they've blown $50K and have nothing to show for it.
No comments:
Post a Comment