[lunaru]

Agree. It seems the OP is just moving from one language to another rather than from one domain (back-end) to another (front-end).

If you're learning JavaScript to get familiar with front-end and UI, Node.js is just a distraction. Instead, my advice is to learn raw HTML/CSS/JS without frameworks.

You know those cheesy web-based "OSes"/Desktops that no one really uses? Building one is actually quite helpful to developing JavaScript skills. Try building a Window manager in HTML/CSS/JS. You'll go through the entire gauntlet of what JavaScript has to offer (e.g. closures, prototypes) while dealing with a practical front-end problem (DOM manipulation, CSS styling) while learning a lot about why the modern js frameworks are so useful (e.g. jQuery for DOM, backbone.js for MVC). You'll also start getting exposure to some basic decisions that make up the foundations of a good UI sense. I consider this sort of exercise much more appropriate for polishing front-end skills.

Other possible exercises include re-implementing common jQuery UI components - drop-down menus, trees, tabs, etc. But do them without jQuery. It might sound like reinventing the wheel, but learning fundamentals sometimes requires retreading worn out paths.

[4as198sGxV]

Sure. Then he will want to kill himself when trying to use of all those inferior and mismatched technologies for any kind of complex application (achieving crossbrowser support will ensure many nights of fun!). He will then go back to coding server-side where at least you can use sane language and tools so you can be as productive as possible. However, he will be thinking about this glimpse of hell for the rest of his career.