<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Node on Subhadip's Blog</title><link>https://www.subhadig.net/tags/node/</link><description>Recent content in Node on Subhadip's Blog</description><generator>Hugo</generator><language>en-us</language><copyright>Subhadip Ghosh</copyright><lastBuildDate>Sun, 02 Oct 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://www.subhadig.net/tags/node/index.xml" rel="self" type="application/rss+xml"/><item><title>My Experience with React: The Hello World</title><link>https://www.subhadig.net/posts/my-experience-with-react-the-hello-world/</link><pubDate>Sun, 02 Oct 2016 00:00:00 +0000</pubDate><guid>https://www.subhadig.net/posts/my-experience-with-react-the-hello-world/</guid><description>&lt;p&gt;I have been working on a home project these days for which I needed to use a Javascript framework on the UI. But to select a JS framework is a difficult task because there are a overwhelmingly lot to choose from. And each of those has its own strengths and flaws. Still after considering a few of them, I finally chose React. The reasons why I selected React are a) it's more Javascript-centric  than some of its close competitors which means, you write your app in JS with pieces of HTML embedded inside JS and b) it uses the Node.js and the npm ecosystem, so it's easier to grasp for somebody with prior Node experience. So I decided to learn React.js.&lt;/p&gt;</description></item><item><title>The Perfect Javascript Editor</title><link>https://www.subhadig.net/posts/the-perfect-javascript-editor/</link><pubDate>Sun, 28 Aug 2016 00:00:00 +0000</pubDate><guid>https://www.subhadig.net/posts/the-perfect-javascript-editor/</guid><description>&lt;p&gt;Being primarily a Java developer using Eclipse IDE, there are two things I always look for in any IDE - content assist/code completion and syntax checking/highlighting. While the latest version of Eclipse (Neon) has made a lot of improvements over the previous versions in terms of the JSDT plugin for Javascript developers, it's far from perfect. The syntax highlighting works upto some extent but the content assist is still very primitive if at all useful.&lt;/p&gt;</description></item><item><title>Developing Node.js with Atom Editor</title><link>https://www.subhadig.net/posts/developing-node-js-with-atom-editor/</link><pubDate>Sun, 27 Sep 2015 00:00:00 +0000</pubDate><guid>https://www.subhadig.net/posts/developing-node-js-with-atom-editor/</guid><description>&lt;p&gt;Recently I have been playing with Node.js and for every developer, getting the perfect IDE/Editor and setting up the workspace is very important. Here's how I got my set up ready:&lt;/p&gt;

&lt;p&gt;I am using Xubuntu 14.04.3 LTS. So the steps that I am going to share will work in any of the Ubuntu flavours.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. Installing Node.js:&lt;/strong&gt; Node.js is already there in the default Ubuntu 14.04 repository and the version is 0.10.25. If you need more updated version, you have 2 ways. You can either download it from the official Node.js &lt;a href="https://nodejs.org/" target="_blank"&gt;site&lt;/a&gt;, or you can follow &lt;a href="https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-an-ubuntu-14-04-server" target="_blank"&gt;this&lt;/a&gt; tutorial and add a third-party repository or use &lt;em&gt;nvm&lt;/em&gt; to get it installed. In the first case, it will not be auto-updated though. However, I chose to use the default repository version as I didn't see the point in going through all these hassle unless I specifically want a feature that is only available in the newer versions.&lt;/p&gt;</description></item></channel></rss>