<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Front-End-Frameworks on Scholion</title><link>https://scholion.thluiz.com/tags/front-end-frameworks/</link><description>Recent content in Front-End-Frameworks on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Fri, 16 Jan 2015 09:54:57 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/front-end-frameworks/index.xml" rel="self" type="application/rss+xml"/><item><title>2015: The End of the Monolithic JavaScript Framework</title><link>https://scholion.thluiz.com/notes/2015-the-end-of-the-monolithic-javascript-framework/</link><pubDate>Fri, 16 Jan 2015 09:54:57 -0300</pubDate><guid>https://scholion.thluiz.com/notes/2015-the-end-of-the-monolithic-javascript-framework/</guid><description>The post argues that front-end development should move away from monolithic JavaScript frameworks toward smaller libraries and components, with less abstraction, more reuse, and stronger shared standards.</description></item></channel></rss>