Meteor 0.6.5: namespacing, modularity, new build system, source maps

This is a bit irrational, but it nags me every time the occasional Meteor post shows up here - it seems to always get a lot of upvotes and very few comments:<p>The Meteor blog goes back (under a different name) almost two years, that huge announcement thread is from 490 days ago, and they got VC funding over a year ago.<p>I remember being pretty excited at the time but somehow this long wait for a 1.0 has taken the wind out of my sails. I don&#x27;t mean to diminish all their hard work, and to be fair, there are frequent signs of life, but somehow it no longer captures the imagination. Am I the only one?

I feel that Meteor is awesome and has quite a bit of potential, but why stray from npm, which is one of those things that is actually awesome about node? I really wish Meteor would use npm. Is there some technical reason they don&#x27;t?

I&#x27;ve been a little more impressed with Derby (<a href="http://derbyjs.com/" rel="nofollow">http:&#x2F;&#x2F;derbyjs.com&#x2F;</a>) than Meteor, as it&#x27;s based on similar concepts, but plays well with the rest of the Node&#x2F;JS ecosystem (for example, it uses npm), has server-side rendering of page content, and can scale to multiple servers.<p>I have to admit my only hands-on experience so far has been a little tinkering, though. Who&#x27;s actually written stuff with Meteor, Derby and&#x2F;or similar frameworks, and what were your thoughts?

probably wrong to post this here, but did anyone actually chose slipstream over meteor (or meteor over another framework)? can you let us know why?

Awesome! I&#x27;m looking forward to using source maps.