Neat, I've been following Tiny and Meteor for years and I didn't see this coming at all. My first (and one of very few) blog post was about Meteor [1]. It got a

Neat, I've been following Tiny and Meteor for years and I didn't see this coming at all. My first (and one of very few) blog post was about Meteor [1]. It got a stunning number of visits (by my standards) and at the time I thought Meteor was going to have major traction if I was seeing so much traffic. In retrospect it was probably more so that I was one of few people who wrote about customizing authentication at the time, and it was something I had to do on most projects I built in Meteor. I'm guessing others did too. I very quickly lost interest in Meteor because it seemed so efficient for very basic applications, but ridiculously inefficient for heavily custom logical and ux flows. That's usually what I needed to build. I've come to dislike intimately learning my frameworks' guts - it suggests to me they could be too complex, and there's too much potential for technical debt from working around things. I think it's important to know how your framework works, but... There are limitations to how deeply I want to know these things. I'm curious to see where this goes, anyway. I feel like I should give Meteor another chance soon. 1. http://steve-adams.me/practical-examples-of-authentication-in-meteor-1-0/ http://steve-adams.me/practical-examples-of-authentication-i...