| • Mean.js is a full-stack JavaScript boilerplate
|
| • It's an opinionated framework using MongoDB, Express, AngularJS, and Node.js
|
| • It was created to help developers from a Java/PHP background transition to Node.js web applications
|
| • Mean.js aims to make it easier to get started with the stack by addressing the interface between the different parts
|
| • The framework is open-source and was released in response to a common trend in Node.js development
|
| • It was born out of a blog post on the MongoDB blog about the "Mean" stack
|
| • The creators, Amos Aviv and Roe Schwaber Cohen, used it in their own projects and recognized its potential
|
| • Mean.js is intended to be a better organized and more efficient way to build Node.js applications
|
| • Developing a REST API for Angular JS using Mean Stack (MongoDB, Express, Angular, Node)
|
| • Importance of proper organization and structure in a web application
|
| • Using popular and well-documented components to simplify development
|
| • Trade-off between simplicity and control over individual components
|
| • Discussion of Mean Stack's modularity and ease of use
|
| • The problem of forks and different flavors of Mean Stack
|
| • Encouragement of variety and choice of tools, rather than a "one true way"
|
| • Juggling multiple databases as an obfuscation layer for different databases
|
| • Using Angular and letting users choose their own web framework (e.g. Amber, Backbone, Knockout)
|
| • Full stack JavaScript as a vision and starting point, not a goal
|
| • Performance gain and benefits of using a full stack JavaScript boilerplate
|
| • Starting a project (JSFS) to contain different flavors of full stack JavaScript
|
| • Implementing own flavor of stack and taking the discussion about JavaScript to a new level
|
| • Collaboration across the ecosystem and package management for front-end and back-end
|
| • Introduction of Rackspace as a sponsor and provider of developer discount and free cloud services
|
| • Editor wars and discussion about the best editor to use with MEAN developers
|
| • Difficulty in juggling multiple tools and editors when maintaining a full stack application
|
| • Learning and adapting to new environment in node land and MEAN framework
|
| • Experimentation and understanding of JavaScript core and asynchronous programming
|
| • The Mean JS project aims to simplify web development with a popular stack that includes MongoDB, Express, AngularJS, and Node.js.
|
| • The project's documentation is designed to point developers to the documentation of the individual components, rather than duplicating information.
|
| • The project's community support is built-in due to the popularity of the stack, and updates are handled by the community.
|
| • The team tries to make updates modular to avoid breaking projects.
|
| • The team is aware of the challenges of maintaining backward compatibility and supporting dependencies.
|
| • The team uses package managers like npm and Bower to manage dependencies.
|
| • The project's complexity makes it hard to predict breaking changes, but the team is doing their best to handle them.
|
| • The team chose popular and well-supported tools like Express and AngularJS for the project.
|
| • The project is designed to be flexible and allow developers to choose their own tools and frameworks.
|
| • Discussing the decision to choose between supported packages and maintaining backwards compatibility
|
| • Introducing JSFS (Javascript Full Stack) as a concept to address larger issues in full stack javascript development
|
| • Mentioning the goal of JSFS to create a level playing field for different flavours of javascript stacks
|
| • Describing the process of managing file systems, deployment, and development cycles in JSFS
|
| • Discussing the concept of modules in JSFS, with examples such as the Mean SEO module
|
| • Explaining the features of JSFS modules, including cross-stack compatibility and improved loading and compressing of scripts
|
| • Mentioning the focus on creating features that make stacks work properly, rather than building something opinionated towards a specific stack
|
| • Discussing the sponsorship of the changelog by Harry's, a shaving supplies company
|
| • Discussion of Harry's shaving kit, its quality, and the company's product design.
|
| • Switching from Jade to Swig as a templating engine in the Mean framework.
|
| • The need for a generator to support different view engines and alleviate community concerns.
|
| • Getting started with Mean: recommended steps for new users, including documentation and examples.
|
| • Importance of community engagement and support for open-source projects.
|
| • Mean JS community support and involvement
|
| • Documentation improvements
|
| • Accepting forks and community contributions
|
| • Limiting scope to JavaScript for now
|
| • Real-world use cases for Mean JS
|
| • Building a "built with" section on the Mean JS website
|
| • Call to action for community involvement
|
| • Ways to provide feedback and suggestions (github issues, twitter, etc.)
|
| • Hosts' personal interests and hobbies (surfing, music)
|
| • Discussion of a new project or initiative with significant movement
|
| • Promotion of the Mean JS organization (meanjs.org) on various platforms (Facebook, GitHub)
|
| • Request to have the @MeanJS Twitter handle (currently abandoned) |
