JavaScript Frameworks High Level View

I'm watching the Choosing a JavaScript Framework course from @pluralsight authored by @holtbt http://pluralsight.com/courses/choosing-javascript-framework

Basically, in the video, they build a small JavaScript application in a variety of common JavaScript frameworks.

The presenter does a good job of explaining the basic details that encompass each language.  He explains the differences, the commonalities, the pros and cons, personal opinions, best practices, and industry norms.

I've only been into JavaScript frameworks for about a week now.  Working with web apps is a lot different from what I've been doing the past few years, Business Intelligence.

My goal in learning Web Programming with JavaScript, is to understand the latest trends, and how things have evolved since I programmed in classic ASP in 2000, and .net after that.

It seems to me that many of these languages are based on the MVC Model, View and Controller.  MVC is rather new to me so I won't try to explain it.

JavaScript is case sensitive.  There seem to be many editors or IDEs, including Visual Studio, however it lacks Intellisense I believe, although someone created a script for AngularJS.

A JavaScript programmer / engineer must also have a GOOD understanding of HTML.  And possibly JQuery.  And CSS.  And the DOM.  And Web Browsers.  And the Plug-Ins.  And Testing.  And Programming with Objects, like Functions, Inheritance and re-usable code.  And which tool to use when.

Watching the video, each of the frameworks offers strengths and weaknesses, some languages have common features between other languages, and some you have to write a lot of code while others have 'black magic' going on under the covers.  Sometimes its good to have the language do you favors to simplify and speed up development, although you lose some control and you have to have a good understanding of why things are happening the way they are.

Some languages you can have a working app in just a few lines of code.  Others you have to build out the structure and write a lot of code before you can start the app.

What I remember from JavaScript way back when, it was always tough to troubleshoot errors.  I think that has gotten better over time, but it seems that when an error is thrown, it doesn't give a specific reason why it failed, so there's some pain involved.

I don't think we had Intellisense in Classic ASP, so that's a good feature to have, because the code is wired up all over the place and I wouldn't call it spaghetti, but having the IDE assist in writing code is always a good thing.

I'm not sure exactly how one would host a JavaScript application.  For example, if I wanted to host an application on my own, and had to find a hosting company, I wouldn't know where to look.  I spoke with another programmer and he said he can host a .net app for about $5 a month, but said if he wanted to host an Angular app, his option would be Azure and he didn't have an account.

I did a sample Angular application in Visual Studio 2013 and uploaded to my Azure account and blogged about it here.

Overall, I think it's a cool technology.  I can see why so many developers are programming in JavaScript.  I know more than last week.  There's a lot to know with all the different flavors.  If I get a chance to work with this technology in the future, great.  If not, at least I have enough knowledge to know the basics.

And there you have it~!