[iSoron]

I see it as a pendulum. In the old times, we used to write web applications in CGI, where there was no fixed structure whatsoever; the application programmer was responsible for creating the entire web stack with their own bare hands. Then the pendulum started swinging towards more structured frameworks and reached a peak with J2EE, where the application programmer only had to write a tiny piece of code (servlet) that went into a massive framework (servlet container), in a language that had a huge standard library (Java), following clear industry standards (e.g. JavaBeans, design patterns). By the time Rails appeared, the pendulum had started swinging back towards less structure and less formalism. Rails was still a framework, with a strong set of conventions, but it was quite simplified compared to J2EE. The pendulum then continued and people switched to Node.js, which was much more barebones and flexible than Rails. Right now, the pendulum seems to be reaching the opposite extreme with Go, where not only there isn't a framework, but there also isn't a virtual machine (everything is compiled to native code), the language itself is almost as simple as C, and there is barely any standard library.

[pjmlp]

Meanwhile those of us on the JVM/CLR ecosystems, saw it come, influence of some the JEE/Spring/MVC designs, Groovy, coming and going as IronRuby, influence CoffeScript, and eventually fade away we still keep using JVM/CLR ecosystem, and the savy ones will even know how to AOT compile our applications, if needed.