<?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 Meteor Toys on Medium]]></title>
        <description><![CDATA[Stories by Meteor Toys on Medium]]></description>
        <link>https://medium.com/@MeteorToys?source=rss-d32e3aa6cf60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*-kjiyMTd21H2vjVS.png</url>
            <title>Stories by Meteor Toys on Medium</title>
            <link>https://medium.com/@MeteorToys?source=rss-d32e3aa6cf60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:26:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@MeteorToys/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[The State of Meteor Toys]]></title>
            <link>https://medium.com/@MeteorToys/the-state-of-meteor-toys-6f53b3c07b01?source=rss-d32e3aa6cf60------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f53b3c07b01</guid>
            <category><![CDATA[meteorjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[meteor]]></category>
            <dc:creator><![CDATA[Meteor Toys]]></dc:creator>
            <pubDate>Tue, 22 Mar 2016 14:06:14 GMT</pubDate>
            <atom:updated>2016-03-23T11:47:39.876Z</atom:updated>
            <content:encoded><![CDATA[<h4>In Brief: Meteor is changing; Meteor Toys 3 are coming to improve current tools; free upgrade for all customers; aside from fixes, future developments halted until Meteor re-solidifies; price dropped to $49 at least until 3.0 launches; new technologies coming to Meteor may call for new strategy.</h4><p>Back when Meteor Toys were created, Meteor was a very simple framework which focused on aligning the community and practices around a common way of doing things.</p><p>In recent months, we’ve seen people develop unique preferences for their tools, and with it, Meteor Development Group has been changing their approach.</p><p>If there was a way to explain what’s happening, it’s that everything is changing, but nothing is changing.</p><p>Meteor is becoming more modular, and you will have the choice of using the set of core packages, or to swap them out for others. Additionally, there will be new core packages, which I believe will serve as more advanced alternatives to older ones.</p><p>With the changes in motion, and the numerous “state of” posts that came with it, comes the time to clarify what’s happening with Meteor Toys.</p><h3>First, What’s Next for Meteor?</h3><p>So, if we look at the facts and hints that have been dropped, we know NPM integration is here, a new data layer is coming, a new accounts package is coming, there may be React Native and Webpack integration, and MDG really likes React.</p><p>My hunch is that if/when all those pieces come together, React will become the “standard” view layer for Meteor, and Meteor will look a lot different, but also very similar, to what what it was. We might as well call it “Meteor 2.0.&quot;</p><p>Meteor itself will take on the form of a build tool, and from there, you would be able to swap in whatever you seem fit. If you want the Tracker/Mongo stack, okay, easy, and if you want to get fancy with the React/Apollo stack, okay, just as easy.</p><p>MDG plans to export the current core packages as seperate NPM modules and repositories, which would pave the way for the community to leave their mark on them.</p><p>Once that and the new build tool happens, I think we’d run the classic Meteor stack, or a modified stack, through that and NPM, and that would start the end of Atmosphere.</p><p>I’m also thinking that:</p><ul><li>it wouldn’t be a matter of which is better, but which fits your needs</li><li>it’ll could be at least a year (or longer) until these new tools are designed, built, documented, and stabilized for production</li><li>people will likely be able to replace and rebuild their apps part by part based on what they see fit</li></ul><p>There’s also a lot of innovation happening in the JavaScript world, so its likely that even if viable Meteor alternatives appear, we would still be able use the parts of Meteor with-in them. (if that helps you keep your bet…)</p><h3>Evolving with Meteor</h3><p>With support for NPM in v1.3, Meteor will have a lot more options for everything. However, MDG plans to go a step ahead by having vendor supported packages. We can see this with their core packages, Angular and React support, the impending support for MySQL &amp; LiveQuery, and whatever else they have cooking.</p><p>Meteor Toys goal has always been to provide tools around the officially supported packages, and that will continue to be the plan. When it comes to things that are designed outside of MDG, ToyKit will be available to build additional toys.</p><h3>The Front-End Situation</h3><p>Currently, the Meteor Toys UI is built in Blaze, which most of the Meteor community is using.</p><p>For all the hype of React, I think Blaze is actually very underrated. Aside from the fact that it was React before React came out, it also serves as its polar opposite with designer-friendly templating and amazing flexibility. I think it could have had the traction React received, and Vue is recieving, and maybe it’s not too late.</p><p>However, Meteor is growing to be a truely front-end agnostic solution, and not everyone wants Blaze.</p><p>Currently, for non-Blaze Meteor apps, the plan is to load in Blaze as a dependency during development mode, and then yank it out when you build for production. This seems to already work, but I have yet to. thoroughly inspect it. If/when Blaze becomes dethroned, or as I suspect, React becomes primary, I’ll look into what the next best step to take is.</p><h3>The Business Model, and a New Price</h3><p>Since what I call “The Great Fatigue” began, we saw a number of posts from projects like CollectionFS and Telescope suggesting that they are basically no longer supported, at least in their current form. Even Blaze had a similar dialogue around it, where it was accepted that there is no financial incentive for MDG to carry on with it.</p><p>First, I think they all did huge, great, work, and it’s amazing how much value they provided to the community, from sharing what they’ve learned to the making the code open source.</p><p>However, as we see, the motivation to support a free package tends to fizzle quickly, and outside code contributions are not encouraging. On the other side of it, paying a developer for something increases their commitment to the project.</p><p>That’s why I encourage people to continue to open up to the idea of paid packages, because while money does not grow on trees, it can make trees and other things grow. The return on them is always great, and having a supported solution is priceless.</p><p>And of course, I don’t know if the approach being taken with Meteor Toys is the “correct one,” though I am happy with the results it’s producing. I’ve decided to take the next test, by dropping the price to $49 per license at least until Meteor Toys 3 are released.</p><p>I’ve tested a lower prices before on the assumption that it would lead to higher volume, but it did not do much for the conversion. However, I suspect that many people spend time considering the purchase before jumping on it, so maybe the short term tests may have done more harm than good.</p><h3>The Next Step</h3><p>Given my very unfortunate lack of ability to predict the future, I have to move on the assumption that “everything is changing, but nothing is changing” and re-evaluate the Meteor Toys strategy when the dust settles.</p><p>Meteor Toys 3 is underway, which will come with improved tools, a surprise or two, and leapfrog a few of the bugs that remain in Meteor Toys 2. Their development actually started a few months ago, but an injury, the Great Fatigue, and a new project put them on hold.</p><p>Once they are ready, I’ll pause new developments, aside from bug fixing, with the emphasis that Meteor Toys are only able to support the Meteor that we currently know. Only once we have a clearer vision of where Meteor and the JavaScript world is going can I focus on the right strategy for moving forward.</p><p>What do you guys think? Let me know over on <a href="https://crater.io/posts/sQZBHe9HKc9AHowRc">Crater</a>.</p><p>See you folks soon! ☺️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f53b3c07b01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[J2MT3: The Toys Never Forget]]></title>
            <link>https://medium.com/the-journey-to-meteor-toys-3/j2mt3-the-toys-never-forget-61dbf4bbcaec?source=rss-d32e3aa6cf60------2</link>
            <guid isPermaLink="false">https://medium.com/p/61dbf4bbcaec</guid>
            <category><![CDATA[meteorjs]]></category>
            <category><![CDATA[meteor]]></category>
            <dc:creator><![CDATA[Meteor Toys]]></dc:creator>
            <pubDate>Sat, 28 Nov 2015 12:34:20 GMT</pubDate>
            <atom:updated>2015-11-28T12:43:36.716Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey folks, thanks for tuning into the <a href="https://medium.com/the-journey-to-meteor-toys-3/latest">Journey to Meteor Toys 3</a>. As you’ve probably seen, last week was pretty crazy, with lots to think about, so my apologies for the delayed update. Good news is, this week I’ll be updating <em>two</em> toys: Method and Pub.</p><p>The Method and Pub toy display your Methods and Publications, and when you click on them, you can see their parameters, input them, and run the function. It’s a day and night difference compared to typing out the code yourself and then going back to your source code to make sure the parameters match up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kEMVA4H3sFjSp7jexgDYxA.gif" /><figcaption>Original Method toy, re-used for demonstration of its purpose</figcaption></figure><p>However, I found it gets annoying when you have to re-enter the parameters. Maybe I’m getting spoiled — but that shouldn’t stop progress! So, the updated Method and Pub toys will remember the parameters you enter into them, so you can quickly tweak them and then run again.</p><p>One of the other benefits of these two toys I noticed is when you jump into a new project, it’s really nice to see all the methods and publication from a high level — and its getting easier now that they will be sorted alphabetically. Its really nice if you name our Methods like “Email/action1”, “Email/bction2”, etc.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FuFUOmZQDHp4%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DuFUOmZQDHp4%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FuFUOmZQDHp4%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/45f8e66fb0b2a2ea10b40b1c0998e4dc/href">https://medium.com/media/45f8e66fb0b2a2ea10b40b1c0998e4dc/href</a></iframe><p>Check out the video for a demo. And to update, just remove your Meteor Toys and add them again with `meteor add meteortoys:allthings`.</p><h3>Cyber Monday</h3><p>If this has persuaded you to begin your Meteor Toys addiction and completely relapse into childhood, then I have some good news! Up until Cyber Monday ends (NY time), Meteor Toys will be half price off with coupon code `asl`.</p><p>Thanks for tuning in! More updates on the way :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61dbf4bbcaec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-journey-to-meteor-toys-3/j2mt3-the-toys-never-forget-61dbf4bbcaec">J2MT3: The Toys Never Forget</a> was originally published in <a href="https://medium.com/the-journey-to-meteor-toys-3">The Journey to Meteor Toys 3</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Journey to Meteor Toys 3]]></title>
            <link>https://medium.com/the-journey-to-meteor-toys-3/the-journey-to-meteor-toys-3-509e0a398e31?source=rss-d32e3aa6cf60------2</link>
            <guid isPermaLink="false">https://medium.com/p/509e0a398e31</guid>
            <category><![CDATA[meteor-framework]]></category>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[meteorjs]]></category>
            <dc:creator><![CDATA[Meteor Toys]]></dc:creator>
            <pubDate>Mon, 09 Nov 2015 19:49:47 GMT</pubDate>
            <atom:updated>2015-11-10T16:55:38.620Z</atom:updated>
            <content:encoded><![CDATA[<p>Meteor Toys is one of the funnest projects I’ve ever worked on. For me, it’s a completely new concept, and targets a different market than I am used to — developers. The challenge to overcome new territory has been very stimulating, and it has been driving a big part of the enthusiasm to create the best development tools for Meteor developers!</p><p>The first release was testing the grounds and providing what I thought were essential tools for Meteor developers, while the 2.0 release distinguished itself with a platform play through the possibility to <a href="http://github.com/MeteorToys/ToyKit">extend Meteor Toys with the ToyKit SDK</a>. This came to life after I had built enough toys by hand. Seeing the the repetitive steps helped me understand what needed to be tucked away.</p><p>Now that the grounds have been covered, and the SDK is complete, I’ll be focusing on rebuilding the toys with the SDK and making them better. However, rather than do an all-at-once release, we’ll go through the updates step-by-step through this blog series. The plan, roughly, will be to improve one toy or feature each week for the next 12 weeks. And of course, that doesn’t mean there won’t be a few surprises. :)</p><p>Many people are wondering how the project is working out, so I thought I’d first take a step back to see how it got here. Up until June, I was thinking (or heavily pressured to think) about taking a job a stable company. Around that time, I sold the start-up I co-founded called Flutter to SumAll, and was left burned out and back on the market.</p><p>I’ve interviewed everywhere from established and unestablished start-ups, to the $100b+ guys, but virtually every place I’ve been to wasn’t inspiring (to say the least). As with freelance work, I knew that I wouldn’t be able to execute in my style, so I realized there is no future for me there. Many people told me that’s how life is, but I wasn’t having that.</p><p>Much to my surprise, Meteor Toys rescued me from the situation. Initially, it was an recreational project I worked on for fun and to get my head away from the madness. However, once I saw the response, and that it could become bigger, I decided to take a bet on it. And I’m glad I did, because it let me continue on my entrepreneurial path.</p><h3>Embracing Life Abroad</h3><p>New York was trying to kill me, so I reluctantly went for the emergency exit. I jumped on a plane to visit my Swedish people, and we took a trip down to a music festival called <a href="https://www.youtube.com/watch?v=HuAxVfZasUk">Tomorrowland</a> for “rehab from real life.”</p><p>After the “dream” was over, I extended my stay abroad, at first for a week, then a month, and then I figured at least a year 😋. With my clean break, I decided to tour Europe, which gave me the pleasure of taking a break from the start-up matrix, meeting new people, and visiting Serbia, my home country, nearly 20 years after my departure.</p><p>Once my visa expired, I flew in to Thailand, where I’ve been residing the past two weeks. I’ve picked out a place for the long term, <a href="https://twitter.com/msavin/status/659830140550037505">shaved my head</a> for curiosity’s sake, and look forward to cooling off for the Winter in this warm weather!</p><p>As a developer, I can do my work from anywhere. As developers, we’re very lucky to have that kind of opportunity. If you’re into traveling, you may like to try it as a lifestyle. Its becoming a movement by people who call themselves “digital nomads,” and it’s growing.</p><p>If you’re from a place like SF or NY, you’ll find its actually cheaper to travel than pay the insanely expensive rent! With big cities, I think unless you are leveraging the cities infrastructure, there may not be many good reasons to live there. <a href="http://www.theonion.com/article/84-million-new-yorkers-suddenly-realize-new-york-c-18003">The Onion</a> summed up my feelings toward it quite well. 😛</p><p>Anyways, Meteor Toys have been a big part of this journey, as they freed me up from freelancing and made the experience of work as enjoyable as the play. For the next three months, my plan is to relax, focus on getting into my best shape, and focus on getting the Toys into their best state. 😁</p><h3>The New Thing This Week</h3><p>As part of the Euro-Trip, I got over to Madrid for the Meteor hackathon, and the Toys stirred a couple of discussions. One of them has centered around open source versus closed source. Since Meteor Toys is a product — I figure closed source is normal, but not everyone agreed.</p><p>We realized that what people really want is for them to be <em>hackable</em>. That means they can remove toys, add their own stuff, and customize them. On the first level of that, there’s the <a href="https://github.com/MeteorToys/ToyKit">ToyKit SDK</a>, which lets you build stuff for yourself and then even publish it for others.</p><p>On the second level of that, I’m happy to introduce <a href="https://github.com/MeteorToys/ThemeKit">ThemeKit</a>, which lets you theme your Meteor Toys the way you’d like. There are currently <a href="https://atmospherejs.com/meteortoysthemes">eight themes available</a>, and if they don’t suit your needs, you can make and publish your own 👍🏻</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TIV7IMDmawZWjmFsEUTVXQ.gif" /></figure><p><em>(Note: if you were wondering what the “other thing like an SDK” was from the </em><a href="http://blog.modulus.io/meteor-toys"><em>Meteor Toys 2 announcement,</em></a><em> this is it 😎. It took a little longer to deliver because of the Meteor Toys 2.2 update, which brings in bug fixes, UI improvements and a few needed updates. To update, remove your Meteor Toys package then add them again 😊)</em></p><h3>We’re Just Starting!</h3><p>This update is a little bigger than what I expect to be usual, but each week I’ll pop in with a new feature to make your development life easier. 😋</p><p>So- am I the only one getting tired of the start-up hype? And what do you think of Meteor Toys, and where would you like to see it go? Let me know over on <a href="https://crater.io/posts/z2vMrCs4Du34hvpqb/the-journey-to-meteor-toys-3">Crater</a>! 😊</p><p><em>Thanks Sam (miningsam) for providing a second pair of eyes on this article!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=509e0a398e31" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-journey-to-meteor-toys-3/the-journey-to-meteor-toys-3-509e0a398e31">The Journey to Meteor Toys 3</a> was originally published in <a href="https://medium.com/the-journey-to-meteor-toys-3">The Journey to Meteor Toys 3</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Meteor Clone in Meteor]]></title>
            <link>https://medium.com/@MeteorToys/building-a-meteor-clone-in-meteor-58412f876aa7?source=rss-d32e3aa6cf60------2</link>
            <guid isPermaLink="false">https://medium.com/p/58412f876aa7</guid>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[meteorjs]]></category>
            <dc:creator><![CDATA[Meteor Toys]]></dc:creator>
            <pubDate>Mon, 02 Nov 2015 01:50:15 GMT</pubDate>
            <atom:updated>2015-11-02T03:52:32.683Z</atom:updated>
            <content:encoded><![CDATA[<p>With so many tutorials on How to Clone App X, I figured I’d just go for the meta-clone and clone Meteor in Meteor.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>How do you do this?</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>Keep scrolling… (the suspense makes it better)</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><h4>CrackRock = Meteor;</h4><p><em>Boom. </em>I think CrackRock is a more descriptive name for Meteor than Meteor anyways. Then, you can run all your favorite commands..</p><p>CrackRock.subscribe(…);<br>CrackRock.call(…)<br>CrackRock.etc…</p><p>.</p><p>.</p><p>.</p><p>.</p><p>Do you think the name “MongoDB” is kinda weird? I do too.<br>That’s why:</p><h4>CrackDB = MongoDB;</h4><p>.</p><p>.</p><p>.</p><p>.</p><p>If anyone needs branding advice, you can find my email address on the Internet. I’ll try to respond if I’m not too busy.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>I have nothing else for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58412f876aa7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Clue to Building a Blaze.rerender() function]]></title>
            <link>https://medium.com/@MeteorToys/a-clue-to-building-a-blaze-rerender-function-65ef0b132236?source=rss-d32e3aa6cf60------2</link>
            <guid isPermaLink="false">https://medium.com/p/65ef0b132236</guid>
            <dc:creator><![CDATA[Meteor Toys]]></dc:creator>
            <pubDate>Sat, 31 Oct 2015 09:54:55 GMT</pubDate>
            <atom:updated>2015-10-31T10:10:32.860Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot of people have been searching for re-render functionality, and we have a first clue to achieving it:</p><p>CleanCode = Blaze.toHTMLWithData(Template.Mongol, data)<br>CleanCode = Blaze.toHTML(Template.StaticTemplate)<br>$(“#Mongol”).html(CleanCode)</p><p>This lets you generate the HTML as a string, and then we can inject into wherever it needs to be. Blaze shouldn’t notice, and it’ll continue to update reactively.</p><p>This is a needed function because sometimes an element needs to be reset after being modified with contenteditable, updates via jQuery, animation, etc.</p><p>Props if you can make a package that works without requiring a parent element to be named :) In the meanwhile, I’ll get back to working on Mongol 2.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65ef0b132236" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blaze 2.0 Speculation]]></title>
            <link>https://medium.com/@MeteorToys/blaze-2-0-speculation-ab49db3441af?source=rss-d32e3aa6cf60------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab49db3441af</guid>
            <category><![CDATA[meteorjs]]></category>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Meteor Toys]]></dc:creator>
            <pubDate>Mon, 12 Oct 2015 19:29:38 GMT</pubDate>
            <atom:updated>2015-10-12T19:40:10.225Z</atom:updated>
            <content:encoded><![CDATA[<p>This week, there was an AMA on Crater by the Meteor Development Group (MDG), where one of the big questions was what will happen to Blaze?</p><p>Many people got the impression that the Blaze days are coming to an end, and some of us were sad, but that may not be the case.</p><p>During a brief conversation with Sashko from MDG a couple of months ago, he mentioned his idea of using React as a rendering engine for Blaze. I saw a hint of that in his <a href="https://gist.github.com/stubailo/9296dbd39fad0d6bbf58">Gist</a> on the subject, and emailed him to clarify.</p><p>There’s now a new edit to it that is very re-assuring:</p><blockquote><em>I think the best thing to do is probably build Blaze 2.0 on top of the React rendering system to get a nice developer experience while taking advantage of new tech like React Native and the React component ecosystem.</em></blockquote><p>I thought it’s worth paying this possibility because a lot of people, including myself, are very happy with the approach that Blaze takes and hope to see it evolve.</p><p>Much like Meteor gave us a great experience for writing on top of Node, perhaps it can do the same for React. And it would continue to reap the benefits of all the developments built on top of them.</p><p>What do you guys think of the approach? Let’s talk about it on <a href="https://crater.io/posts/xgxdmceFfGfBhoNN8/blaze-2-0-speculation">Crater</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab49db3441af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>