Meteor 0.9.3: Packaging updates and improvements • Hacker News Board

Re: Meteor 0.9.3: Packaging updates and improvements

#11

Post by Igglyboo » Fri, Sep 26, 2014, 1:22 PM UTC

davedx wrote: post #2

I used Meteor intensely for two projects up to where they introduced the new templating system (blaze), which broke both of my projects extensively including some third party Meteorite packages that I couldn't fix myself (believe me I tried) and seemed to be abandoned by their authors. I also gave up trying to get my projects to be SEOable because the package that supposedly lets you do this (spiderable) was very har…

Meteor isn't even version 1.0 yet, I would hope they would do breaking changes and standardize their api before their first major release.

Re: Meteor 0.9.3: Packaging updates and improvements

#12

Post by russtrotter » Fri, Sep 26, 2014, 2:33 PM UTC

Igglyboo wrote: post #11

davedx wrote: post #2

I used Meteor intensely for two projects up to where they introduced the new templating system (blaze), which broke both of my projects extensively including some third party Meteorite packages that I couldn't fix myself (believe me I tried) and seemed to be abandoned by their authors. I also gave up trying to get my projects to be SEOable because the package that supposedly lets you do this (spiderable) was very har…

Meteor isn't even version 1.0 yet, I would hope they would do breaking changes and standardize their api before their first major release.

Hmm... just how much stuff in the JS universe is actually not 0.x.y?

Re: Meteor 0.9.3: Packaging updates and improvements

#13

Post by maxharris » Fri, Sep 26, 2014, 3:59 PM UTC

sgarrity wrote: post #10

maxharris wrote: post #5

Meteor has gotten a hell of a lot better since I started using it (back in the 0.6.5 days about a year ago, in the fall of 2013). Performance and stability have improved dramatically, both on the client and server. I've been working on several large projects, and the new things that Blaze has added (mutable, per-template data instances) have made my life a lot easier. The transition between each release has been very…

Can you elaborate on this statement? "Now that it's possible to write sensible UI components" I'm curious what improvements you are referring to.

http://docs.meteor.com/#template_instance http://docs.meteor.com/#tracker_autorun

Suppose you want to make a widget, such as a drop-down menu that lets you edit the currently selected item. To do that, you need a place to store the currently selected item id. Storing this in a collection is not desirable either. If you rely on session variables, you can't have more than a single instance of your widget running at a time because session variables are globally scoped.

Now with template instances, there's finally a way to store and retrieve that selected item id (or anything else, for that matter) in a way that's conveniently accessible within template helpers and event handlers on a per-template basis.