<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Paul Falgout on Medium]]></title>
        <description><![CDATA[Stories by Paul Falgout on Medium]]></description>
        <link>https://medium.com/@paulfalgout?source=rss-62d971d6ce16------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-WJ77FFZDOAU4jJ4.</url>
            <title>Stories by Paul Falgout on Medium</title>
            <link>https://medium.com/@paulfalgout?source=rss-62d971d6ce16------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:38:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paulfalgout/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introducing Marionette 5]]></title>
            <link>https://medium.com/blog-marionettejs/introducing-marionette-5-0e6ecd087f8c?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e6ecd087f8c</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 00:00:25 GMT</pubDate>
            <atom:updated>2026-10-13T13:00:39.106Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://marionettejs.com/news/">← News</a></p><p>Marionette 5.0.0 is here: an independent core, flexible integrations, and tools to help your agent work with it. Maintainer Paul Falgout talks with dot about why he came back to v5 and what they’ve tried with it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hrqYeJn6__Wdu8Y6GaemkQ.png" /></figure><h3>How did those reasons land with you?</h3><p>Those arguments still have some value. But they seemed to assume a human would be doing most of the implementation. I wanted to know how their value might change when agents were doing more of that work.</p><h3>What did they think?</h3><p>I deliberately didn’t ask ChatGPT, which was my daily driver. I didn’t want its familiarity with my preferences to influence the answer. The responses from Claude Opus 4.7 and Gemini 3.5 were positive about Regions, predictable lifecycles, knowing who owns and cleans up each piece, and keeping application state separate from presentation. Claude’s was more qualified; Gemini’s favored that architectural fit over React or Vue. They disagreed on things like message buses and reactivity, but both saw real value in the architecture and wanted it modernized.</p><p>That encouragement is why I picked v5 back up. It was an idea worth trying in real applications. That, and OpenAI gave me six months free on their $200-a-month plan.</p><p>That gives an agent a place to make a change, and you a way to review its consequences.</p><h3>How did you decide what to change?</h3><p>The human ergonomics of the code were about code review and not saving keystrokes. So I would bring questions about what to keep or change to multiple agents until there was some sort of consensus.</p><h3>What can an agent use to work with that?</h3><p>The package includes version-matched docs and a Marionette skill that points an agent to the installed API. Its local helper can look up a symbol, a documentation section, or a diagnostic code. There are TypeScript declarations and an ESLint rule for catching use of private framework members, too. <a href="https://marionettejs.com/docs/agents/">Work with an agent →</a> · <a href="https://marionettejs.com/docs/tooling/">Application tooling →</a></p><h3>What have you tried with it?</h3><p>The results have been surprising. Agent-led development seems to work, and the applications have performed well against their peers.</p><p>In <a href="https://github.com/marionettejs/marionette-realworld-example-app">RealWorld</a>, an agent built Conduit, a blogging frontend, then refined it through review and follow-up requests. In the simulated-mobile benchmark, median article navigation was 175 ms for the measured v5 build versus 425 ms for Vue, across ten samples per app. <a href="https://marionettejs.com/case-studies/realworld/#comparison">Read the RealWorld measurements →</a></p><p>The Vikunja Vue migration measurements show another encouraging result: median rich-task opening was 1.04 seconds for the measured v5 build versus 3.72 seconds for Vue. That’s 72% shorter across 20 samples per app in desktop Chromium, using production builds and a 500-task fixture with 50 comments on the opened task. <a href="https://marionettejs.com/case-studies/vikunja/#journey">Read the Vikunja measurements →</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hBP5gKuiZXbuOiwu.png" /></figure><h3>Try it in your project.</h3><p>Try v5 on a small feature. Start with the quick start for a new project, or the migration guide for an existing Marionette app.</p><p><em>Originally published at </em><a href="https://marionettejs.com/news/introducing-marionette-5/"><em>https://marionettejs.com</em></a><em> on October 10, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e6ecd087f8c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-marionettejs/introducing-marionette-5-0e6ecd087f8c">Introducing Marionette 5</a> was originally published in <a href="https://medium.com/blog-marionettejs">Marionette.js blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marionette v4.1 Released]]></title>
            <link>https://medium.com/blog-marionettejs/marionette-v4-1-released-3ef3fab5cde7?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ef3fab5cde7</guid>
            <category><![CDATA[backbonejs]]></category>
            <category><![CDATA[jquery]]></category>
            <category><![CDATA[marionettejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Sat, 20 Apr 2019 16:27:17 GMT</pubDate>
            <atom:updated>2019-04-20T19:41:21.634Z</atom:updated>
            <content:encoded><![CDATA[<p>Paving the way forward.</p><p>We’ve released the latest version of Marionette: 4.1! This release mainly fixes a few issues we found in Marionette 4 (special thanks to <a href="https://github.com/taburetkin">taburetkin</a>!) and provides official support for Backbone 1.4. You can find the full details in the <a href="https://github.com/marionettejs/backbone.marionette/blob/master/changelog.md">changelog</a>.</p><h4>The road ahead</h4><p>So what’s next for Marionette? There are two main areas Marionette is looking to address. The first is to continue improving our rendering strategy. Since v2, Marionette has made <a href="https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts-results/table.html">major strides</a> towards a modern rendering strategy. While Marionette can currently compete with modern frameworks, there are areas to improve the available tools and strategies for accomplishing a fast and easy to maintain solution. Expect some modifications to Marionette.Region related to these goals in upcoming releases.</p><p>Similarly the second area we’ll be addressing is dependencies. Both jQuery and Backbone are dependencies of Marionette, but currently with some effort, jQuery can be removed. Marionette has always fallen on the side of being minimally opinionated and has continued to scale back opinions, leaving options open for the developer to make the best decision for their project. It is a goal that both jQuery and Backbone eventually become opt-in rather than opt-out as dependencies. We certainly don’t want to drop support for Backbone, and hope to make any changes minimal for current projects. However there are currently many data and routing solutions available, and you should be able to choose which works best.</p><h4>We need your help!</h4><p>Marionette could not continue without the support of the community. Please share your experiences with this new version or ways things can improve in <a href="https://gitter.im/marionettejs/backbone.marionette">Gitter</a>, or if you run into a problem, <a href="https://github.com/marionettejs/backbone.marionette/issues">open an issue on Github</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XtKdE2crjH4-OJi1UEQbvg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ef3fab5cde7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-marionettejs/marionette-v4-1-released-3ef3fab5cde7">Marionette v4.1 Released</a> was originally published in <a href="https://medium.com/blog-marionettejs">Marionette.js blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marionette.js v4 — Getting started with the new version]]></title>
            <link>https://medium.com/blog-marionettejs/marionette-js-v4-getting-started-with-the-new-version-4e5d88cea975?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e5d88cea975</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[marionettejs]]></category>
            <category><![CDATA[backbonejs]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Mon, 06 Aug 2018 08:08:55 GMT</pubDate>
            <atom:updated>2018-08-06T08:08:55.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XRqMoDmWdrVHMLIclhdwQg.png" /></figure><p>The Marionette library is now over 6 years old, and our goal is still the same. Marionette aims to be <strong>approachable</strong> with a small, easy to understand API. The core team has been working hard to fulfill the promise of iterative and incremental updates. For those keeping up with deprecations and experimental API this should be an easy transition. For others the transition should still be fairly straightforward and is well documented.</p><p><strong>For the v3-v4 upgrade guide:</strong><br><a href="https://marionettejs.com/docs/v4.0.0/upgrade-v3-v4.html">https://marionettejs.com/docs/v4.0.0/upgrade-v3-v4.html</a></p><p><strong>For v4 documentation:</strong><br><a href="https://marionettejs.com/docs/v4.0.0">https://marionettejs.com/docs/v4.0.0</a></p><h4>Accomplishments</h4><p>The new release comes with a <strong>simplified API and performance gains</strong>. To demonstrate the performance of v4 we utilize the js-framework-benchmark. The interactive results table is available here: <a href="https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts-results/table.html">https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts-results/table.html</a></p><p>We currently test against two scenarios. One uses jQuery with underscore templates which is certainly the slower of the options, but those solutions come free with Backbone. The other uses Marionette’s new renderer API and a custom DOM template to produce results outpacing most all of the modern popular frameworks. It is unlikely anyone would write custom DOM templates for their entire project, but this shows the range of Marionette. Any number of rendering and templating solutions can be used with Marionette to produce performance keeping up with other modern solutions. With Marionette you can even mix-and-match choosing to hyper-optimize even a single view for a hot route if necessary.</p><p>Here is a snapshot of the results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rlr7lTFW_7016Upju0LN4Q.png" /><figcaption>Speed tests in context of other popular frameworks (Columns 3 and 8)</figcaption></figure><p>Notably Marionette and its dependencies have a smaller byte weight and memory footprint than the libraries in close comparison.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BE13AKYJQ34iQErPxenIHA.png" /><figcaption>(Columns 3 and 8)</figcaption></figure><h3>Major Changes</h3><p>With v4 came a few major changes:</p><h4>New CollectionView</h4><p>TheNextCollectionView, introduced in v3.3, was renamed CollectionView replacing both the previous CollectionView and CompositeView.</p><p><a href="https://medium.com/blog-marionettejs/next-collection-view-d335f5a9736a">A New Refined CollectionView for Marionette.js</a></p><h4>AppRouter was extracted</h4><p>Marionette no longer has an opinion on routers however developers were always free to choose alternatives to AppRouter. AppRouter was extracted to its own library and can certainly still be used if one so chooses.</p><p><a href="https://github.com/marionettejs/marionette.approuter">https://github.com/marionettejs/marionette.approuter</a></p><h4>Renderer class was removed and TemplateCache was extracted</h4><p>Setting a view class renderer is easier than ever and as such the original global v2-style renderer was removed as was the TemplateCache library which read and cached templates from the DOM. TemplateCache was extracted and can still be used as Marionette’s renderer or as part of a custom renderer.</p><p><a href="https://github.com/marionettejs/marionette.templatecache">https://github.com/marionettejs/marionette.templatecache</a></p><p>Read more on renderers here:</p><p><a href="https://medium.com/blog-marionettejs/going-virtual-or-incremental-with-marionette-js-1a38837cc1be">Going virtual or incremental with Marionette.js</a></p><h4>Looking forward</h4><p>Browsing the open issues on the Marionette repo, a clear candidate for improvement is Region. Expect to see some reform and improvements to regions in upcoming versions.</p><p>Perhaps the most important goal is that we plan to support our <strong>community</strong> as best as we can. The Marionette community has been excellent at supporting each other and building content to improve the ecosystem.</p><p><a href="https://gitter.im/marionettejs/backbone.marionette">Come chat with us</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e5d88cea975" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-marionettejs/marionette-js-v4-getting-started-with-the-new-version-4e5d88cea975">Marionette.js v4 — Getting started with the new version</a> was originally published in <a href="https://medium.com/blog-marionettejs">Marionette.js blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marionette v4 beta]]></title>
            <link>https://medium.com/blog-marionettejs/marionette-v4-beta-ebfaa67872c0?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebfaa67872c0</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[backbonejs]]></category>
            <category><![CDATA[marionettejs]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Mon, 23 Jul 2018 13:34:53 GMT</pubDate>
            <atom:updated>2018-07-23T13:35:38.659Z</atom:updated>
            <content:encoded><![CDATA[<p>The new version is on it’s way here and is a simpler API with plenty of performance improvements. We’ll be hard at work testing it in the wild during the beta, but unless anything surprising comes up, expect a full release in the coming weeks. Also watch a more in-depth blog post of the changes with the full release.</p><p><strong>For v4 documentation:</strong><br><a href="https://github.com/marionettejs/backbone.marionette/blob/v4-beta/docs/installation.md">https://github.com/marionettejs/backbone.marionette/blob/v4-beta/docs/installation.md</a></p><p><strong>For the v3-v4 upgrade guide:</strong><br><a href="https://github.com/marionettejs/backbone.marionette/blob/v4-beta/docs/upgrade-v3-v4.md">https://github.com/marionettejs/backbone.marionette/blob/v4-beta/docs/upgrade-v3-v4.md</a></p><h4>We need your help!</h4><p>Marionette could not continue without the support of the community. Please share your experiences with this new version or ways things can improve in <a href="https://gitter.im/marionettejs/backbone.marionette">Gitter</a>, or if you run into a problem, <a href="https://github.com/marionettejs/backbone.marionette/issues">open an issue on Github</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XtKdE2crjH4-OJi1UEQbvg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebfaa67872c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-marionettejs/marionette-v4-beta-ebfaa67872c0">Marionette v4 beta</a> was originally published in <a href="https://medium.com/blog-marionettejs">Marionette.js blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marionette v3.5 Released]]></title>
            <link>https://medium.com/blog-marionettejs/marionette-v3-5-released-6734f4aea4e0?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/6734f4aea4e0</guid>
            <category><![CDATA[javascript-frameworks]]></category>
            <category><![CDATA[backbonejs]]></category>
            <category><![CDATA[marionettejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Sun, 05 Nov 2017 13:37:03 GMT</pubDate>
            <atom:updated>2017-11-05T13:37:03.286Z</atom:updated>
            <content:encoded><![CDATA[<p>Getting ready for Marionette v4</p><p>The Marionette community is approaching a release candidate for a version 4 release. Along the way we learned of some issues that would be best resolved in v3. Namely these changes are improvements to NextCollectionView, fixes for Behavior related events, and an easier way to clean up bound events and requests. Further details can be found in the <a href="https://github.com/marionettejs/backbone.marionette/blob/master/changelog.md">changelog</a>.</p><p>Be on the look out for a follow up post detailing the changes coming in v4.</p><h4>We need your help!</h4><p>Marionette could not continue without the support of the community. Please share your experiences with this new version or ways things can improve in <a href="https://gitter.im/marionettejs/backbone.marionette">Gitter</a>, or if you run into a problem, <a href="https://github.com/marionettejs/backbone.marionette/issues">open an issue on Github</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XtKdE2crjH4-OJi1UEQbvg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6734f4aea4e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-marionettejs/marionette-v3-5-released-6734f4aea4e0">Marionette v3.5 Released</a> was originally published in <a href="https://medium.com/blog-marionettejs">Marionette.js blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[!Do Action({ option: ‘repeat’}) Person.extend(constructor(){ this.me = true; this._super(); })]]></title>
            <link>https://medium.com/hackernoon/do-action-option-repeat-person-extend-constructor-this-me-true-this-super-6ca705ec7520?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ca705ec7520</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[repeat-myself]]></category>
            <category><![CDATA[all-of-the-time]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[do-action]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Fri, 18 Aug 2017 06:52:14 GMT</pubDate>
            <atom:updated>2019-09-27T05:51:43.901Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or why I purposely repeat myself all of the time.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1vgunpShn0YZt6IfUKfoRQ.jpeg" /></figure><p>I was recently working on a project with a developer who held a very dogmatic view of enforcing the DRY principle (Don’t Repeat Yourself). Personally I think perfectly DRY code is brittle, hard to understand, and hard to maintain. I’m certainly not the first to suggest this, but I prefer repetition to abstraction in many cases.</p><h4>Conflicting Principles</h4><p>At what point does DRY help with creating good architectural patterns? First I think it is important to consider that using the term “architectural pattern” indicates a certain level of repetition. Patterns are good! If all code was entirely unique, all code would have to be learned and understood on its own. Instead if code follows very similar patterns, learning it in one place, leads to understanding in all of its other cases. It is less useful to abstract code so that a pattern is only used once. At that point it ceases to be much of a pattern.</p><h4>Understanding DRY Caveats</h4><p>A DRY zealot is going to produce functions or classes that require vast amounts of understanding to know what that function or class can do. This is because in order to use a particular logic pattern, a function or class must account for all of its various use cases. With overDRYing, options and arguments will abound, and responsibility and complexity will increase over time.</p><h4>A Broader View of DRY</h4><p>Thus I think in order for the DRY principle to be useful it must be more broadly considered. While I think abstracting sound patterns and understandable code is a poor use of DRY, I think that architecting code such that business logic only occurs in one place <em>is</em> important. If a behavior of your product changes, you want to be able to address that behavior in a single location, and not in all of the places you can remember across the app. This means if you are regularly modifying data to display it a particular way, make sure you’re doing that in one place, but apply DRY to the business logic itself, and not to <em>how</em> the business logic is being modified.</p><p>For instance you might find that you are consistently filtering a list of products a particular way in various places of your app. It would be best to make sure this is done in one place in code. However if you also find that you are filtering your users in a similar way, it may not be and is probably not in your best interest to make a generic filter that handles both products and users, as when the use case for either products or users change, your DRYness becomes an issue. Not to mention once you’ve added five other entities to the same generic filter solution, changes to the filter may have broad, potentially difficult to fully understand, implications across your app instead of on a singular entity.</p><h4>Apply When Needed</h4><p>Finally I think one of the more important aspects of DRY to consider is that you should only use it if you find you are already repeating, or are about to repeat, yourself. Spending time and energy pre-DRYing code is inefficient and destined for refactoring. It is much harder to guess at future use cases with perfect code than it is to handle them with code that is easy to modify. If I’ve learned anything in years of development, it is that I’m wrong a lot, and it is easier to plan for that than to improve my ability to understand the future.</p><p><strong>Simply put: Don’t DRY until you repeat yourself. aka: DDRYUYRY.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ca705ec7520" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/do-action-option-repeat-person-extend-constructor-this-me-true-this-super-6ca705ec7520">!Do Action({ option: ‘repeat’}) Person.extend(constructor(){ this.me = true; this._super(); })</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marionette v3.4 Released]]></title>
            <link>https://medium.com/blog-marionettejs/marionette-v3-4-released-a07d193ea88c?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/a07d193ea88c</guid>
            <category><![CDATA[backbonejs]]></category>
            <category><![CDATA[marionettejs]]></category>
            <category><![CDATA[jquery]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Sat, 05 Aug 2017 06:50:01 GMT</pubDate>
            <atom:updated>2017-08-08T16:04:31.051Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/177/1*yM1YdaJWcvUXzddJAr4w6A.png" /></figure><ul><li>Now exporting an ES6 module</li><li>A DOM API added as a method for replacing how Marionette deals with the DOM.</li><li>Features and improvements added to NextCollectionView</li></ul><h4>Exporting ES6</h4><p>As of the v3.4 release module bundlers that support the <a href="https://github.com/rollup/rollup/wiki/pkg.module">“module” key</a> of package.json may import an ES6 module build of Marionette. This better allows for tree-shaking (though there is <a href="https://github.com/marionettejs/backbone.marionette/pull/3393">more to do</a> there) and removes the need for a UMD wrapper.</p><p><strong><em>edit: </em></strong><em>The ES6 module was a breaking change for some builds. The ES6 module will still be built and shipped with v3.4.1, but the “module” key will be removed from </em>package.json <em>until the feature is fully flushed out for v4. To use the ES6 module, aliasing or importing from the </em>node_module<em> folder will be required.</em></p><h4>DOM API — or the path to replacing jQuery</h4><p>Say what you want about jQuery, but there are certainly faster ways in dealing with the DOM, particularly when dealing with large CollectionViews. By default Marionette uses jQuery to interface with the DOM and though there have always been ways to replace these interactions, the DOM API provides an easier method for modifying these interactions per view prototype.</p><p>In combination with the setRenderer API introduced in v3.3, we hope that it will be easy to customize performant rendering for the whole app or even per view. For more on alternate rendering strategies, read <a href="https://medium.com/blog-marionettejs/going-virtual-or-incremental-with-marionette-js-1a38837cc1be">Going virtual or incremental with Marionette.js</a>, and anticipate further updates here on the blog discussing additional strategies. Before moving onto the next feature a DOM API that could replace jQuery may look like this:</p><pre>const DomApi = {<br>  getEl(selector) {<br>    if (_.isObject(selector)) return [selector];</pre><pre>    return document.querySelectorAll(selector);<br>  },</pre><pre>  findEl(el, selector) {<br>    return el.querySelectorAll(selector);<br>  },</pre><pre>  detachEl(el) {<br>    if (el.parentNode) el.parentNode.removeChild(el);<br>  },</pre><pre>  hasContents(el) {<br>    return el.hasChildNodes();<br>  },</pre><pre>  setContents(el, html) {<br>    el.innerHTML = html<br>  },</pre><pre>  appendContents(el, contents) {<br>    el.appendChild(contents)<br>  },</pre><pre>  detachContents(el) {<br>    while (el.firstChild) {<br>      el.removeChild(el.firstChild);<br>    }<br>  }<br>};</pre><pre>Marionette.setDomApi(DomApi);</pre><p>It can also be applied to singular view prototype</p><pre>const MyView = Marionette.View.extend({...});</pre><pre>MyView.setDomApi(DomApi);</pre><h4>NextCollectionView Improvements</h4><p>Also introduced in v3.3 NextCollectionView <a href="https://medium.com/blog-marionettejs/next-collection-view-d335f5a9736a">was added</a> as a possible replacement candidate for the current CollectionView in an upcoming major version. It is currently being vetted and battle tests and from user feedback and benchmarks v3.4 will include additions and improvements to NextCollectionView. Among some general performance improvements the following changes were made:</p><ul><li>swapChildViews was added for an easy interface for changing the placement of two children within a CollectionView.</li><li>viewComparator: false was added for disabling the sort functionality when not needed. By default the sort is kept in sync with the order of the Backbone collection.</li><li>An improvement was made to avoid unnecessary calculations if children are added to the end of an existing CollectionView.</li><li>attachHtml which is overridable by the user used to receive the instance of the CollectionView as the first argument. This argument was originally added to the CollectionView to support the CompositeView. As NextCollectionView is listed as an experimental API, we removed this unnecessary argument to simplify the API.</li></ul><h4>Other notable updates</h4><p>What might be considered an advanced flag, monitorViewEvents was added to all of the Marionette View prototypes. Essentially if set to false Marionette will no longer trigger attach/detach or dom:refresh/dom:remove events for that view <em>or any of its children. </em><strong>Use this flag with care!</strong> This flag may be useful in cases where very large numbers of views need to be added or removed at once and extra attention is needed to improve rendering or view destruction.</p><p>Additionally, Backbone.Radio is no longer needed by the UMD wrapper. While Radio is still listed as a dependency, in the case where you are simply loading Marionette via a script tag (say for instance on codepen or jsfiddle) you do not need to load Radio unless you intend to use the radioEvents interface.</p><h4>We need your help!</h4><p>Marionette could not continue without the support of the community. Please share your experiences with this new version or ways things can improve in <a href="https://gitter.im/marionettejs/backbone.marionette">Gitter</a>, or if you run into a problem, <a href="https://github.com/marionettejs/backbone.marionette/issues">open an issue on Github</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XtKdE2crjH4-OJi1UEQbvg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a07d193ea88c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-marionettejs/marionette-v3-4-released-a07d193ea88c">Marionette v3.4 Released</a> was originally published in <a href="https://medium.com/blog-marionettejs">Marionette.js blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Marionette v3.3 Released]]></title>
            <link>https://medium.com/blog-marionettejs/marionette-v3-3-released-415883a6da87?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/415883a6da87</guid>
            <category><![CDATA[backbonejs]]></category>
            <category><![CDATA[javascript-frameworks]]></category>
            <category><![CDATA[marionettejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Wed, 03 May 2017 14:02:31 GMT</pubDate>
            <atom:updated>2017-05-06T13:22:42.913Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/177/1*610TNhfATVz8H2UNldHZzA.png" /></figure><ul><li>Region better supports animation</li><li>NextCollectionView a possible CollectionView replacement</li><li>Customize the View renderer per View prototype</li></ul><p>With this new version of Marionette comes many new features. We’ll briefly cover some of them here. Be sure to check the <a href="https://marionettejs.com/updates/">changelog</a> for a full list of changes.</p><h4>Region Animation</h4><p>While there are animation solutions out there for Regions, in v3.3 efforts were made to make adding transitions easier. It should now be easier to understand the state of the view in the region by checking isSwappingView.</p><p>Additionally removeView and destroyView were added so that a transition could be added cleanly within the Region API.</p><pre>var AnimatedRegion = Mn.Region.extend({<br>  attachHtml: function(view) {<br>    view.$el<br>      .css({display: &#39;none&#39;})<br>      .appendTo(this.$el);<br>    if (!this.isSwappingView()) view.$el.fadeIn(&#39;slow&#39;);<br>  },<br><br>  removeView: function(view) {<br>    var self = this;<br>    view.$el.fadeOut(&#39;slow&#39;, function() {<br>      self.destroyView(view);<br>      if (self.currentView) self.currentView.$el.fadeIn(&#39;slow&#39;);<br>    });<br>  }<br>});</pre><p>See this <a href="http://codepen.io/blikblum/pen/PppGmG">codepen</a> for the proof-of-concept for this addition.</p><h4>NextCollectionView</h4><p>In order to improve issues with the current CollectionView breaking changes needed to be made. Instead of iteratively releasing breaking changes along with major versions, we are trying a different approach of introducing an improved view along side the current one. This will allow the community to test and improve the new view in the real world prior to replacing the current view. A more detailed explanation of the changes are available in an another blog post.</p><p><a href="https://medium.com/blog-marionettejs/next-collection-view-d335f5a9736a">https://medium.com/blog-marionettejs/next-collection-view-d335f5a9736a</a></p><h4>Setting a Custom Renderer</h4><p>Overriding the Marionette renderer has never been complicated, but using the new interface Marionette.View.setRenderer allows for further simplification by providing an easy interface for importing 3rd party or custom renderers and allowing the renderer to be defined per view definition.</p><pre>// Hypothetical solution<br>import IDomRender from &#39;marionette-idom&#39;;<br>Marionette.View.setRenderer(IDomRender);</pre><pre>var MyExtendedView = Marionette.View.extend({ ... });<br>MyExtendedView.setRenderer(function(template, data) {<br>  return MyTemplateRenderer(template, data);<br>});</pre><p>While you may not modify the renderer now in your app, our hope is that new renderers will provide easy ways to increase performance or add functionality in the future.</p><h4>Other notable updates</h4><p>An onDomRemove event was added as a convienent place to do any necessary clean up for things added inside a View’s onDomRefresh. Previous to this event both onBeforeRefresh and onBeforeDetach would have been needed to adequately clean up some situations. Look for a future blog post where we go into further details on the view lifecycle events and related best practices.</p><p>A <a href="https://marionettejs.com/docs/master/marionette.features.html">feature flag</a> was added ( childViewEventPrefix ) for changing the prefix from the default &quot;childview&quot; to false. In v3.2 the prefix could be set to false to prevent the view auto-proxying all events from child to parent. To prevent many unlistened events this feature flag should be set to false and this may be the default setting in an upcoming major version of Marionette. Note that setting this flag does not prevent changing the prefix on any individual view.</p><h4>We need your help!</h4><p>Marionette could not continue without the support of the community. Please share your experiences with this new version or ways things can improve in <a href="https://gitter.im/marionettejs/backbone.marionette">Gitter</a>, or if you run into a problem, <a href="https://github.com/marionettejs/backbone.marionette/issues">open an issue on Github</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h3ID2YYpwvn8e-kzMZlY8g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=415883a6da87" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-marionettejs/marionette-v3-3-released-415883a6da87">Marionette v3.3 Released</a> was originally published in <a href="https://medium.com/blog-marionettejs">Marionette.js blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A New Refined CollectionView for Marionette.js]]></title>
            <link>https://medium.com/blog-marionettejs/next-collection-view-d335f5a9736a?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/d335f5a9736a</guid>
            <category><![CDATA[marionettejs]]></category>
            <category><![CDATA[backbonejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Mon, 01 May 2017 01:34:40 GMT</pubDate>
            <atom:updated>2017-05-10T18:03:10.533Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*67j3ZP2cAbAmlKfoZ9DAVg.jpeg" /></figure><p>In version 3.3 of Marionette, we will be introducing the <a href="https://github.com/marionettejs/backbone.marionette/pull/3244">Marionette.NextCollectionView</a> along side the current CollectionView. This new CollectionView will bring better performance along with a more consistent API, and in doing so it includes some breaking changes and introduces a lot of new code that needs to be battle tested in the real world. So introducing it alongside the current CollectionView allows developers to gradually try it and migrate prior to needing to move to it in an upcoming major release.</p><p>The goals behind this change fall into three major categories:</p><ul><li>There should be one method and logic flow for doing something.</li><li>The CollectionView should be more concerned with the child views than the collection models.</li><li>The API should be intuitive and consistent</li></ul><h3><strong>One logic flow</strong></h3><p>Backbone v1.3 released a substantial feature when it included an update event on the collection which is described by backbonejs.org as a, “single event triggered after any number of models have been added or removed from a collection.” Previous to this release a developer was given two options, reset the collection, which in Marionette would re-render the entire CollectionView, or let Marionette add and remove changed views one at a time, each time determining where a view should be inserted or removed in the DOM. If Marionette knew it was re-rendering the entire CollectionView it would create a document fragment to build the DOM within before inserting it all at once, but inserting one at a time made it such that we needed two different ways to render. Thus the current CollectionView contains both an attachBuffer and an attachHtml. Though Marionette was able to utilize the update event to improve performance in <a href="https://github.com/marionettejs/backbone.marionette/pull/3113">some</a> <a href="https://github.com/marionettejs/backbone.marionette/pull/3105">cases</a>, in others it was <a href="https://github.com/marionettejs/backbone.marionette/pull/3173">difficult</a> if not <a href="https://github.com/marionettejs/backbone.marionette/issues/2723">impossible</a> without introducing breaking changes. This complexity introduced added issues when combined with sorting and filtering. An added feature had so many edge-case issues because there were multiple ways to add or remove views, some related to the collection and some not.</p><p>So we introduced a simplified logic flow. Regardless of how a child is added or removed, the same logic flow is used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*csq3DgiS_KmY7aSznhihHw.png" /></figure><p>This means that any view added to the DOM by a collection will be added via the same attachHtml method. It also means that each child view will only be instantiated and rendered if it <em>has</em> to be. Outside of removing and re-adding a model to a collection, a child view will only be rendered by the CollectionView one time (assuming it isn’t pre-rendered), no matter what action you take. Currently the CollectionView will heavy handedly destroy and reinitialize all of its children in many cases such as <a href="https://github.com/marionettejs/backbone.marionette/issues/2829">if any models are added when the CollectionView’s </a><a href="https://github.com/marionettejs/backbone.marionette/issues/2829">reorderOnSort optimization is set to true</a>.</p><h3>Concerning Views</h3><p>Marionette’s current CollectionView has a precarious relationship with its collection. In theory the API would suggest, and in many cases is designed such, that you do not need a collection to use the view. A collection is merely one way (and perhaps the primary way) to manage the views in a CollectionView. However as the CollectionView progressed, some features focused more specifically on the CollectionView’s relation to the collection’s underlying models. The biggest example of this is probably filter.</p><p>When filtering a CollectionView currently the view iterates over this.collection.models to filter which views should be included in the children. With this approach, views added outside of the collection whether they have a model or not are never considered by the filter. To further complicate things, models are filtered prior to constructing the children. At first this may not seem like a big deal, but after this point if a model is inserted into the original collection, everything must be reconstructed as the inserted index has no real context with the already filtered children.</p><p>In the NextCollectionView the children are determined <em>first</em>. Then sorting and filtering iterate over the children by view and not model. Views that are filtered out are merely detached instead of destroyed and remain in the children. If they are ever filtered back in, they are simply re-attached and do not have to be reconstructed or rendered.</p><h3>Consistent API</h3><p>As with any refactor it is important to take a step back and consider the issue as a whole. While iterating on new features on the CollectionView, APIs were added that made sense in context, but it is time to consider how the API could be made more consistent and intuitive. Ideally learning one feature leads to an early understanding of another such that one could assume the API of a different feature without needing to read documentation. The API was modified a little bit in various areas, but the most drastic modification was to sorting and filtering. The chart below compares both sorting and filtering for the next and current CollectionView.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fairtable.com%2Fembed%2FshrI6dNSjXv2jNlqj&amp;url=https%3A%2F%2Fairtable.com%2FshrI6dNSjXv2jNlqj&amp;image=https%3A%2F%2Fstatic.airtable.com%2Fimages%2Foembed%2Fairtable.png&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=airtable" width="800" height="533" frameborder="0" scrolling="no"><a href="https://medium.com/media/56e703a0c4ad0f7ff09087bafab93bc5/href">https://medium.com/media/56e703a0c4ad0f7ff09087bafab93bc5/href</a></iframe><p>First the actions to perform a sort or filter were aptly named sort and filter. While these methods may not makes sense to call directly often, the option is there for those use-cases. This meant that the current sort flag would need to be renamed, and it was given a name that matches more directly its underlying purpose sortWithCollection. Both sets of features now have getters, setters, and a remove method (which is sugar for set(null)). Additionally the view iterators were similarly named viewFilter and viewComparator and as previously mentioned they both iterate over views now instead of models.</p><p>An additional refinement to both iterators is that they can be defined as a string, indicating an attribute on the views model (returning an undefined if the view has no model). Additionally viewFilter can take a predicate object that would also attempt to match the value within the view’s model, ie: view.setFilter({ visible: true });</p><h4>Other notable breaking changes…</h4><p>Two other breaking changes worth mentioning regard how the NextCollectionView deals with an emptyView and how the developer can manipulate the children.</p><p>In the current CollectionView an emptyView is added like any other child affecting the children.length. Additionally the CollectionView triggers specific events unique to the empty view. In the NextCollectionView, a region is attached to the NextCollectionView’s el and the emptyView is shown in this region. The emptyRegion is made publicly accessible and can be used to understand when an emptyView is shown. Otherwise the emptyView is kept fairly separate from the NextCollectionView children. It is notable that an emptyView may be shown when there are no children <em>or </em>when there are children but they have all been filtered out. Thus it makes sense that the emptyView should not affect the view’s children.</p><p>Another significant change is the children can no longer be modified directly. You can still iterate over them or request specific view’s, but you can no longer add or remove children directly. This keeps the CollectionView from getting out of sync with the children container.</p><p>A detailed list of breaking changes are on the feature’s PR, <a href="https://github.com/marionettejs/backbone.marionette/pull/3244">https://github.com/marionettejs/backbone.marionette/pull/3244</a></p><h4>We need your help!</h4><p>The NextCollectionView cannot be successful without the involvement of the Marionette community. We need developers to try the new view in real world scenarios. We need help identifying and squashing bugs as well as understanding any performance regressions or new limitations we’ve overlooked. Please, if you can, try out the new view and let us know how it goes in <a href="https://gitter.im/marionettejs/backbone.marionette">Gitter</a>, or if you run into a problem, <a href="https://github.com/marionettejs/backbone.marionette/issues">open an issue on Github</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d335f5a9736a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blog-marionettejs/next-collection-view-d335f5a9736a">A New Refined CollectionView for Marionette.js</a> was originally published in <a href="https://medium.com/blog-marionettejs">Marionette.js blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cypress will change the way you develop]]></title>
            <link>https://medium.com/hackernoon/cypress-will-change-the-way-you-develop-47a194d2a33f?source=rss-62d971d6ce16------2</link>
            <guid isPermaLink="false">https://medium.com/p/47a194d2a33f</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[integration-testing]]></category>
            <dc:creator><![CDATA[Paul Falgout]]></dc:creator>
            <pubDate>Sun, 01 Jan 2017 15:06:08 GMT</pubDate>
            <atom:updated>2017-07-14T20:16:56.086Z</atom:updated>
            <content:encoded><![CDATA[<h4>Make TDD your front-end new year’s resolution with Cypress</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TUHYnkN1UJku2Db0aTLSwA.jpeg" /></figure><p>In November 2015 I saw Brian Mann give a presentation on <a href="https://cypress.io/">Cypress.io</a>. It immediately felt like the future.</p><p>At the time I had challenged myself and my coworkers to improve our testing. I was working on code coverage for <a href="http://marionettejs.com/">MarionetteJs</a>, and I took what I had learned there to the day job. Unit testing in Mocha was fine, and it worked great for Marionette, but it hardly covered the app we were developing. We had Selenium tests, but those were frequently flaky and done as an additional step after development. Attempts to integrate Selenium testing with our developer workflow failed. There was too much friction and everything felt kind of hacky.</p><blockquote>“The last tool that changed my workflow this dramatically for the better was git.”</blockquote><p>By May I had early access to the beta for Cypress and wrote my first test. It was clear that I did not know what I was doing. Cypress felt very familiar and it used Mocha and Chai for test writing, but knowing where to start for my mature application was daunting. My first error was to treat Cypress as a replacement for Selenium. While it can replace Selenium, I would highly recommend setting aside end-to-end tests for now and begin stubbing for integration tests.</p><p>After we began stubbing our server API we immediately saw workflow improvements. We weren’t even writing tests yet, but we were able to easily stub complicated data scenarios. We didn’t need to touch a database or setup a server. With some simple javascript we could setup every scenario we needed to cover to develop a new feature and then through cypress, interact with it, in our app, with excellent visibility into what was actually happening in the browser. Soon I stopped opening chrome to test my work and was exclusively using Cypress for development. The last tool that changed my workflow this dramatically for the better was git.</p><p>Let’s take a look at what this looks like in practice.</p><pre><strong>describe</strong>(&#39;User List&#39;, function() {<br>  <strong>describe</strong>(&#39;when there are users in selected group&#39;, function() {<br>    <strong>beforeEach</strong>(function() {<br>      cy.server()<br>        .route(&#39;/api/users?group_id=*&#39;, &#39;fixture:users&#39;)<br>        .visit(&#39;/users&#39;);<br>    });<br>    <br>    <strong>it</strong>(&#39;should load the list page&#39;, function() {});  <br>  });<br>  <br>  <strong>describe</strong>(&#39;when there are no users in group&#39;, function() {<br>    <strong>beforeEach</strong>(function() {<br>      cy.server()<br>        .route(&#39;/api/users?group_id=*&#39;, [])<br>        .visit(&#39;/users&#39;);<br>    });<br>    <br>    <strong>it</strong>(&#39;should load the empty page&#39;, function() {});<br>  });<br>});</pre><p>In this Cypress example, we have setup two data scenarios for different API results. In practice we might add describe.only to one of the scenarios so that we can develop in that environment. After running the “test” Cypress is a fully interactive Chrome instance complete with console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bj-tC-Tw603j5ZMT-GJMDw.png" /><figcaption>The code example in Cypress. The left side is the interactive test results.</figcaption></figure><p>While this doesn’t scratch the surface of the promise and potential of Cypress, if this was all it did, it would be enough. In the first week of January I’m pleased to say we’re launching our first major feature that includes Cypress testing for every aspect. Additionally I am working with the Marionette team on possibly testing Marionette with Cypress, and while it was not designed specifically to test a library, everything is looking very promising. I hope to share more about what I’ve learned along the way soon.</p><p>Cypress should be public in the near future and I believe we’ll soon be questioning how we functioned without it. Get in on it now, and make Cypress and TDD your new year’s resolution. Cypress has an active and growing community, and while you don’t need access to run cypress headlessly, access to the GUI is currently by invitation during the beta. However getting access is easy; just ask in their g<a href="https://gitter.im/cypress-io/cypress">itter room</a>.</p><h3>Sam Saccone on Twitter</h3><p>I am calling it now... https://t.co/7IfXnMhLbb will be the biggest game changer in UI testing since webdriver https://t.co/Z4P8wrVWwj</p><p><strong>Relevant Links:</strong></p><ul><li><a href="https://cypress.io/">https://cypress.io</a></li><li><a href="https://gitter.im/cypress-io/cypress">https://gitter.im/cypress-io/cypress</a></li><li><a href="https://www.youtube.com/watch?v=yq99BvSe1AQ">Nodevember 2015 Cypress Presentation</a></li></ul><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47a194d2a33f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/cypress-will-change-the-way-you-develop-47a194d2a33f">Cypress will change the way you develop</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>