CMP*_*res 334 javascript web-applications node.js angularjs mean-stack
我想使用MEAN JavaScript Stack,但我注意到有两个不同的堆栈,它们有自己的网站和安装方法:mean.js和mean.io. 所以我想问自己这个问题:"我使用哪一个?".
所以为了回答这个问题,我问社区你是否可以解释这两者之间有什么区别?如果可能的利弊?因为它们看起来和我很相似.
SDu*_*ude 374
它们基本相同......它们都使用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最近已经
开始使用了意大利人.Ges使用了咕噜声
部署
两者都有各自的Repos中的Dockerfiles ,而Mean.io可以在Google Compute Engine上一键安装,而Mean.js也可以在Digital Ocean上一键安装.
文档
Mean.io有ok文档
Mean.js有AWESOME文档
社区
Mean.io有一个更大的社区,因为它是最初的样板
Mean.js动力较小但增长稳定
在个人层面上,我更喜欢MeanJS的理念和开放性,以及更多MeanIO的牵引和模块/包方法.两者都很好,你最终可能会修改它们,所以你选择其中一个就不会出错.只需将它们作为起点和学习练习.
MEAN是一种通用的方式(由Valeri Karpov创造)来描述以"Mongo + Express + Angular + Node"作为堆栈基础的样板/框架.您可以找到使用此堆栈的框架,这些框架使用其他面额,其中一些非常适合RAD(快速应用程序开发)和构建SPA.例如:
你也有Hackathon Starter.它没有A的意思(它是'MEN'),但它摇滚..
玩得开心!
Chr*_*lli 66
首先,MEAN是M ongoDB,E xpress,A ngular和N ode.js 的首字母缩写.
它通常在"堆栈"中识别这些技术的组合使用.有没有这样的事" 的 MEAN框架".
利奥尔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的网站:
Linnovate是以色列领先的开源公司,拥有该国最有经验的团队,致力于创建高端开源解决方案.Linnovate是以色列唯一一家为企业提供AZ服务以建立和维护其下一个Web项目的公司.
从网站上看,他们的核心技能集是Drupal(PHP内容管理系统),最近才开始使用Node.js和AngularJS.
最近我正在阅读Mean.js博客,事情变得更加清晰.我的理解是,主要的Javascript开发人员(Amos Haviv)离开了Linnovate,在Mean.js上工作,离开MEAN.io项目的人是新手Node.js的开发人员,他们正在放慢对事情应该如何工作的理解.
在未来,事情可能会改变,但现在我会避免使用mean.io. 如果您正在为快速入门寻找样板,则Mean.js似乎比mean.io更好.
Dan*_*cro 19
以下是几个应用程序启动器/生成器和其他技术(包括MEAN.js,MEAN.io和cleverstack)的并排比较.随着时间的推移,我不断添加备选方案,当发生这种情况时,潜在提供的好处列表也在不断增长.今天大约1600岁.如果有人想帮助提高其准确性或完整性,请单击下一个链接并对您知道的事项进行问卷调查.
从该数据库中,系统生成如下报告:
Dan*_*cro 13
我的比较电子表格的Starter Trade-offs表格在每个发生器之间进行了全面的一对一比较.所以不再需要歪曲地挑选出你最喜欢的东西.
这是generator-angular-fullstack和MEAN.js之间的那个.百分比是基于我个人权重的每个福利的值,其中完美的发电机将是100%
generator- angular- fullstack提供8%,MEANJS.org没有
MeanJS.org.提供9%的发电机角度 - fullstack没有
这是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>
Run Code Online (Sandbox Code Playgroud)
我很惊讶没有人提到过Yeoman发电机角度 - 全栈.它是头号Yeoman社区发电机,目前在发电机页面上有1490颗星与Mean.js的81颗星(鉴于新MEANJS是多么公平的比较).它似乎是积极维护的,在我写这篇文章的时候是版本2.05.与MEANJS不同,它不使用Swig进行模板化.它可以搭建护照内置的脚手架.
归档时间: |
|
查看次数: |
109329 次 |
最近记录: |