<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title/><link>http://localhostblog/feed/emberjs.xml</link><description>EmberJS</description><atom:link href="http://localhost/blog/feed/emberjs.xml" rel="self"/><language>en-us</language><category>EmberJS</category><category>Django</category><category>WebDev</category><category>My2Cents</category><lastBuildDate>Fri, 11 Apr 2025 14:12:54 +0000</lastBuildDate><item><title>Stability without stagnation</title><link>https://localhost/articles/stability-without-stagnation.html</link><description>&lt;p&gt;Recently several different conversations around Django, stability, conservativism and/or breaking changes have caught my eye. Having been known a while ago in certain Python circles as &amp;quot;the Ember lady&amp;quot;, I couldn&amp;#x27;t help but draw some parallels with EmberJS and the way they have been managing releases since several years.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Disclaimer&lt;/strong&gt;: this post asks a lot of questions and provides absolutely no answer. My hope is that some of those questions might foster some fruitful discussions.&lt;/p&gt;

&lt;p&gt;For those …&lt;/p&gt;</description><pubDate>Thu, 03 Oct 2024 00:00:00 +0000</pubDate><guid>https://localhost/articles/stability-without-stagnation.html</guid><category>WebDev</category><category>Django</category><category>EmberJS</category><category>My2Cents</category></item></channel></rss>