I think if you would look around for alternatives for WebForms around the day it came out it was better than most things at the time. Java had a few horrible frameworks as well and PHP was still in it's phase of stuffing markup, database and logic in one ginormous SQL injection friendly file. The thing that was flawed about it that it was meant to work like a desktop app in WinForms style, yet the HTTP protocol isn't stateful so as soon as you would start to nest controls and route clicks, you were up for some pretty messy wiring up during different phases of loading the page.
I had an introductory course of one hour on Microsoft MVC and the next day I created and deployed a small website from scratch with it. I always basically tell people that are still on WebForms that they don't need to learn something new when they switch to MVC, they just need to forget a lot of the crap they needed to know to work on WebForms. Every day still on WebForms is a wasted day.
The writer seems to have moved from strong typed languages to loosely typed languages. It's pretty unclear to me why he quit using Django and went for JavaScript instead, but the path is pretty clear. I used and use a lot of programming languages and frameworks and I pick whatever seems the most appropriate for the job.
- WordPress for dead easy websites only doing basic stuff
- PHP/SLIM/MySQL for very simple webservices
- Django whenever I want to do a lot of custom views
- Microsoft MVC for larger web projects with a lot of business rules
Statically typed code works better in an IDE as it is easier to predict what code will do (this is one of the reasons Visual Studio with ReSharper is so effective in compile time and pre compile time error checking and refactoring).
I am not sure if I want to maintain all those Node.JS / Ruby / flavor of the month frameworks in eight years either.....probably we will curse it by then too.
I had an introductory course of one hour on Microsoft MVC and the next day I created and deployed a small website from scratch with it. I always basically tell people that are still on WebForms that they don't need to learn something new when they switch to MVC, they just need to forget a lot of the crap they needed to know to work on WebForms. Every day still on WebForms is a wasted day.
The writer seems to have moved from strong typed languages to loosely typed languages. It's pretty unclear to me why he quit using Django and went for JavaScript instead, but the path is pretty clear. I used and use a lot of programming languages and frameworks and I pick whatever seems the most appropriate for the job.
- WordPress for dead easy websites only doing basic stuff - PHP/SLIM/MySQL for very simple webservices - Django whenever I want to do a lot of custom views - Microsoft MVC for larger web projects with a lot of business rules
Statically typed code works better in an IDE as it is easier to predict what code will do (this is one of the reasons Visual Studio with ReSharper is so effective in compile time and pre compile time error checking and refactoring).
I am not sure if I want to maintain all those Node.JS / Ruby / flavor of the month frameworks in eight years either.....probably we will curse it by then too.