search

meteor / meteor-feature-requests

A tracker for Meteor issues that are requests for new functionality, not bugs.
Other
89 stars 3 forks source link

Making it easy to use individual Meteor features. #360

Open trusktr opened 5 years ago

trusktr commented 5 years ago

One of the main reasons Meteor is underrated (IMO) is because people believe that using Meteor is an all-or-nothing type of framework, and they feel they lose control over their stack.

It'd be great to make it super clear how to use only certain parts of Meteor without the parts they don't want.

I think it'd be great to also have client-only mode that can produce a static easily-extractable bundle (if not already?), that has no coupling to a server (or at least make this a prime feature in the documentation) so that people can clearly see how to use Meteor's awesome build system and then take those client-only bundles and deploy them how they wish.

This could make Meteor more attractive, if people see it as a collection of tools that one can easily choose from, versus and all-inclusive vendor-lockin framework.

Meteor had really great technology, but I think many developers do not spend enough time to realize how to enable/disable certain Meteor features, and it definitely isn't clear how to take advantage of the build system on it's own.

I would be happy to help with some articles in this area (once documented or implemented). Please let me know how I can help, and please do describe how to use the build system purely on its own for static builds if that is already possible).

trusktr commented 5 years ago

P.S. I'm coming to Meteor Night. It'd be great to meet some of you!