Ironing out bugs in Meteor


#1

Spinning off Next steps on Blaze and the view layer, where @gschmidt states

MDG is taking a look at the Meteor stack from top to bottom and thinking about what’s next.

I strongly suggest MDG commits more resources to squashing bugs - there currently 856(!) open issues on github.
And specifically it would be VERY nice if one of the first to address was build performance in 1.2 - which prevents me and many other devs from transitioning to 1.2.