I’m really looking for some community feedback for solving the issue with a large fragment of people not wanting change and would like a Meteor that is more like plugging in leggos and less configuring.
Unfortunately this means that Meteor can’t keep up with the latest and greatest and do both.
One idea I had was to create an official Prototype Edition that would be essentially frozen and would focus more on doing things really fast, even if that means creating a less maintainable app and not having the latest bells and whistles.
Beginners and prototypes both fall into the same category. You want to build an app super fast and with little configuration. Neither want the latest and greatest and both want things to be more stable.
User accounts UI is a great example. Most production apps won’t use this as is but for prototypes and beginners it’s perfect.
The Prototype Edition could be a version tag that packages could target so when you install the package it’s been tested to work against that and would make for an easy target.
If someone started with a prototype app and wanted to remove insecure for example, they can, as well as add React. However, the app is now possibly not compatible with Prototype Edition packages.
Meteor Prototype Edition:
- Slow moving / frozen API
- Blaze templates
- MongoDB as the only database (instead of upcoming ones)
- Packages can be marked ‘approved’ so they just work and continue to work
- Everything is aimed at creation speed (insecure, autopublish, more stuff like this)
- Aimed at assembling leggos that are semi customizable (like accounts-ui)
- Rails style generator to make CRUD apps even faster (with standard layout)
- Focuses on keeping up with the fast moving JS world
- Aims at keeping med/large apps maintainable yet easy to build
- Flexible view layers
- Flexible database layers
- no default insecure or autopublish packages
- Improved subscription (eg, declarative like Falcor/GraphQL)
- Sign me up, I want it!
- No, this is not good
- I don’t care either way