<story><title>Four Eras of JavaScript Frameworks</title><url>https://www.pzuraq.com/blog/four-eras-of-javascript-frameworks</url></story><parent_chain><item><author>k__</author><text>A bit of history revisionism, haha&lt;p&gt;ExtJS, Ember, Angular, and Next are all &amp;quot;full-stack&amp;quot; frameworks and the all were released at very different times.&lt;p&gt;I would say the &amp;quot;eras&amp;quot; were more like:&lt;p&gt;Direct manipilation with custom architecture and models (JQuery) -&amp;gt; MVC&amp;#x2F;P (Ember&amp;#x2F;ExtJS&amp;#x2F;Angular) -&amp;gt; Components (React&amp;#x2F;Vue).</text></item></parent_chain><comment><author>pzuraq</author><text>By &amp;quot;full-stack&amp;quot; here I mean frameworks which handle both the frontend and backend simultaneously, in a seamless way. The closest thing framework that I remember from the MVC&amp;#x2F;P era which attempted this was Meteor.js, but it was really horrendous to use in my experience.&lt;p&gt;Otherwise, it was very common practice to serve an Ember or Angular app as static files Nginx or directly on a CDN. Wrapping them in a server-side framework was always a bespoke process which required you to effectively maintain two frameworks, and stitch them together yourself (unless you count Ember + Rails in the early days, but even that is a stretch IMO). When SSR was introduced in any framework, it was usually not used to its full potential to be able to accomplish the use cases I discuss in the post, like authentication, API endpoints, etc. It was just used to render the app on the server. It did not fundamentally change the DX of the framework.&lt;p&gt;I honestly was pretty skeptical of these latest frameworks until I gave them a shot! It doesn&amp;#x27;t sound that revolutionary until you actually start using them, and things which were previously quite difficult become absolutely trivial. I highly recommend trying them out some time.</text></comment>
<story><title>Four Eras of JavaScript Frameworks</title><url>https://www.pzuraq.com/blog/four-eras-of-javascript-frameworks</url></story><parent_chain><item><author>k__</author><text>A bit of history revisionism, haha&lt;p&gt;ExtJS, Ember, Angular, and Next are all &amp;quot;full-stack&amp;quot; frameworks and the all were released at very different times.&lt;p&gt;I would say the &amp;quot;eras&amp;quot; were more like:&lt;p&gt;Direct manipilation with custom architecture and models (JQuery) -&amp;gt; MVC&amp;#x2F;P (Ember&amp;#x2F;ExtJS&amp;#x2F;Angular) -&amp;gt; Components (React&amp;#x2F;Vue).</text></item></parent_chain><comment><author>magnio</author><text>That&amp;#x27;s how the article delineates it too. The term &amp;quot;Full-stack Frameworks&amp;quot; for the fourth era is a bit confusing: what the article means is the battery-included wrappers for popular component libraries like Next.js, Remix (React) or Nuxt.js (Vue) and not just any full-stack framework per se.</text></comment>