<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Meteor on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/meteor/</link>
    <description>Recent content in Meteor on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 23 Oct 2022 21:54:54 -0400</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/meteor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Brief Comparison of FlowRouter and Iron:Router for Meteor.js</title>
      <link>https://www.bradcypert.com/a-brief-comparison-of-flowrouter-and-iron-router-for-meteor-js/</link>
      <pubDate>Fri, 11 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/a-brief-comparison-of-flowrouter-and-iron-router-for-meteor-js/</guid>
      <description>&lt;p&gt;Recently, I was updating an open source package that I maintain – &lt;a href=&#34;http://www.github.com/bradcypert/ignite&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;a project structure scaffolding tool&lt;/a&gt;&#xA;. While updating the template I use for my Meteor apps, I realized my tool was still catering towards Iron:Router. For those unaware, Iron:Router has a history of being &lt;strong&gt;the&lt;/strong&gt; Router for Meteor apps. When I first used it, however, it felt like it was lacking in some ways. After using it on about several Meteor apps now, I’ve adjusted my design to conform to Iron:Router and it works extremely well, but recently &lt;a href=&#34;http://www.kadira.io&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;KadiraHQ&lt;/a&gt;&#xA; created their own Router – FlowRouter – and oh, is it nice.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
