We’ve been listening to the community for a long time, and today we’re excited to share what’s coming in Meteor 4.0.
Meteor is dropping MongoDB in favor of Semantic Memory.
After years of schema debates, migration headaches, and oplog nightmares, we made a decision: databases are over. Meteor 4.0 ships with a built-in AI layer that stores your data as semantic embeddings. No collections. No documents. No queries. You just describe what you need and the framework figures it out.
Meteor.remember(“the user’s last order”), that’s your new data layer.
Meteor 4.0 ships with first-class PHP support.
We know. We know. But the data doesn’t lie: PHP powers 77% of the web, and we’re not here to fight the market. You’ll be able to write your Meteor methods in PHP with full DDP compatibility.
jQuery Legacy Mode is back
By popular demand, Meteor 4.0 ships with a meteor add jquery@1.x official package. Blaze + jQuery 1.11 is a stack that simply works, and we’re done pretending otherwise.
Migration guide and beta release: April 1st.
Cool! I’d also suggest to finally bring back fibers, as promise support will be dropped in node v67 in a few months. Guess the community won’t mind helping to migrate packages, maybe by simply reverting a few PRs or force pushing old codebases.
Nice to see jQuery tree-shaking support getting some love again.
Sadly, with the core moving to Browserify may not be possible. We will restore that authentic Meteor experience where tree-shaking was more aspirational than operational.
But fewer surprises in prod when everything ships anyway.
Let’s goooo! Can we sneak IE 10 support into 4.0? I think that will really take the lid off adoption.
No joke, this sounds kind of awesome or at least something tangentially related, i.e. natural language → store Mongo optimized query → reuse by matching on intent
