4 ms·

Love to see Meteor still out there in the wild. We migrated about six years ago to Node/Express/Typescript/Postgres + React/Mobx and never looked back, but have

• 015a 4y ago
  Agreed; nothing in JS has hit the level of productivity I got with Meteor, and while its still going along, its pretty sad that it (or its ideas) didn't catch on.
  • sergiotapia 4y ago
    They mistakenly tried to support every frontend under the sun and not even bother shipping a router with their fullstack framework. Crazy in hindsight! If only they focus on React and included a default vetted router, Meteor would probably still be thriving today. Instead they tried to please everybody and ended up satisfying nobody. MDG ultimately pivoted to Apollo and _that_ stuck like glue everywhere, so I am happy they ultimately found success. I still miss Meteor though, it was so stupidly productive early on.
• eyelidlessness 4y ago
  > not so much of Mongo So, the Meteor magic was just not thinking about await?
  • dham 4y ago
    Meteor predates Promises and Async/Await. You have to remember at the time all you had was callbacks and async.js to manage them. There was Bluebird around 2014 but Meteor was even before that. Meteor uses node-fiber, I assume it still does, but it was very "non-standard" at the time and definitely now. You rarely saw it in any codebase.
    • eyelidlessness 4y ago
      I’m well aware of Fibers, and the big async API kerfuffle of 200*s! I was amused to see Q pop up unmentioned in git blames just today. I’d be curious if Fibers would find adoption if it were introduced today. I suspect yes, with much regret because knowing when functions suspend is not something people would give up knowing the implications.