History of my Javascript (random thoughts)

Loosely coupled, well-supported and easy to use.  SailsJS really is the epitome of a NodeJS ORM/MVC framework. I ended up using SailsJS  because I expected certain standards and they delivered.

NodeJS has matured over the years and multi-core environments make it so much more awesome!

I have always tried all new technology and dabbled in:

• ASP 3.0
• XML/XSLT
• .NET
• Visual Basic
• JSP

However, I lived in Ruby land for a few years and grew through Ruby 2 and Ruby 3 and found that maintaining love for it was more pain than it was worth.  Gems and libraries died off from support, assistance was hard to find.  Ruby and Ruby on Rails as a trend became a maintenance nightmare.

These downfalls are not due to the language or framework, but due to the fact that "IT" constraints don't upgrade as fast as the development arena does. We were stuck with old software for way too long.

I worked in PHP for quite a while, Codeigniter, Symphony, Cake and Zend.   All good but somehow never felt right. Seemed like a hybrid of Perl with Java and C conventions.  Documentation was great but consistency behind usage was all over the place.  I had a good 'bout of about 10 years with PHP and just gave up as NodeJS, Dart and other JS related languages started to peak.

I turned back to my core, what I knew, and Javascript was there.  The concepts of:

• Easy to understand
• Prototyping
• Mutable objects
• Lambda support
• Asynchronous by design

... were so natural to me. Moving from frontend JS to NodeJS was so easy.

Scared by the past failures of

• jScript
• Apache Jaxer

.. server-side JS just still sounds bad. 

However, knowing Google and their V8 Engine was taking storm over the initiative was a HUGE revival!

I am very happy that I have turned back to my core knowledge as it has provided many awesome solutions.

Long live Javascript!