Building web applications: Experimenting with Node.js
I will begin by saying that I am not (yet) a web application expert or programming veteran. I am just someone who enjoys coding and thinking about how things work. My first exposure in creating web applications is with Ruby on Rails back in January 2016. I have used it since then and I built a web application with few other students for a class at Wesleyan University. I decided to experiment Node.js very recently, and I am currently still learning what it has to offer. So, please take this musings with a grain of salt, as it is just my early thoughts about Node.js and reflections of my experience of learning the framework.
It is interesting as to how during the learning process, I kept finding myself comparing the things that I do in Node.js with the equivalent commands in Rails. Writing something like,
$ express medium_demo
in the command line for a Node project is like writing,
$ rails new medium_demo
in Ruby on Rails project.
Basically what both line does is calling the Express/Rails framework to generate a directory called medium_demo, that contains all the necessary files for the web applications. It is the first thing you do when you start a Node/Ruby on Rails project.
However, there are also some commands that I wished it was also included in Node/Express framework. Ruby on Rails has this very powerful command called,
$ rake routes
I could go on with few other examples I learned thus far, but I realized this post is getting long and I’d rather keep this scribble short and sweet.