[angersock]

We've been doing doubletime to migrate off of an old Meteor app, due to its bundling of old versions of node and really questionable use of Mongo.

I think that, in the right hands, Meteor is a great prototyping tool--putting into production and scaling it though is a fool's errand.

[aogaili]

What older version of node? it support Node 8, please get your facts straight https://blog.meteor.com/announcing-meteor-1-6-abf30f29e2c6

[hexsprite]

Meteor 1.6 supports Node 8.9.x. What's questionable about Meteor's use of Mongo? Reading the oplog? You don't need to use the reactivity if you don't want it. There is a simple API to either use polling or turn off reactivity altogether if you don't care about it.

[angersock]

Legacy. Meteor. App.

Doesn't matter what new versions support if we can't update things.

The reactivity choice was made for us (poorly).

[roro5678]

We are in the same situation too, I am curious, you are migrating towards what and how ?

[angersock]

Phoenix and Postgres.

And while the Phoenix part has all kinds of issues--especially when you make it work with Mongo instead of Postgres and Ecto--it's waaaay better than the Meteor bilge we inherited.

EDIT: And honestly, at this point we all think that Rails or Node or anything else would've been a better move than Phoenix, but hey hindsight is 20/20 and we inherited the legacy Phoenix app.

Bet folks don't even know that those exist. :(

[networked]

Could you describe the issues you've had with Phoenix and why you would have preferred something else? I am about to commit to Elixir and Phoenix for a project, perhaps a long-term one, and I would love to hear stories about how it doesn't work out.

[angersock]

So, I think that Elixir/Phoenix for a new project, if you're careful, is totally great.

Make sure you do happy-path integration tests first before screwing around with unit tests. Don't use Mongo, use Postgres + Ecto. Don't put changesets/business logic into controllers, call out to a dedicated business app. Don't use Mongo. Switch away from Brunch to Webpack early. Don't use Mongo. Don't do everything in maps, only use that at the edges of the web logic until you parse things into normal business objects. Don't use Mongo. Use a linter like Credo, customize the settings for your project early on. Don't use Mongo. Think about the "community standards" and make sure they actually apply to your problem.

Don't use Mongo.