Coming soon: Meteor 1.4

[Hongbo_Miao]

That will be amazing!! Finally Mongo 3.2 is coming out!

[mz103]

Woop woop! MDG keep rockin!

[awatson1978]

Looking forward to a solid maintenance release and the option of using Mongo’s data-at-rest encryption (requires enterprise license; but still). Looking forward to this!

[rlivingston]

Awesome! So what is “soon”?

I’m currently using the “wip-upgrade-to-node-4” branch to good effect but have changes planned for the moment MongoDB 3.2 hits!

[AndreasGalster]

I’m curious how new Node versions are going to reflect in performance? I’ve read that Node 6 has drastic speed improvements.

Also, really looking more forward to see an experimental Alpha build of Apollo to play with :D.

[bsprite]

This is the best news I’ve seen since 1.3.

The newer mongo and node versions have some major major performance increases. Node 6 is amazing so the sooner the better.

[vikr00001]

Fantastic! It will be great to have access to the Mongo 3.2 $lookup operator.

[sergiotapia]

Free performance and a nice Quality of Life update, sounds good to me.

I wonder how this will affect build/refresh times? I imagine it’s going to make things quicker?

[marklynch]

That’s great news. Any idea when can we expect to see the first Beta ?

[tanis]

To solve this problem for Node 4 and any future Node updates, we’re going to require Meteor users who rely on packages with binary dependencies to install a compiler toolchain on their development and build machines. We’ll make sure this is a straightforward and well documented process. In addition, we’ll ship Meteor’s core dependencies with pre-built binaries.

Can’t you also use the Atmosphere build server to automatically build binaries for versions of Node officially supported by Meteor? That would save time and sweat for those using packages depending on binaries.

[Siyfion]

That’s great news. Any idea when can we expect to see the first Beta ?

Agreed, any idea when we’re likely to have a usable, testable, version?

[rhywden]

@vikr00001

Fantastic! It will be great to have access to the Mongo 3.2 $lookup operator.

Question is: Will $lookup be reactive?

[robfallows]

@rhywden

Question is: Will $lookup be reactive?

Well, to reiterate a point I made elsewhere, $lookup is part of the aggregation pipeline and so not immediately reactive.

[deligence1]

That’s amazing news. Great work MDG!!!

[lai]

Is the DDP batching stuff going to be part of it too?

[robfallows]

Is the DDP batching stuff going to be part of it too?

Looking at the releases, that should be in 1.3.3

[rhywden]

@robfallows

@rhywden

Question is: Will $lookup be reactive?

Well, to reiterate a point I made elsewhere, $lookup is part of the aggregation pipeline and so not immediately reactive.

So, moderately useless, then. I’m liking Mongodb less and less. There’s a reason why you try to normalize stuff in a database - yes, I can denormalize the data and put it into every document it’s relevant to.

And then I update the data - and now I have to do multiple updates instead of just one (and god help me if I forget one). I’m really not seeing the usefulness of these kind of dbs unless you have a singular table with next to no external dependencies.

[Stan]

This is exactly why Apollo is a thing.

Woo on v1.4!

[jeffshaver]

why not just let us use whatever node version we want. why do we have to lock into v4.