MEAN.js和MEAN.io的区别

首先，MEAN是MongoDB、Express、Angular和Node.js的首字母缩写。

它通常在“堆栈”中标识这些技术的组合使用。没有所谓的“均值框架”。

Linnovate的Lior Kesos利用了这种混乱。他买了域名MEAN。IO，并把一些代码放在https://github.com/linnovate/mean

幸运的是，他们得到了大量的宣传，关于MEAN的文章和视频越来越多。当你谷歌“mean framework”时，mean。IO是列表中的第一个。

不幸的是，https://github.com/linnovate/mean上的代码似乎设计得很糟糕。

今年2月，我自己也掉进了陷阱。站点意味着。io有一个吸引人的设计，Github回购有1000+星。我根本没想过要质疑它的品质。我开始用它做实验，但没过多久就发现了一些不能工作的东西，以及一些令人费解的代码。

提交历史也非常令人担忧。他们多次重新设计代码和目录结构，合并新的更改太费时了。

两者的优点都意味着。i . io和mean.js代码的优点是它们带有Bootstrap集成。它们还带有Facebook, Github, Linkedin等通过PassportJs和MongoDB后端模型(文章)的示例进行身份验证，与AngularJS的前端模型同步。

Linnovate网站显示:

Linnovate是以色列领先的开源公司在国内经验丰富的团队，致力于打造高端开源解决方案。Linnovate是以色列唯一一家为企业提供全方位的建设和维护服务他们的下一个网络项目。

从网站上看，他们的核心技能是Drupal(一个PHP内容管理系统)，直到最近他们才开始使用Node.js和AngularJS。

最近我在看Mean.js博客，事情变得更清楚了。我的理解是，主要的Javascript开发人员(Amos Haviv)离开Linnovate去做MEAN. js。io项目的开发人员是Node.js的新手，他们正在慢慢理解事情是如何工作的。

将来情况可能会改变，但现在我会避免使用mean.io。如果你正在寻找一个快速入门的样板文件，Mean.js似乎比mean.io更好。

2014-04-26 03:39:32

我的比较电子表格的初始权衡表在每个生成器之间进行了全面的一对一比较。所以没有必要再扭曲地挑选你最喜欢的东西来谈论。

这里是generator-angular-fullstack和MEAN.js之间的一个。百分比是基于我个人权重的每个收益的值，其中完美的生成器将是100%

generator- angular- fullstack提供了8%，这是MEANJS.org所没有的

1.9% Client-side end-to-end tests 0.6% factory 0.5% provider 0.4% SASS 0.4% LESS 0.4% Compass 0.4% decorator 0.4% Endpoint subgenerator 0.4% Comments 0.3% FontAwesome 0.3% Run server in debug mode 0.3% Save generator answers to a file 0.2% constant 0.2% Development build script: ...... replace 3rd party deps with CDN versions 0.2% Authentication - Cookie 0.2% Authentication - JSON Web Token (JWT) 0.2% Server-side logging 0.1% Development build script: run tasks in parallel to speed it up 0.1% Development build script: Renames asset files to prevent browser caching 0.1% Development build script: run end to end tests 0.1% Production build script: safe pre-minification 0.1% Production build script: add CSS vendor prefixes 0.1% Heroku deployment automation 0.1% value 0.1% Jade 0.1% Coffeescript 0.1% Serverside authenticated route restriction 0.1% SASS version of Twitter Bootstrap 0.1% Production build script: compress images 0.1% OpenShift deployment automation

MeanJS.org。提供generator- angle -fullstack所没有的9%

3.7% Dedicated/searchable user group: response time mostly under a day 0.4% Generate routes 0.4% Authentication - Oauth 0.4% config 0.4% i18n, localization 0.4% Input application profile 0.3% FEATURE (a.k.a. module, entity, crud-mock) 0.3% Menus system 0.3% Options for making subcomponents 0.3% test - client side 0.3% Javascript performance thing 0.3% Production build script: make static pages for SEO 0.2% Quick install? 0.2% Dedicated/searchable user group 0.1% Development build script: reload build file upon change 0.1% Development build script: coffee files compiled to JS 0.1% controller - server side 0.1% model - server side 0.1% route - server side 0.1% test - server side 0.1% Swig 0.1% Safe from IP Spoofing 0.1% Production build script: uglification 0.0% Approach to views: URLs start with "#!" 0.0% Approach to frontend services and ajax calls: uses $resource

这是MEAN之间的一个。io和MEAN.js的格式

