I don't need to get down to bare metal but I like to have a good sense of how/why things work they way the do.
Node.js on its own is quite low level. I do recommend you spend a day playing around with the http module on its own before moving onto connect.
Express builds on top of connect so if you spend a few days playing around with connect and then "upgrade" to express you can start using express without feeling like it's doing all kinds of magic.
All express will offer you from there onwards a nice routing API and a view engine.
Possibly pertinent: I've worked with JavaScript and some libraries (jQuery, Dojo, Raphaeljs, ESRI) for a few years now so I'm not completely js uninitiated.
It's important to come into node with strong JavaScript skills because it makes the learning curve a lot more manageable. The important thing to learn is the asynchronous style of programming (and not making a mess of you code!)
Answer from Raynos on Stack OverflowI don't need to get down to bare metal but I like to have a good sense of how/why things work they way the do.
Node.js on its own is quite low level. I do recommend you spend a day playing around with the http module on its own before moving onto connect.
Express builds on top of connect so if you spend a few days playing around with connect and then "upgrade" to express you can start using express without feeling like it's doing all kinds of magic.
All express will offer you from there onwards a nice routing API and a view engine.
Possibly pertinent: I've worked with JavaScript and some libraries (jQuery, Dojo, Raphaeljs, ESRI) for a few years now so I'm not completely js uninitiated.
It's important to come into node with strong JavaScript skills because it makes the learning curve a lot more manageable. The important thing to learn is the asynchronous style of programming (and not making a mess of you code!)
I would say it's definitely worth learning node.js first. I'm learning myself and just went through this tutorial and found it very helpful...
http://nodebeginner.org
This video tutorial was pretty helpful also.
Right now I'm going through this book: Hands-On Node.js (via the PC Kindle app).
More resources in this topic.
So I wanted to learn Node.Js thoroughly and recently I’ve been learning Node.js from online tutorial and it seems they are focusing on Node.js with express.js and not Node.js alone. Is it okay to learn it with express? Or should I complete this course and later learn few other things, OR, skip this course and learn only Nodejs??????? (In my company I want to switch internally where they require Node.js developer with some exp.)
Videos
Are Express.js and Node.js the same thing?
What are some common pitfalls when using Node.js or Express.js?
Is it required to learn Node.js before diving into Express.js?
I mistakenly learned Laravel for nearly 6 months before learning vanilla PHP and don't want to make the same mistake. I know Laravel is very different to vanilla so wanted to check before focusing on Expeess whether it would screw me up.
Given that I've read express is more of a barebones framework I was hoping not, but I can't find much on YouTube that just uses base node.js
Should I learn to code in Node from scratch, or should I begin from using frameworks like Express?
And what frameworks should I use to begin?
I found Express to be very "small", more a library than a framework. It doesn't do much, but is very helpful with what it does. That means it isn't much to learn and the payoff is high.
Depends on what you're doing. If you just want to use node... it's just Javascript. Express is a framework specifically for building web-base projects in node.
I’m a self taught developer who’s new in Web development. I’m struggling to figure out what’s the best road map to learning next.js. Please I need your advice on this topic whether to learn Next js before node js or should I start learning node js before next js. Your contributions will be very helpful to me.