Forking Mean.io

Why MEAN.IO will fail in the long run?

If any of you have try to setup your own Angular, Mongo, Express, Node programming stack you know the pains of setting up everything correctly to find out that it’s not the “right” way to do things. If you have not used MEAN.IO go and check them out before continuing reading. After playing around with the master branch of MEAN.IO, I decided that this tool is great but it’s trying to do about a million things all at the same time. Don’t get me wrong their is plenty of good things and just enough bad things to get me motivated to write my own tool to fix the problem.

What MEAN.IO did right?

Some of my favorite parts of MEAN.IO, that I just simply enjoy using are the following.

• MEAN MVC design pattern
• MEAN packages
• MEAN CLI tool
• Folder scaffolding
• Grunt preconfigured

What MEAN.IO did WRONG

But with all great things there is a down side to them, the main vision behind the MEAN project is to create this larger eco system where packages can be created and exchange back and forward with anyone that uses that stack. What are you talking about that sounds like a great idea! To some point it does sound like a solid idea but in implementation it’s a whole other thing. If you go and take a look at some of there packages they are relative good implementations of actual useful code, but at this point we get into the war of packages. Don’t know what I am talking about? go and look at drupal and each of there competitive CMS for example WordPress, packages can not be exchanged even though both of them are written in PHP.

A better idea would be to implement exchangeable packages, take for example a package developed by MEAN.IO can be easily reused in a IONIC application, but of course this requires us to build code that has low coupling and use best practices to actually develop SOLID code.

PS: Book + Videos + Code Download