本文翻译自：Difference between MEAN.js and MEAN.io
I wanted to use the MEAN JavaScript Stack, but I noticed that there are two different stacks with either their own website and installation methods: mean.js and mean.io. 我想使用MEAN JavaScript Stack，但我注意到有两个不同的堆栈，它们有自己的网站和安装方法：mean.js和mean.io. So I came up asking myself this question: "Which one do I use?". 所以我想问自己这个问题：“我使用哪一个？”。
So in order to answer this question I ask the community if you could explain what are the differences between these two? 所以为了回答这个问题，我问社区你是否可以解释这两者之间有什么区别？ And if possible pros and cons? 如果可能的利弊？ Because they look very similar to me. 因为它们看起来和我很相似。
#1楼
参考：https://stackoom.com/question/1ZLDk/MEAN-js和MEAN-io之间的区别
#2楼
They're essentially the same... They both use swig for templating, they both use karma and mocha for tests, passport integration, nodemon, etc. 它们基本相同......它们都使用swig进行模板化，它们都使用业力和摩卡进行测试，护照集成，nodemon等。
Why so similar? 为何如此相似？ Mean.js is a fork of Mean.io and both initiatives were started by the same guy ... Mean.io is now under the umbrella of the company Linnovate and looks like the guy (Amos Haviv) stopped his collaboration with this company and started Mean.js. Mean.js是Mean.io的一个分支，两个倡议都是由同一个人开始的...... Mean.io现在在Linnovate公司的保护伞下，看起来那个人（Amos Haviv）停止了与这家公司的合作，开始Mean.js. You can read more about the reasons here . 您可以在此处详细了解原因。
Now... main (or little) differences you can see right now are: 现在......您现在可以看到的主要（或很小）差异是：
SCAFFOLDING AND BOILERPLATE GENERATION 脚手架和锅炉生成
Mean.io uses a custom cli tool named 'mean' Mean.io使用名为'mean'的自定义cli工具
Mean.js uses Yeoman Generators Mean.js使用Yeoman Generators
MODULARITY 模块性
Mean.io uses a more self-contained node packages modularity with client and server files inside the modules. Mean.io使用更自包含的节点包模块化，模块内部包含客户端和服务器文件。
Mean.js uses modules just in the front-end (for angular), and connects them with Express. Mean.js仅在前端使用模块（用于角度），并使用Express连接它们。 Although they were working on vertical modules as well... 虽然他们也在研究垂直模块......
BUILD SYSTEM 建立系统
Mean.io has recently moved to gulp Mean.io最近已经开始了
Mean.js uses grunt Mean.js使用grunt
DEPLOYMENT 部署
Both have Dockerfiles in their respective repos, and Mean.io has one-click install on Google Compute Engine , while Mean.js can also be deployed with one-click install on Digital Ocean . 两者都有各自的Repos中的Dockerfiles，而Mean.io可以在Google Compute Engine上一键安装，而Mean.js也可以在Digital Ocean上一键安装 。
DOCUMENTATION 文档
Mean.io has ok docs Mean.io有好的文档
Mean.js has AWESOME docs Mean.js有很棒的文档
COMMUNITY 社区
Mean.io has a bigger community since it was the original boilerplate Mean.io拥有更大的社区，因为它是最初的样板
Mean.js has less momentum but steady growth Mean.js势头较小但增长稳定
On a personal level, I like more the philosophy and openness of MeanJS and more the traction and modules/packages approach of MeanIO. 在个人层面上，我更喜欢MeanJS的理念和开放性，以及更多MeanIO的牵引和模块/包方法。 Both are nice, and you'll end probably modifying them, so you can't really go wrong picking one or the other. 两者都很好，你最终可能会修改它们，所以你选择其中一个就不会出错。 Just take them as starting point and as a learning exercise. 只需将它们作为起点和学习练习。
ALTERNATIVE “MEAN” SOLUTIONS 替代“平均”解决方案
MEAN is a generic way (coined by Valeri Karpov ) to describe a boilerplate/framework that takes "Mongo + Express + Angular + Node" as the base of the stack. MEAN是一种通用的方式（由Valeri Karpov创造）来描述以“Mongo + Express + Angular + Node”作为堆栈基础的样板/框架。 You can find frameworks with this stack that use other denomination, some of them really good for RAD (Rapid Application Development) and building SPAs. 您可以找到使用此堆栈的框架，这些框架使用其他面额，其中一些非常适合RAD（快速应用程序开发）和构建SPA。 Eg: 例如：
- Meteor . 流星 。 Now with official Angular support , represents a great MEAN stack 现在有了官方的Angular支持 ，代表了一个伟大的MEAN堆栈
- StrongLoop Loopback (main Node.js core contributors and Express maintainers ) StrongLoop Loopback （主要Node.js核心贡献者和Express维护者 ）
- Generator Angular Fullstack 发电机角度Fullstack
- Sails.js Sails.js
- Cleverstack Cleverstack
- Deployd, etc (there are more) Deployd等（还有更多）
You also have Hackathon Starter . 你也有Hackathon Starter 。 It doesn't have A of MEAN (it is 'MEN'), but it rocks.. 它没有A的意思（它是'MEN'），但它摇滚..
Have fun! 玩得开心！
#3楼
First of all, MEAN is an acronym for M ongoDB, E xpress, A ngular and N ode.js. 首先， MEAN是M ongoDB， E xpress， A ngular和N ode.js的首字母缩写。
It generically identifies the combined used of these technologies in a "stack". 它通常在“堆栈”中识别这些技术的组合使用。 There is no such a thing as " The MEAN framework". 有没有这样的事“ 的意味框架”。
Lior Kesos at Linnovate took advantage of this confusion. 利奥尔Kesos在Linnovate了这种混乱的优势。 He bought the domain MEAN.io and put some code at https://github.com/linnovate/mean 他购买了MEAN.io域名并在https://github.com/linnovate/mean上添加了一些代码
They luckily received a lot of publicity, and theree are more and more articles and video about MEAN. 幸运的是，他们收到了很多宣传，而且关于MEAN的文章和视频越来越多。 When you Google "mean framework", mean.io is the first in the list. 当你谷歌“卑鄙的框架”时，mean.io是列表中的第一个。
Unfortunately the code at https://github.com/linnovate/mean seems poorly engineered . 不幸的是， https：//github.com/linnovate/mean上的代码似乎设计得很差 。
In February I fell in the trap myself. 二月份，我自己陷入陷阱。 The site mean.io had a catchy design and the Github repo had 1000+ stars. 网站mean.io有一个吸引人的设计，Github回购有1000多颗星。 The idea of questioning the quality did not even pass through my mind. 质疑质量的想法甚至没有在我脑海中浮现。 I started experimenting with it but it did not take too long to stumble upon things that were not working, and puzzling pieces of code. 我开始尝试它，但是没有花太多时间来偶然发现那些不起作用的东西，以及令人费解的代码。
The commit history was also pretty concerning. 提交历史也非常令人担忧。 They re-engineered the code and directory structure multiple times, and merging the new changes is too time consuming. 他们多次重新设计代码和目录结构，并且合并新的更改太费时间了。
The nice things about both mean.io and mean.js code is that they come with Bootstrap integration. 关于mean.io和mean.js代码的好处是它们带有Bootstrap集成。 They also come with Facebook, Github, Linkedin etc authentication through PassportJs and an example of a model (Article) on the backend on MongoDB that sync with the frontend model with AngularJS. 他们还通过PassportJs进行Facebook，Github，Linkedin等身份验证，以及MongoDB后端的模型（文章）示例，该模型与AngularJS的前端模型同步。
According to Linnovate's website: 根据Linnovate的网站：
Linnovate is the leading Open Source company in Israel, with the most experienced team in the country, dedicated to the creation of high-end open source solutions. Linnovate是以色列领先的开源公司，拥有该国最有经验的团队，致力于创建高端开源解决方案。 Linnovate is the only company in Israel which gives an AZ services for enterprises for building and maintaining their next web project. Linnovate是以色列唯一一家为企业提供AZ服务以建立和维护其下一个Web项目的公司。
From the website it looks like that their core skill set is Drupal (a PHP content management system) and only lately they started using Node.js and AngularJS. 从网站上看，他们的核心技能集是Drupal（PHP内容管理系统），最近才开始使用Node.js和AngularJS。
Lately I was reading the Mean.js Blog and things became clearer. 最近我正在阅读Mean.js博客 ，事情变得更加清晰。 My understanding is that the main Javascript developer (Amos Haviv) left Linnovate to work on Mean.js leaving MEAN.io project with people that are novice Node.js developers that are slowing understanding how things are supposed to work. 我的理解是，主要的Javascript开发人员（Amos Haviv）离开了Linnovate，在Mean.js上工作，离开MEAN.io项目的人是新手Node.js的开发人员，他们正在放慢对事情应该如何工作的理解。
In the future things may change but for now I would avoid to use mean.io. 在未来，事情可能会改变，但现在我会避免使用mean.io. If you are looking for a boilerplate for a quickstart Mean.js seems a better option than mean.io. 如果您正在为快速入门寻找样板，则Mean.js似乎比mean.io更好。
#4楼
Here is a side-by-side comparison of several application starters/generators and other technologies including MEAN.js, MEAN.io, and cleverstack. 以下是几个应用程序启动器/生成器和其他技术（包括MEAN.js，MEAN.io和cleverstack）的并排比较。 I keep adding alternatives as I find time and as that happens, the list of potentially provided benefits keeps growing too. 随着时间的推移，我不断添加备选方案，当发生这种情况时，潜在提供的好处列表也在不断增长。 Today it's up to around 1600. If anyone wants to help improve its accuracy or completeness, click the next link and do a questionnaire about something you know. 今天大约1600岁。如果有人想帮助提高其准确性或完整性，请单击下一个链接并对您知道的事项进行问卷调查。
Compare app technologies project 比较应用技术项目
From this database, the system generates reports like the following: 从该数据库中，系统生成如下报告：
MeanJS vs MeanIO trade-off report MeanJS与MeanIO权衡报告
#5楼
I'm surprised nobody has mentioned the Yeoman generator angular-fullstack . 我很惊讶没有人提到过Yeoman发电机角度 - 全栈 。 It is the number one Yeoman community generator, with currently 1490 stars on the generator page vs Mean.js' 81 stars (admittedly not a fair comparison given how new MEANJS is). 它是头号Yeoman社区发电机，目前在发电机页面上有1490颗星与Mean.js的81颗星（鉴于新MEANJS是多么公平的比较）。 It is appears to be actively maintained and is in version 2.05 as I write this. 它似乎是积极维护的，在我写这篇文章的时候是版本2.05。 Unlike MEANJS, it doesn't use Swig for templating. 与MEANJS不同，它不使用Swig进行模板化。 It can be scaffolded with passport built in. 它可以搭建护照内置的脚手架。
#6楼
The Starter Trade-offs sheet of my comparison spreadsheet has comprehensive one-on-one comparisons between each generator. 我的比较电子表格的Starter Trade-offs表格在每个发生器之间进行了全面的一对一比较。 So no more need to distortedly cherry-pick great things to say about your favorite. 所以不再需要歪曲地挑选出你最喜欢的东西。
Here is the one between generator-angular-fullstack and MEAN.js. 这是generator-angular-fullstack和MEAN.js之间的那个。 The percentages are values for each benefit based on my personal weightings, where a perfect generator would be 100% 百分比是基于我个人权重的每个福利的值，其中完美的发电机将是100％
generator- angular- fullstack offers 8% that MEANJS.org doesn't generator- angular- fullstack提供8％，MEANJS.org没有
- 1.9% Client-side end-to-end tests 1.9％客户端端到端测试
- 0.6% factory 工厂0.6％
- 0.5% provider 0.5％的提供者
- 0.4% SASS 0.4％SASS
- 0.4% LESS 0.4％少
- 0.4% Compass 0.4％指南针
- 0.4% decorator 装饰0.4％
- 0.4% Endpoint subgenerator 0.4％端点子发电机
- 0.4% Comments 0.4％评论
- 0.3% FontAwesome 0.3％FontAwesome
- 0.3% Run server in debug mode 0.3％在调试模式下运行服务器
- 0.3% Save generator answers to a file 0.3％将生成器答案保存到文件中
- 0.2% constant 0.2％不变
- 0.2% Development build script: ...... replace 3rd party deps with CDN versions 0.2％开发构建脚本：......用CDN版本替换第三方代表
- 0.2% Authentication - Cookie 0.2％身份验证 - Cookie
- 0.2% Authentication - JSON Web Token (JWT) 0.2％身份验证 - JSON Web令牌（JWT）
- 0.2% Server-side logging 0.2％服务器端日志记录
- 0.1% Development build script: run tasks in parallel to speed it up 0.1％开发构建脚本：并行运行任务以加快速度
- 0.1% Development build script: Renames asset files to prevent browser caching 0.1％开发构建脚本：重命名资产文件以防止浏览器缓存
- 0.1% Development build script: run end to end tests 0.1％开发构建脚本：运行端到端测试
- 0.1% Production build script: safe pre-minification 0.1％生产构建脚本：安全预先缩小
- 0.1% Production build script: add CSS vendor prefixes 0.1％生产构建脚本：添加CSS供应商前缀
- 0.1% Heroku deployment automation 0.1％Heroku部署自动化
- 0.1% value 0.1％的价值
- 0.1% Jade 0.1％玉
- 0.1% Coffeescript 0.1％Coffeescript
- 0.1% Serverside authenticated route restriction 0.1％Serverside认证的路由限制
- 0.1% SASS version of Twitter Bootstrap 0.1％SASS版本的Twitter Bootstrap
- 0.1% Production build script: compress images 0.1％生产构建脚本：压缩图像
- 0.1% OpenShift deployment automation 0.1％OpenShift部署自动化
MeanJS.org. MeanJS.org。 offers 9% that generator-angular-fullstack doesn't 提供9％的发电机角度 - fullstack没有
- 3.7% Dedicated/searchable user group: response time mostly under a day 3.7％专用/可搜索用户组：响应时间大多在一天之内
- 0.4% Generate routes 0.4％生成路线
- 0.4% Authentication - Oauth 0.4％认证 - Oauth
- 0.4% config 0.4％配置
- 0.4% i18n, localization 0.4％i18n，本地化
- 0.4% Input application profile 0.4％输入申请资料
- 0.3% FEATURE (aka module, entity, crud-mock) 0.3％FEATURE（又名模块，实体，crud-mock）
- 0.3% Menus system 0.3％菜单系统
- 0.3% Options for making subcomponents 0.3％制作子组件的选项
- 0.3% test - client side 0.3％测试 - 客户端
- 0.3% Javascript performance thing 0.3％Javascript性能的东西
- 0.3% Production build script: make static pages for SEO 0.3％生产构建脚本：为SEO制作静态页面
- 0.2% Quick install? 0.2％快速安装？
- 0.2% Dedicated/searchable user group 0.2％专用/可搜索用户组
- 0.1% Development build script: reload build file upon change 0.1％开发构建脚本：在更改时重新加载构建文件
- 0.1% Development build script: coffee files compiled to JS 0.1％开发构建脚本：编译为JS的咖啡文件
- 0.1% controller - server side 0.1％控制器 - 服务器端
- 0.1% model - server side 0.1％模型 - 服务器端
- 0.1% route - server side 0.1％路由 - 服务器端
- 0.1% test - server side 0.1％测试 - 服务器端
- 0.1% Swig 0.1％Swig
- 0.1% Safe from IP Spoofing IP欺骗0.1％安全
- 0.1% Production build script: uglification 0.1％生产构建脚本：uglification
- 0.0% Approach to views: URLs start with "#!" 0.0％观看方法：网址以“＃！”开头
- 0.0% Approach to frontend services and ajax calls: uses $resource 0.0％前端服务和ajax调用的方法：使用$ resource
Here is the one between MEAN.io and MEAN.js in a more readable format 这是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 (aka 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 (aka 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> 
扫一扫
714
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
