Skip to content

Instantly share code, notes, and snippets.

@fritzy

fritzy/Pros and Cons of Meteor.md

Last active January 20, 2016 21:01
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save fritzy/83d76022f2213f0aacc8 to your computer and use it in GitHub Desktop.
Save fritzy/83d76022f2213f0aacc8 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Pros and Cons of Meteor.md

Pros:

  • Shallow Learning Curve
  • Easy to get and app running

Cons:

  • It's not composable.
  • DDP is not used anywhere else, REST is, and you'd have to do that in addition to your app.
  • Only MongoDB support right now, which we consider a marketing driven product with a troubled history rather than a technical driven tool (although Postgres support is in the works)
  • Making React views in Meteor client-side is not the point -- the front-end is tightly coupled to the backed via DDP, having the server direct the client state and causing many edge cases.
  • The biggest use case for Meteor is a niche edge case -- simultaneously editing the same field, and can be solved via standards and small packages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment