<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Is Model-View-Controller dead on the front end?</title>
	<atom:link href="http://www.epanorama.net/blog/2016/11/11/is-model-view-controller-dead-on-the-front-end/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2016/11/11/is-model-view-controller-dead-on-the-front-end/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Wed, 06 May 2026 05:46:19 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2016/11/11/is-model-view-controller-dead-on-the-front-end/comment-page-1/#comment-1523878</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Tue, 15 Nov 2016 13:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=49176#comment-1523878</guid>
		<description><![CDATA[With the popularity of React and component-based architecture, we saw the rise of unidirectional architectures for managing application state.

One of the reasons these two go so well together so well is that they cover the classic MVC approach entirely. They also provide a much better separation of concerns when it comes to building front-end architectures.

But this is no longer a React story. If you look at Angular 2, you’ll see the exact same pattern being applied, even though you have different options for managing application state like ngrx/store.

There wasn’t really anything MVC could have done better on the client. It was doomed to fail from the beginning. We just needed time to see this. Through this five-year process, front-end architecture evolved into what it is today.

Source: https://medium.freecodecamp.com/is-mvc-dead-for-the-frontend-35b4d1fe39ec#.ec4e8y4bs]]></description>
		<content:encoded><![CDATA[<p>With the popularity of React and component-based architecture, we saw the rise of unidirectional architectures for managing application state.</p>
<p>One of the reasons these two go so well together so well is that they cover the classic MVC approach entirely. They also provide a much better separation of concerns when it comes to building front-end architectures.</p>
<p>But this is no longer a React story. If you look at Angular 2, you’ll see the exact same pattern being applied, even though you have different options for managing application state like ngrx/store.</p>
<p>There wasn’t really anything MVC could have done better on the client. It was doomed to fail from the beginning. We just needed time to see this. Through this five-year process, front-end architecture evolved into what it is today.</p>
<p>Source: <a href="https://medium.freecodecamp.com/is-mvc-dead-for-the-frontend-35b4d1fe39ec#.ec4e8y4bs" rel="nofollow">https://medium.freecodecamp.com/is-mvc-dead-for-the-frontend-35b4d1fe39ec#.ec4e8y4bs</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