<table border="1" cellpadding="10"><tbody><tr><td valign="top" width="33%"> <h1>MeanJS.org. provides these benefits that MEAN.io. doesn't</h1> Help:     * Dedicated/searchable user group for questions, using github issues     * There's a book about it File Organization:     * Basic sourcecode organization, module(->submodule)->side     * Module directories hold directives Code Modularization:     * Approach to AngularJS modules, Only one module definition per file     * Approach to AngularJS modules, Don’t alter a module other than where it is defined Model:     * Object-relational mapping     * Server-side validation, server-side example     * Client side validation, using Angular 1.3 View:     * Approach to AngularJS views, Directives start with "data-"     * Approach to data readiness, Use ng-init Control:     * Approach to frontend routing or state changing, URLs start with '#!'     * Approach to frontend routing or state changing, Use query parameters to store route state Support for things:     * Languages, LESS     * Languages, SASS Syntax, language and coding:     * JavaScript 5 best practices, Don't use "new" Testing:     * Testing, using Mocha     * End-to-end tests     * End-to-end tests, using Protractor     * Continuous integration (CI), using Travis Development and debugging:     * Command line interface (CLI), using Yeoman Build:     * Build configurations file(s)     * Deployment automation, using Azure     * Deployment automation, using Digital Ocean, screencast of it     * Deployment automation, using Heroku, screencast of it Code Generation:     * Input application profile     * Quick install?     * Options for making subcomponents     * config generator     * controller (client side) generator     * directive generator     * filter generator     * route (client side) generator     * service (client side) generator     * test - client side     * view or view partial generator     * controller (server side) generator     * model (server side) generator     * route (server side) generator     * test (server side) generator Implemented Functionality:     * Account Management, Forgotten Password with Resetting     * Chat     * CSV processing     * E-mail sending system     * E-mail sending system, using Nodemailer     * E-mail sending system, using its own e-mail implementation     * Menus system, state-based     * Paypal integration     * Responsive design     * Social connections management page Performance:     * Creates a favicon Security:     * Safe from IP Spoofing     * Authorization, Access Contol List (ACL)     * Authentication, Cookie     * Websocket and RESTful http share security policies </td><td valign="top" width="33%"> <h1>MEAN.io. provides these benefits that MeanJS.org. doesn't</h1> Quality:     * Sponsoring company Help:     * Docs with flatdoc Code Modularization:     * Share code between projects     * Module manager View:     * Approach to data readiness, Use state.resolve() Control:     * Approach to frontend code loading, Use AMD with Require.js     * Approach to frontend code loading, using wiredep     * Approach to error handling, Server-side logging Client/Server Communication:     * Centralized event handling     * Approach to XHR calls, using $http and $q Syntax, language and coding:     * JavaScript 5 best practices, Wrap code in an IIFE (SEAF, SIAF) Development and debugging:     * API introspection report and testing interface, using Swagger     * Command line interface (CLI), using Independent command line interface Build:     * Development build, add IIFEs (SEAF, SIAF) to executable copies of code     * Deployment automation     * Deployment automation, using Heroku Code Generation:     * Scaffolding undo    (mean package -d <name>)     * FEATURE (a.k.a. module, entity) generator, Menu items added for new features Implemented Functionality:     * Admin page for users and roles     * Content Management System    (Use special data-bound directives in your templates. Switch to edit mode and you can edit the values right where you see them)     * File Upload     * i18n, localization     * Menus system, submenus     * Search     * Search, actually works with backend API     * Search, using Elastic Search     * Styles, using Bootstrap, using UI Bootstrap AngularJS directives     * Text (WYSIWYG) Editor     * Text (WYSIWYG) Editor, using medium-editor Performance:     * Instrumentation, server-side Security:     * Serverside authenticated route restriction     * Authentication, using Oauth, Link multiple Oauth strategies to one account     * Authentication, JSON Web Token (JWT) </td><td valign="top" width="33%"> <h1>MEAN.io. and MeanJS.org. both provide these benefits</h1> Quality:     * Version Control, using git Platforms:     * Client-side JS Framework, using AngularJS     * Frontend Server/ Framework, using Node.JS     * Frontend Server/ Framework, using Node.JS, using Express     * API Server/ Framework, using NodeJS     * API Server/ Framework, using NodeJS, using Express Help:     * Dedicated/searchable user group for questions     * Dedicated/searchable user group for questions, using Google Groups     * Dedicated/searchable user group for questions, using Facebook     * Dedicated/searchable user group for questions, response time mostly under a day     * Example application     * Tutorial screencast in English     * Tutorial screencast in English, using Youtube     * Dedicated chatroom File Organization:     * Basic sourcecode organization, module(->submodule)->side, with type subfolders     * Module directories hold controllers     * Module directories hold services     * Module directories hold templates     * Module directories hold unit tests     * Separate route configuration files for each module Code Modularization:     * Modularized Functionality     * Approach to AngularJS modules, No global 'app' module variable     * Approach to AngularJS modules, No global 'app' module variable without an IIFE Model:     * Setup of persistent storage     * Setup of persistent storage, using NoSQL db     * Setup of persistent storage, using NoSQL db, using MongoDB View:     * No XHR calls in controllers     * Templates, using Angular directives     * Approach to data readiness, prevents Flash of Unstyled/compiled Content (FOUC) Control:     * Approach to frontend routing or state changing, example of it     * Approach to frontend routing or state changing, State-based routing     * Approach to frontend routing or state changing, State-based routing, using ui-router     * Approach to frontend routing or state changing, HTML5 Mode     * Approach to frontend code loading, using angular.bootstrap() Client/Server Communication:     * Serve status codes only as responses     * Accept nested, JSON parameters     * Add timer header to requests     * Support for signed and encrypted cookies     * Serve URLs based on the route definitions     * Can serve headers only     * Approach to XHR calls, using JSON     * Approach to XHR calls, using $resource (angular-resource) Support for things:     * Languages, JavaScript (server side)     * Languages, Swig Syntax, language and coding:     * JavaScript 5 best practices, Use 'use strict' Tool Configuration/customization:     * Separate runtime configuration profiles Testing:     * Testing, using Jasmine     * Testing, using Karma     * Client-side unit tests     * Continuous integration (CI)     * Automated device testing, using Live Reload     * Server-side integration & unit tests     * Server-side integration & unit tests, using Mocha Development and debugging:     * Command line interface (CLI) Build:     * Build-time Dependency Management, using npm     * Build-time Dependency Management, using bower     * Build tool / Task runner, using Grunt     * Build tool / Task runner, using gulp     * Development build, script     * Development build, reload build script file upon change     * Development build, copy assets to build or dist or target folder     * Development build, html page processing     * Development build, html page processing, inject references by searching directories     * Development build, html page processing, inject references by searching directories, injects js references     * Development build, html page processing, inject references by searching directories, injects css references     * Development build, LESS/SASS/etc files are linted, compiled     * Development build, JavaScript style checking     * Development build, JavaScript style checking, using jshint or jslint     * Development build, run unit tests     * Production build, script     * Production build, concatenation (aggregation, globbing, bundling)    (If you add debug:true to your config/env/development.js the will not be uglified)     * Production build, minification     * Production build, safe pre-minification, using ng-annotate     * Production build, uglification     * Production build, make static pages for SEO Code Generation:     * FEATURE (a.k.a. module, entity) generator    (README.md feature css routes controller view additional menu item) Implemented Functionality:     * 404 Page     * 500 Page     * Account Management     * Account Management, register/login/logout     * Account Management, is password manager friendly     * Front-end CRUD     * Full-stack CRUD     * Full-stack CRUD, with Read     * Full-stack CRUD, with Create, Update and Delete     * Google Analytics     * Menus system     * Realtime data sync     * Realtime data sync, using socket.io     * Styles, using Bootstrap Performance:     * Javascript performance thing     * Javascript performance thing, using lodash     * One event-loop thread handles all requests     * Configurable response caching    (Express plugin https://www.npmjs.org/package/apicache)     * Clustered HTTP sessions Security:     * JavaScript obfuscation     * https     * Authentication, using Oauth     * Authentication, Basic    (With Passport or others)     * Authentication, Digest    (With Passport or others)     * Authentication, Token    (With Passport or others) </td></tr></tbody></table>

2014-07-24 11:12:55

我很惊讶没有人提到Yeoman生成器角-全栈。它是第一个Yeoman社区生成器，目前生成器页面上有1490颗星，而Mean.js只有81颗星(诚然，考虑到MEANJS是多么新的，这个比较并不公平)。在我写这篇文章时，它似乎正在积极维护，并且在2.05版本中。与MEANJS不同，它不使用Swig来创建模板。它可以搭在脚手架上，内置护照。

2014-07-23 10:01:21

这里是几个应用程序启动器/生成器和其他技术的并排比较，包括MEAN.js, MEAN。Io，和cleverstack。只要有时间，我就会不断添加替代方案，而在这种情况下，潜在的好处也在不断增加。今天已经上升到1600左右。如果有人想帮助提高准确性或完整性，请点击下一个链接，就你知道的事情做一份问卷调查。

比较应用技术项目

从这个数据库中，系统生成如下报告:

MeanJS vs MeanIO权衡报告

2014-06-26 22:29:14

首先，MEAN是MongoDB、Express、Angular和Node.js的首字母缩写。

它通常在“堆栈”中标识这些技术的组合使用。没有所谓的“均值框架”。

Linnovate的Lior Kesos利用了这种混乱。他买了域名MEAN。IO，并把一些代码放在https://github.com/linnovate/mean

幸运的是，他们得到了大量的宣传，关于MEAN的文章和视频越来越多。当你谷歌“mean framework”时，mean。IO是列表中的第一个。

不幸的是，https://github.com/linnovate/mean上的代码似乎设计得很糟糕。

今年2月，我自己也掉进了陷阱。站点意味着。io有一个吸引人的设计，Github回购有1000+星。我根本没想过要质疑它的品质。我开始用它做实验，但没过多久就发现了一些不能工作的东西，以及一些令人费解的代码。

提交历史也非常令人担忧。他们多次重新设计代码和目录结构，合并新的更改太费时了。

两者的优点都意味着。i . io和mean.js代码的优点是它们带有Bootstrap集成。它们还带有Facebook, Github, Linkedin等通过PassportJs和MongoDB后端模型(文章)的示例进行身份验证，与AngularJS的前端模型同步。

Linnovate网站显示:

Linnovate是以色列领先的开源公司在国内经验丰富的团队，致力于打造高端开源解决方案。Linnovate是以色列唯一一家为企业提供全方位的建设和维护服务他们的下一个网络项目。

从网站上看，他们的核心技能是Drupal(一个PHP内容管理系统)，直到最近他们才开始使用Node.js和AngularJS。

最近我在看Mean.js博客，事情变得更清楚了。我的理解是，主要的Javascript开发人员(Amos Haviv)离开Linnovate去做MEAN. js。io项目的开发人员是Node.js的新手，他们正在慢慢理解事情是如何工作的。

将来情况可能会改变，但现在我会避免使用mean.io。如果你正在寻找一个快速入门的样板文件，Mean.js似乎比mean.io更好。

2014-04-26 03:39:32

它们本质上是一样的……他们都使用swig作为模板，他们都使用karma和mocha进行测试，护照集成，nodemon等。

为什么如此相似?js是Mean的一个分支。IO和这两个项目都是由同一个人发起的…的意思。io现在在Linnovate公司的保护伞下，看起来就像那个家伙(Amos Haviv)停止了与该公司的合作，并开始了Mean.js。你可以在这里读到更多的原因。

现在…你现在可以看到的主要(或小)差异是:

脚手架和样板生成

的意思。IO使用自定义命令行工具'mean' js使用Yeoman生成器

模块化

的意思。IO使用更独立的节点包模块性，在模块中包含客户端和服务器文件。 js只在前端使用模块(用于angular)，并将它们与Express连接起来。尽管他们也在研究垂直模块……

构建系统

的意思。IO最近转向了gulp js使用grunt

部署

它们在各自的repo和Mean中都有Dockerfiles。io在谷歌计算引擎上有一键式安装，而Mean.js也可以在Digital Ocean上一键式安装部署。

文档

的意思。IO有ok文档 Mean.js有很棒的文档

社区

的意思。IO有一个更大的社区，因为它是最初的样板 Mean.js的势头较弱，但增长稳定

就个人而言，我更喜欢MeanJS的理念和开放性，而更喜欢MeanIO的吸引力和模块/包方法。两者都很好，最后你可能会修改它们，所以选择其中一个不会错。把它们作为一个起点，作为一个学习练习。

替代的“均值”解决方案

MEAN是一种通用的方法(由Valeri Karpov创造)，用来描述以“Mongo + Express + Angular + Node”为栈基础的样板文件/框架。您可以找到使用其他名称的具有此堆栈的框架，其中一些非常适合RAD(快速应用程序开发)和构建spa。例如:

流星。现在有了官方的Angular支持，它代表了一个很棒的MEAN堆栈环回(主要Node.js核心贡献者和Express维护者) Generator Angular Fullstack Sails.js Cleverstack 部署，等等(还有更多)

你还有Hackathon Starter。它没有“MEAN”(它是“MEN”)，但它很酷。

玩得开心!

2014-04-21 22:16:37

MEAN.js和MEAN.io的区别

推荐文章

最新文章

标签