Time. • No unnecessary DOM manipulations needed. • Smart packages, ui-accounts, backbone, email, d3 • Useful for Protypting • Its all Javascript. Double Edged Sword.
yet, so perhaps not scalable for sites that need super fast loads on the client. 2. Meteor's autopublish is not yet proven to scale for a few thousand users. [Think Quora using Meteor.js] 3. Unstable packages, as of April 2013, the smart packages have to grow for widespread use of Meteor. 4. Security is a concern, as you can edit/drop DBs via the console. The insecure package 'kinda' solves this.
send HTML over the network. Send data and let the client decide how to render it. 2. One Language. Write both the client and the server parts of your interface in JavaScript. 3. Database Everywhere. Use the same transparent API to access your database from the client or the server. 4. Latency Compensation. On the client, use prefetching and model simulation to make it look like you have a zero-latency connection to the database. 5. Full Stack Reactivity. Make realtime the default. All layers, from database to template, should make an event-driven interface available. 6. Embrace the Ecosystem. Meteor is open source and integrates, rather than replaces, existing open source tools and frameworks. 7. Simplicity Equals Productivity. The best way to make something seem simple is to have it actually be simple. Accomplish this through clean, classically beautiful APIs.