Difference between MEAN.js and MEAN.io

Question

I wanted to use the MEAN JavaScript Stack, but I noticed that there are two different stacks with either their own website and installation methods: mean.js and mean.io. So I came up asking myself this question: "Which one do I use?".

So in order to answer this question I ask the community if you could explain what are the differences between these two? And if possible pros and cons? Because they look very similar to me.

Answer 1

Actually, both are the same both use swig for templating, both of them use karma and mocha for tests, passport integration, nodemon, etc.

Both were started by the same people where Mean.js is a fork of Mean.io. Mean.io is now under the umbrella of the company.

Let's see what are the main differences:-

SCAFFOLDING AND BOILERPLATE GENERATION

Mean.io uses a custom CLI  tool named 'mean' whereas Mean.js uses Yeoman Generators.

MODULARITY

Mean.js uses modules just in the front-end (for angular), and connects them with Express. Whereas Mean.io uses a more self-contained node packages modularity with client and server files inside the modules.

BUILD SYSTEM

Mean.io has recently moved to gulp but Mean.js uses grunt.