I found that with the transition to the new documentation system the “Background” and “Principles of Meteor” sections of the original docs were removed.
I believe that an aesthetical statement, such as the one embraced by Python in its PEP 20 aka “The Zen of Python”, is what makes a technology great, as it sets a consistent tone and mission that aligns all the communities involved.
Please consider bringing it back. Checking Meteor for the first time few years ago, it was enough for me to read these sections to know this is a technology really worth checking.
The web was originally designed to work in the same way that mainframes worked in the 70s. The application server rendered a screen and sent it over the network to a dumb terminal. Whenever the user did anything, that server rerendered a whole new screen. This model served the Web well for over a decade. It gave rise to LAMP, Rails, Django, PHP.
Principles of Meteor
- Data on the Wire. Meteor doesn’t send HTML over the network. The server sends data and lets the client render it.
- Database Everywhere. You can use the same methods to access your database from the client or the server.
- Latency Compensation. On the client, Meteor prefetches data and simulates models to make it look like server method calls return instantly.
- Full Stack Reactivity. In Meteor, realtime is the default. All layers, from database to template, update themselves automatically when necessary.
- Embrace the Ecosystem. Meteor is open source and integrates with existing open source tools and frameworks.
- Simplicity Equals Productivity. The best way to make something seem simple is to have it actually be simple. Meteor’s main functionality has clean, classically beautiful APIs.