<table border="1" cellpadding="10"><tbody><tr><td valign="top" width="33%"><br><br><h1>MeanJS.org. provides these benefits that MEAN.io. doesn't</h1><br><br><b>Help</b>:<br> * Dedicated/searchable user group for questions, using github issues<br> * There's a book about it<br><b>File Organization</b>:<br> * Basic sourcecode organization, module(->submodule)->side<br> * Module directories hold directives<br><b>Code Modularization</b>:<br> * Approach to AngularJS modules, Only one module definition per file<br> * Approach to AngularJS modules, Don’t alter a module other than where it is defined<br><b>Model</b>:<br> * Object-relational mapping<br> * Server-side validation, server-side example<br> * Client side validation, using Angular 1.3<br><b>View</b>:<br> * Approach to AngularJS views, Directives start with "data-"<br> * Approach to data readiness, Use ng-init<br><b>Control</b>:<br> * Approach to frontend routing or state changing, URLs start with '#!'<br> * Approach to frontend routing or state changing, Use query parameters to store route state<br><b>Support for things</b>:<br> * Languages, LESS<br> * Languages, SASS<br><b>Syntax, language and coding</b>:<br> * JavaScript 5 best practices, Don't use "new"<br><b>Testing</b>:<br> * Testing, using Mocha<br> * End-to-end tests<br> * End-to-end tests, using Protractor<br> * Continuous integration (CI), using Travis<br><b>Development and debugging</b>:<br> * Command line interface (CLI), using Yeoman<br><b>Build</b>:<br> * Build configurations file(s)<br> * Deployment automation, using Azure<br> * Deployment automation, using Digital Ocean, screencast of it<br> * Deployment automation, using Heroku, screencast of it<br><b>Code Generation</b>:<br> * Input application profile<br> * Quick install?<br> * Options for making subcomponents<br> * config generator<br> * controller (client side) generator<br> * directive generator<br> * filter generator<br> * route (client side) generator<br> * service (client side) generator<br> * test - client side<br> * view or view partial generator<br> * controller (server side) generator<br> * model (server side) generator<br> * route (server side) generator<br> * test (server side) generator<br><b>Implemented Functionality</b>:<br> * Account Management, Forgotten Password with Resetting<br> * Chat<br> * CSV processing<br> * E-mail sending system<br> * E-mail sending system, using Nodemailer<br> * E-mail sending system, using its own e-mail implementation<br> * Menus system, state-based<br> * Paypal integration<br> * Responsive design<br> * Social connections management page<br><b>Performance</b>:<br> * Creates a favicon<br><b>Security</b>:<br> * Safe from IP Spoofing<br> * Authorization, Access Contol List (ACL)<br> * Authentication, Cookie<br> * Websocket and RESTful http share security policies<br><br><br></td><td valign="top" width="33%"><br><br><h1>MEAN.io. provides these benefits that MeanJS.org. doesn't</h1><br><br><b>Quality</b>:<br> * Sponsoring company<br><b>Help</b>:<br> * Docs with flatdoc<br><b>Code Modularization</b>:<br> * Share code between projects<br> * Module manager<br><b>View</b>:<br> * Approach to data readiness, Use state.resolve()<br><b>Control</b>:<br> * Approach to frontend code loading, Use AMD with Require.js<br> * Approach to frontend code loading, using wiredep<br> * Approach to error handling, Server-side logging<br><b>Client/Server Communication</b>:<br> * Centralized event handling<br> * Approach to XHR calls, using $http and $q<br><b>Syntax, language and coding</b>:<br> * JavaScript 5 best practices, Wrap code in an IIFE (SEAF, SIAF)<br><b>Development and debugging</b>:<br> * API introspection report and testing interface, using Swagger<br> * Command line interface (CLI), using Independent command line interface<br><b>Build</b>:<br> * Development build, add IIFEs (SEAF, SIAF) to executable copies of code<br> * Deployment automation<br> * Deployment automation, using Heroku<br><b>Code Generation</b>:<br> * Scaffolding undo (mean package -d <name>)<br> * FEATURE (a.k.a. module, entity) generator, Menu items added for new features<br><b>Implemented Functionality</b>:<br> * Admin page for users and roles<br> * Content Management System (Use special data-bound directives in your templates.<br>Switch to edit mode and you can edit the values right where you see them)<br> * File Upload<br> * i18n, localization<br> * Menus system, submenus<br> * Search<br> * Search, actually works with backend API<br> * Search, using Elastic Search<br> * Styles, using Bootstrap, using UI Bootstrap AngularJS directives<br> * Text (WYSIWYG) Editor<br> * Text (WYSIWYG) Editor, using medium-editor<br><b>Performance</b>:<br> * Instrumentation, server-side<br><b>Security</b>:<br> * Serverside authenticated route restriction<br> * Authentication, using Oauth, Link multiple Oauth strategies to one account<br> * Authentication, JSON Web Token (JWT)<br><br><br></td><td valign="top" width="33%"><br><br><h1>MEAN.io. and MeanJS.org. both provide these benefits</h1><br><br><b>Quality</b>:<br> * Version Control, using git<br><b>Platforms</b>:<br> * Client-side JS Framework, using AngularJS<br> * Frontend Server/ Framework, using Node.JS<br> * Frontend Server/ Framework, using Node.JS, using Express<br> * API Server/ Framework, using NodeJS<br> * API Server/ Framework, using NodeJS, using Express<br><b>Help</b>:<br> * Dedicated/searchable user group for questions<br> * Dedicated/searchable user group for questions, using Google Groups<br> * Dedicated/searchable user group for questions, using Facebook<br> * Dedicated/searchable user group for questions, response time mostly under a day<br> * Example application<br> * Tutorial screencast in English<br> * Tutorial screencast in English, using Youtube<br> * Dedicated chatroom<br><b>File Organization</b>:<br> * Basic sourcecode organization, module(->submodule)->side, with type subfolders<br> * Module directories hold controllers<br> * Module directories hold services<br> * Module directories hold templates<br> * Module directories hold unit tests<br> * Separate route configuration files for each module<br><b>Code Modularization</b>:<br> * Modularized Functionality<br> * Approach to AngularJS modules, No global 'app' module variable<br> * Approach to AngularJS modules, No global 'app' module variable without an IIFE<br><b>Model</b>:<br> * Setup of persistent storage<br> * Setup of persistent storage, using NoSQL db<br> * Setup of persistent storage, using NoSQL db, using MongoDB<br><b>View</b>:<br> * No XHR calls in controllers<br> * Templates, using Angular directives<br> * Approach to data readiness, prevents Flash of Unstyled/compiled Content (FOUC)<br><b>Control</b>:<br> * Approach to frontend routing or state changing, example of it<br> * Approach to frontend routing or state changing, State-based routing<br> * Approach to frontend routing or state changing, State-based routing, using ui-router<br> * Approach to frontend routing or state changing, HTML5 Mode<br> * Approach to frontend code loading, using angular.bootstrap()<br><b>Client/Server Communication</b>:<br> * Serve status codes only as responses<br> * Accept nested, JSON parameters<br> * Add timer header to requests<br> * Support for signed and encrypted cookies<br> * Serve URLs based on the route definitions<br> * Can serve headers only<br> * Approach to XHR calls, using JSON<br> * Approach to XHR calls, using $resource (angular-resource)<br><b>Support for things</b>:<br> * Languages, JavaScript (server side)<br> * Languages, Swig<br><b>Syntax, language and coding</b>:<br> * JavaScript 5 best practices, Use 'use strict'<br><b>Tool Configuration/customization</b>:<br> * Separate runtime configuration profiles<br><b>Testing</b>:<br> * Testing, using Jasmine<br> * Testing, using Karma<br> * Client-side unit tests<br> * Continuous integration (CI)<br> * Automated device testing, using Live Reload<br> * Server-side integration & unit tests<br> * Server-side integration & unit tests, using Mocha<br><b>Development and debugging</b>:<br> * Command line interface (CLI)<br><b>Build</b>:<br> * Build-time Dependency Management, using npm<br> * Build-time Dependency Management, using bower<br> * Build tool / Task runner, using Grunt<br> * Build tool / Task runner, using gulp<br> * Development build, script<br> * Development build, reload build script file upon change<br> * Development build, copy assets to build or dist or target folder<br> * Development build, html page processing<br> * Development build, html page processing, inject references by searching directories<br> * Development build, html page processing, inject references by searching directories, injects js references<br> * Development build, html page processing, inject references by searching directories, injects css references<br> * Development build, LESS/SASS/etc files are linted, compiled<br> * Development build, JavaScript style checking<br> * Development build, JavaScript style checking, using jshint or jslint<br> * Development build, run unit tests<br> * Production build, script<br> * Production build, concatenation (aggregation, globbing, bundling) (If you add debug:true to your config/env/development.js the will not be <br>uglified)<br> * Production build, minification<br> * Production build, safe pre-minification, using ng-annotate<br> * Production build, uglification<br> * Production build, make static pages for SEO<br><b>Code Generation</b>:<br> * FEATURE (a.k.a. module, entity) generator (README.md<br>feature css<br>routes<br>controller<br>view<br>additional menu item)<br><b>Implemented Functionality</b>:<br> * 404 Page<br> * 500 Page<br> * Account Management<br> * Account Management, register/login/logout<br> * Account Management, is password manager friendly<br> * Front-end CRUD<br> * Full-stack CRUD<br> * Full-stack CRUD, with Read<br> * Full-stack CRUD, with Create, Update and Delete<br> * Google Analytics<br> * Menus system<br> * Realtime data sync<br> * Realtime data sync, using socket.io<br> * Styles, using Bootstrap<br><b>Performance</b>:<br> * Javascript performance thing<br> * Javascript performance thing, using lodash<br> * One event-loop thread handles all requests<br> * Configurable response caching (Express plugin<br><b>https</b>://www.npmjs.org/package/apicache)<br> * Clustered HTTP sessions<br><b>Security</b>:<br> * JavaScript obfuscation<br> * https<br> * Authentication, using Oauth<br> * Authentication, Basic (With Passport or others)<br> * Authentication, Digest (With Passport or others)<br> * Authentication, Token (With Passport or others)<br></td></tr></tbody></table>
5 回答
它们基本相同......它们都使用swig进行模板化，它们都使用业力和摩卡进行测试，护照集成，nodemon等 .
为何如此相似？ Mean.js是Mean.io的一个分支，两个计划都是由the same guy开始的...... Mean.io现在在Linnovate公司的保护下，看起来那个人（Amos Haviv）停止了他与该公司的合作并开始意味着.js文件 . 您可以阅读更多有关here的原因 .
现在......您现在可以看到的主要（或很小）差异是：
SCAFFOLDING AND BOILERPLATE GENERATION
Mean.io使用名为'mean'的自定义cli工具
Mean.js使用Yeoman Generators
MODULARITY
Mean.io使用更自包含的节点包模块化，模块内部包含客户端和服务器文件 .
Mean.js仅在前端使用模块（用于角度），并使用Express连接它们 . 虽然他们也在研究垂直模块......
BUILD SYSTEM
Mean.io最近已经开始了
Mean.js使用grunt
DEPLOYMENT
两者都在他们各自的repos中有Dockerfiles，而Mean.io在Google Compute Engine上一键安装，而Mean.js也可以用one-click install on Digital Ocean部署 .
DOCUMENTATION
Mean.io有好的文档
Mean.js有很棒的文档
COMMUNITY
Mean.io拥有更大的社区，因为它是最初的样板
Mean.js势头较小但增长稳定
在个人层面上，我更喜欢MeanJS的理念和开放性，以及更多MeanIO的牵引和模块/包方法 . 两者都很好，你选择其中一个真的出错了 . 只需将它们作为起点和学习练习 .
替代“平均”解决方案
MEAN是一种通用方式（由Valeri Karpov创造）来描述以"Mongo + Express + Angular + Node"作为堆栈基础的样板/框架 . 您可以找到使用此堆栈的框架，这些框架使用其他面额，其中一些非常适合RAD（快速应用程序开发）和构建SPA . 例如：
Meteor . 现在官方Angular support，代表great MEAN stack
StrongLoop Loopback（主要Node.js核心贡献者和Express maintainers）
Generator Angular Fullstack
Sails.js
Cleverstack
Deployd等（还有更多）
你也有Hackathon Starter . 它没有't have A of MEAN (it is ' MEN'），但它摇滚..
玩得开心！
首先， MEAN 是 M ongoDB， E xpress， A ngular和 N ode.js的首字母缩写 .
它通常在"stack"中识别这些技术的组合使用 . 没有“MEAN框架”这样的东西 .
Lior Kesos在Linnovate利用了这种混乱 . 他买了域MEAN.io并在https://github.com/linnovate/mean放了一些代码
幸运的是，他们收到了很多宣传，而且关于MEAN的文章和视频越来越多 . 当你谷歌“卑鄙的框架”时，mean.io是列表中的第一个 .
不幸的是，https://github.com/linnovate/mean的代码设计得很差 .
二月份，我自己陷入陷阱 . 网站mean.io有一个吸引人的设计，Github回购有1000颗星 . 质疑质量的想法甚至没有在我脑海中浮现 . 我开始尝试它，但是没有花太多时间来偶然发现那些不起作用的东西，以及令人费解的代码 .
提交历史也非常令人担忧 . 他们多次重新设计代码和目录结构，并且合并新的更改太费时间了 .
关于mean.io和mean.js代码的好处是它们带有Bootstrap集成 . 他们还通过PassportJs进行了Facebook，Github，Linkedin等认证，以及MongoDB后端的模型（文章）示例，它与AngularJS的前端模型同步 .
根据Linnovate的网站：
从网站上看起来就是他们的核心技能集是Drupal（PHP内容管理系统），最近才开始使用Node.js和AngularJS .
最近我正在阅读Mean.js Blog，事情变得更加清晰 . 我的理解是，主要的Javascript开发人员（Amos Haviv）离开了Linnovate，在Mean.js上工作，离开MEAN.io项目的人是新手Node.js开发人员，他们正在放慢对事情应该如何工作的理解 .
在未来，事情可能会改变，但现在我会避免使用mean.io.如果您正在为快速入门寻找样板，则Mean.js似乎比mean.io更好 .
以下是几个应用程序启动器/生成器和其他技术（包括MEAN.js，MEAN.io和cleverstack）的并排比较 . 随着时间的推移，我不断添加备选方案，当发生这种情况时，潜在提供的好处列表也在不断增长 . 今天大约1600岁 . 如果有人想帮助提高其准确性或完整性，请单击下一个链接并对您知道的事项进行问卷调查 .
Compare app technologies project
从该数据库中，系统生成如下报告：
MeanJS vs MeanIO trade-off report
我的比较电子表格的The Starter Trade-offs sheet在每个生成器之间进行了全面的一对一比较 . 所以不再需要歪曲地挑选出你最喜欢的东西 .
这是generator-angular-fullstack和MEAN.js之间的那个 . 百分比是基于我个人权重的每个福利的值，其中完美的发电机将是100％
generator- angular- fullstack提供8％，MEANJS.org没有
1.9％客户端端到端测试
0.6％出厂
0.5％提供者
0.4％SASS
0.4％少
0.4％指南针
0.4％装饰者
0.4％ endpoints 子发电机
0.4％评论
0.3％FontAwesome
0.3％在调试模式下运行服务器
0.3％将生成器答案保存到文件中
0.2％不变
0.2％开发构建脚本：......用CDN版本替换第三方代表
0.2％身份验证 - Cookie
0.2％身份验证 - JSON Web令牌（JWT）
0.2％服务器端日志记录
0.1％开发构建脚本：并行运行任务以加快速度
0.1％开发构建脚本：重命名资产文件以防止浏览器缓存
0.1％开发构建脚本：运行端到端测试
0.1％ 生产环境 构建脚本：安全预先缩小
0.1％ 生产环境 构建脚本：添加CSS供应商前缀
0.1％Heroku部署自动化
0.1％的 Value
0.1％玉
0.1％Coffeescript
0.1％Serverside认证路由限制
0.1％SASS版本的Twitter Bootstrap
0.1％ 生产环境 构建脚本：压缩图像
0.1％OpenShift部署自动化
MeanJS.org . 提供9％的发电机角度 - fullstack没有
3.7％专用/可搜索用户组：响应时间大多在一天之内
0.4％生成路线
0.4％身份验证 - Oauth
0.4％配置
0.4％i18n，本地化
0.4％输入应用程序配置文件
0.3％FEATURE（a.k.a . 模块，实体，crud-mock）
0.3％菜单系统
0.3％制作子组件的选项
0.3％测试 - 客户端
0.3％Javascript性能的事情
0.3％ 生产环境 构建脚本：为SEO制作静态页面
0.2％快速安装？
0.2％专用/可搜索用户组
0.1％开发构建脚本：在更改时重新加载构建文件
0.1％开发构建脚本：编译为JS的咖啡文件
0.1％控制器 - 服务器端
0.1％型号 - 服务器端
0.1％路由 - 服务器端
0.1％测试 - 服务器端
0.1％Swig
IP欺骗
0.1％安全
0.1％ 生产环境 构建脚本：uglification
0.0％查看方法：网址以"#!"开头
0.0％前端服务和ajax调用的方法：使用$ resource
这是MEAN.io和MEAN.js之间的一种更易读的格式
我很惊讶没人提到Yeoman发电机angular-fullstack . 它是头号Yeoman社区生成器，目前在generator page上使用了1490颗星，使用Swig进行模板化 . 它可以搭建护照内置的脚手架 .