Live data from Hacker News

Why I'm Learning Node

rdegges.com

1–10 of 65 posts

Re: Why I'm Learning Node

#3

browserify ( https://github.com/substack/node-browserify ) is great for providing require() and bundling necessary dependencies for the browser.

Thank god for this - I've been doing a lot of work with some NPM packages that I want to use on the client but for the life of me couldn't figure out how to do it. This looks like it'll do just the trick. Thanks!

Re: Why I'm Learning Node

#4
The author echoes many of the same reasons I really dived into Node - I'm a strong C# back-end developer but really hadn't had much experience designing web UI (HTML5/CSS/JS.)

I can say without a doubt that my experience with Node has translated to some upside in terms of my front-end JavaScript abilities - being able to really master the ins and outs of JavaScript language itself has made it much easier for me to work with even some pretty nasty front-end bits.

In addition, you pick up a lot of tools in Node that are translatable to client-side JS development. Many of the unit testing frameworks work just as well at testing client-side code as they do server-side.

Re: Why I'm Learning Node

#5
After reading so many negative things about nodejs, I'm completely surprised to report that it is actually pretty damn cool.

Most of these negative things were (are being?) written by people who target Node's shortcomings without giving due concern to the areas it shines in.

Good Parts is definitely a good read. If anyone is looking for more reading materials on JavaScript, I had written a post about it recently: http://kishorelive.com/2012/02/23/my-javascript-reading-list...

Re: Why I'm Learning Node

#6

browserify ( https://github.com/substack/node-browserify ) is great for providing require() and bundling necessary dependencies for the browser.

Also, requirejs (http://requirejs.org) is great. It's AMD (asynchronous module definitions) based, and it's worth knowing the differences between AMD and CommonJS (which is what Browserify is based off of).

Re: Why I'm Learning Node

#7
post #5

After reading so many negative things about nodejs, I'm completely surprised to report that it is actually pretty damn cool. Most of these negative things were (are being?) written by people who target Node's shortcomings without giving due concern to the areas it shines in. Good Parts is definitely a good read. If anyone is looking for more reading materials on JavaScript, I had written a post about it recently: htt…

Thanks, this looks like a really great list. I'm adding these to my reading queue :)

Re: Why I'm Learning Node

#8
If the point is to learn front-end development, it seems like you're still sticking to your strengths instead of challenging yourself and delving into actual front-end DOM manipulation stuff.

Re: Why I'm Learning Node

#10
post #7
post #5

After reading so many negative things about nodejs, I'm completely surprised to report that it is actually pretty damn cool. Most of these negative things were (are being?) written by people who target Node's shortcomings without giving due concern to the areas it shines in. Good Parts is definitely a good read. If anyone is looking for more reading materials on JavaScript, I had written a post about it recently: htt…

Thanks, this looks like a really great list. I'm adding these to my reading queue :)

You should add Eloquent Javascript to the list really good JS books, if you haven't already read it: http://eloquentjavascript.net/
Post reply on HN