我想使用MEAN JavaScript Stack,但我注意到有两个不同的堆栈,它们都有自己的网站和安装方法:mean.js和mean.io。因此,我问自己一个问题:“我使用哪个?”。
因此,为了回答这个问题,我问社区是否可以解释这两者之间的区别?以及是否有利弊?因为它们看起来和我非常相似。
他们本质上是相同的...他们都使用swig进行模板制作,他们都使用业力和摩卡咖啡进行测试,护照整合,nodemon等。
为什么如此相似?Mean.js是Mean.io的一个分支,这两个计划都是由同一个人发起的... Mean.io现在隶属于Linnovate公司,看起来这个人(Amos Haviv)停止了与该公司的合作,启动Mean.js。您可以在此处详细了解原因。
现在...您现在可以看到的主要(或很小)差异是:
脚手架和锅炉生成
Mean.io使用名为“ mean”的自定义cli工具
Mean.js使用Yeoman Generators
模块化
Mean.io使用模块中包含客户机和服务器文件的更加独立的节点包模块化。
Mean.js仅在前端使用模块(用于角度),并将其与Express连接。尽管他们也在研究垂直模块...
建立系统
Mean.io最近移至大
口吃Mean.js使用grunt
部署
两者都在各自的仓库中都有Dockerfile,Mean.io在Google Compute Engine上具有一键安装,而Mean.js也可以在Digital Ocean上具有一键安装进行部署。
资料
Mean.io拥有不错的文档
Mean.js拥有很棒的文档
社区
Mean.io有一个更大的社区,因为它是原始样板
Mean.js的动力较小但增长稳定
就个人而言,我更喜欢MeanJS的理念和开放性,更喜欢MeanIO的牵引力和模块/封装方法。两者都很不错,而且您可能最终会修改它们,因此选择一个或另一个确实不会出错。只是将它们作为起点和学习练习。
替代的“均值”解决方案
MEAN是一种通用方法(由Valeri Karpov创造),用于描述以“ Mongo + Express + Angular + Node”作为堆栈基础的样板/框架。您可以在此堆栈中找到使用其他面额的框架,其中一些框架对于RAD(快速应用程序开发)和构建SPA非常有用。例如:
- 流星。现在有了官方的Angular支持,代表了出色的MEAN堆栈
- StrongLoop回送(主要的Node.js核心贡献者和Express维护者)
- 发电机角全堆
- Sails.js
- 聪明的堆栈
- 部署等(还有更多)
您也可以使用Hackathon Starter。它没有A MEAN(它是“ MEN”),但它确实很摇晃。
玩得开心!
首先,MEAN是M ongoDB,E xpress,A ngular和N ode.js的首字母缩写。
它通常在“堆栈”中标识这些技术的组合使用。有没有这样的事“的MEAN框架”。
利奥尔Kesos在Linnovate了这种混乱的优势。他购买了域名MEAN.io,并将一些代码放在https://github.com/linnovate/mean
幸运的是,他们得到了很多宣传,并且有越来越多的关于MEAN的文章和视频。当您使用Google“平均值框架”时,mean.io是列表中的第一位。
不幸的是,https://github.com/linnovate/mean上的代码似乎设计不好。
2月,我本人陷入陷阱。该网站mean.io的设计醒目,Github仓库拥有1000多颗星。对质量提出质疑的想法甚至都没有想到。我开始尝试它,但花了很短的时间才偶然发现不起作用的事情,并使代码感到困惑。
提交历史也令人担忧。他们多次重新设计了代码和目录结构,并且合并新的更改非常耗时。
关于mean.io和mean.js代码的好处在于,它们具有Bootstrap集成。它们还通过PassportJs进行了Facebook,Github,Linkedin等身份验证,并在MongoDB的后端提供了与AngularJS的前端模型同步的模型示例(文章)。
根据Linnovate的网站:
Linnovate是以色列领先的开源公司,拥有该国经验最丰富的团队,致力于创建高端开源解决方案。Linnovate是以色列唯一一家为企业建立和维护其下一个Web项目的企业提供AZ服务的公司。
从网站看来,他们的核心技能是Drupal(一种PHP内容管理系统),直到最近他们才开始使用Node.js和AngularJS。
最近,我正在阅读Mean.js博客,事情变得更加清晰。我的理解是,主要的Java语言开发人员(Amos Haviv)离开Linnovate从事Mean.js的工作,离开了MEAN.io项目,而那些是Node.js新手的开发人员正在减慢对事物应该如何工作的理解。
将来情况可能会发生变化,但现在我会避免使用mean.io。如果您正在寻找快速入门的样板,那么Mean.js似乎比mean.io更好。
这是几种应用程序启动器/生成器和其他技术(包括MEAN.js,MEAN.io和cleverstack)的并排比较。我会在寻找时间时不断添加替代方法,并且随着时间的推移,潜在提供的好处的列表也在不断增长。如今,它已达到1600左右。如果有人想帮助提高其准确性或完整性,请单击下一个链接,并就您所知道的内容进行问卷调查。
系统从该数据库中生成如下报告:
我的比较电子表格的“初学者权衡”工作表在每个生成器之间进行了全面的一对一比较。因此,您无需再扭曲挑剔的话来谈论您的最爱。
这是generator-angular-fullstack和MEAN.js之间的代码。百分比是基于我个人权重的每种福利的价值,其中理想的生成者为100%
generator-angle-fullstack提供了MEANJS.org没有提供的8%
- 1.9%的客户端端到端测试
- 0.6%的工厂
- 0.5%的提供者
- SASS 0.4%
- 减少0.4%
- 指南针0.4%
- 0.4%装饰
- 0.4%端点子生成器
- 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%Production build脚本:安全的最小化
- 0.1%生产构建脚本:添加CSS供应商前缀
- 0.1%Heroku部署自动化
- 值0.1%
- 玉0.1%
- 0.1%咖啡
- 0.1%服务器端身份验证的路由限制
- Twitter Bootstrap的0.1%SASS版本
- 0.1%Production build脚本:压缩图像
- 0.1%OpenShift部署自动化
MeanJS.org。提供了9%的generator-angular-fullstack无法提供的功能
- 3.7%专用/可搜索的用户组:响应时间大部分在一天之内
- 0.4%生成路线
- 0.4%验证-Oauth
- 0.4%的配置
- i18n,本地化率为0.4%
- 0.4%输入应用程序配置文件
- 0.3%的功能(又名模块,实体,实体模拟)
- 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%痛饮
- IP欺骗提供0.1%的安全
- 0.1%生产构建脚本:丑陋
- 0.0%的浏览方式:URL以“#!”开头
- 0.0%的前端服务和Ajax调用方法:使用$ resource
这是MEAN.io和MEAN.js之间的格式,更易读
<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>
文章标签:angularjs , javascript , mean-stack , node.js , web-applications
版权声明:本文为原创文章,版权归 javascript 所有,欢迎分享本文,转载请保留出处!
评论已关闭!