11–13 of 13 posts
node.js is a server framework. You should consider learning foundation and bootstrap. If you just want to go for jobs then php is the way to go otherwise you should consider learning python or ruby for web development as there are a lot of jobs for it in the field as well.
- earnest question.
I will go ahead and add some points and disagree with other points. 1. I believe that the best path is to start from the top. Start with the most user-facing side of the tech stack, the client-side. Why? Because further down the stack (esp. deployment and DBs), there are more and more modern services/libraries that abstract things away. So things like Parse, Firebase, ORMS, Heroku, hosted DBs, MongoHQ, etc. I'm not s…
1. Oh, i personally start from top, too. But the people around me tend to start from the bottom, because most of them are used to rails. You know, choose a datastore and start modeling/scaffolding right away, it's the rails way. That's why I inverted this in my post. I agree with you - the client is the most important thing to think about. When all is said and done only the client experience matters for your customer…
That being said, I personally learned node.js by starting with raw node (and the http module).
node.js is a server framework. You should consider learning foundation and bootstrap. If you just want to go for jobs then php is the way to go otherwise you should consider learning python or ruby for web development as there are a lot of jobs for it in the field as well.
How comes this is the first response to mention python and php? Is the choice really only between ruby and node.js? - earnest question.
But mentioning the near future in web development or general "app" development (typical stuff, not AAA Games and the like) in startups, there will be probably only one question:
"why not javascript?". I expect every other language/stack to fade away over time, at least for startups. However, managing legacycode will last forever and have it's jobs, too. See Cobol.
Of course, all the other coders of all the fascinating and interesting other technologies out there are pissed off by that statements. They have valid points about the ugly "design" of javascript, circumstances where it doesn't shine, and so on, and they are right. But for the majority of all technology decisions, this just won't matter.