Seeking Community Input: Meteor.js Roadmap

[jam]

@trusktr

However, without this change, Meteor is going to be stuck in legacy.

This is an excellent point that I didn’t really appreciate until recently.

@storyteller

make a fork like this for Deno

I think Bun would also be an interesting experiment at some point.

What is the current state of Meteor?

I think the front-end clients should not be the focus on the core team. Probably just sdk + backend and hosting platform (galaxy) and third party integrations with different clients (vite, Cordova, electron, capacitors) could be maintained by the community. I personally decoupled backend from frontend, created a meteor client SDK and used it for backend/hosting. This is how Firebase, and Supabase works except that Meteor backend is more flexible.

A Meteor SDK is also intriguing. Then I suppose you could bring any framework - Astro, SvelteKit, etc. But I’m not sure if there would be a big tradeoff in “it just works so I can focus on business logic” which I think is one of Meteor’s best selling points.