gerrys0

The hardest is from 2 to 3. After 3, the acceleration goes down. It kind of goes like this (x-axis is # of kids):

  |
  |||
 ||||||

||||||||||

Agree. When we had one kid, I started a business. Looking back, it was totally doable. When we had two kids, I was a solo freelancer, worked a ton, and don't remember any issues. The third one, though, we called him The Crusher. Even though he was as easy as the first two, all three constantly demanded attention, and we were outnumbered. There was no "relaxing with the baby". As they got older, the sheer logistics with school and multiple activities got ridiculous (let's say 3 children x 1 activity each x 2 days/wk (1 practice + 1 game) = 6 afternoons/evenings gone). Expenses suddenly got out of hand (preschool++).

Of course, wife & I always wanted three. I was not going to not have three kids, just so I could spend more time coding. I would never tell anyone who has < 3 kids that they have it easy, but this was a very interesting sub-topic of the OP.

This explanation fits better: https://twitter.com/f_bernier/status/451448780999499777

Yeah, the current packaging system is more of a download installer and less of a dependency management system. That should get a lot better in 1.0. As for Jade, https://atmosphere.meteor.com/package/jade-handlebars is working towards this. It also appears that Meteor is (or was) thinking of integrating Jade support in Meteor directly: https://github.com/meteor/meteor/tree/jade

Our company has doubled down on Meteor. We start all greenfield apps in meteor now.

The biggest negative is simply the immaturity of the ecosystem. Everyone has different standards. There are no de facto standard packages (yet). Everything is changing rapidly. What worked well last week may not work well this week. The bleeding edge truly bleeds.

From a pure technology perspective, I'm excited about meteor because (to use a cliché) it shifts the paradigm. I wouldn't compare it to Rails/Ember/Backbone/etc because meteor is full-stack. There is no client/server. There's no ajax. Everything is one codebase. Even though it's built on top of node, it doesn't even feel like node because of the reasons above, and most of meteor is synchronous.

We wrote a couple blog posts about making the jump to meteor. I think the 1st one directly answers your question. The 2nd caused quite a stir here on HN.

http://differential.io/blog/the-current-challenges-of-buildi...

http://differential.io/blog/meteor-killin-rails