> Meteor: the missing infrastructure for building great React apps Extremely bold words as usual. I don't think I've ever seen any JS technology that manufactures as much hype as Meteor. Every single article from Meteor makes it sound like the best thing since sliced Jesus. Are there any reliable numbers on Meteor adoption (and retention)? If you listen to people using Meteor it's already more popular than jQuery but…
Integrating React with Meteor
31–40 of 42 posts
Re: Integrating React with Meteor
#32> Meteor: the missing infrastructure for building great React apps Extremely bold words as usual. I don't think I've ever seen any JS technology that manufactures as much hype as Meteor. Every single article from Meteor makes it sound like the best thing since sliced Jesus. Are there any reliable numbers on Meteor adoption (and retention)? If you listen to people using Meteor it's already more popular than jQuery but…
If you try building a realtime single page app using Meteor and measure the amount of time it took you to complete it, you'll find that the hype is justified.
Re: Integrating React with Meteor
#33> Meteor: the missing infrastructure for building great React apps Extremely bold words as usual. I don't think I've ever seen any JS technology that manufactures as much hype as Meteor. Every single article from Meteor makes it sound like the best thing since sliced Jesus. Are there any reliable numbers on Meteor adoption (and retention)? If you listen to people using Meteor it's already more popular than jQuery but…
Meteor = 86 sites
React = 552 sites
angular = 6,882 Sites
backbone = 9,853 Sites
Re: Integrating React with Meteor
#34> Meteor: the missing infrastructure for building great React apps Extremely bold words as usual. I don't think I've ever seen any JS technology that manufactures as much hype as Meteor. Every single article from Meteor makes it sound like the best thing since sliced Jesus. Are there any reliable numbers on Meteor adoption (and retention)? If you listen to people using Meteor it's already more popular than jQuery but…
libscore ranks js library usage by crawling sites: Meteor = 86 sites http://libscore.com/#Meteor React = 552 sites http://libscore.com/#React angular = 6,882 Sites http://libscore.com/#angular backbone = 9,853 Sites http://libscore.com/#Backbone
Re: Integrating React with Meteor
#35> Meteor: the missing infrastructure for building great React apps Extremely bold words as usual. I don't think I've ever seen any JS technology that manufactures as much hype as Meteor. Every single article from Meteor makes it sound like the best thing since sliced Jesus. Are there any reliable numbers on Meteor adoption (and retention)? If you listen to people using Meteor it's already more popular than jQuery but…
I build stuff with React but never tried with Meteor. But I looked at it, and if you watch the introduction video where he creates something and deploy in like 2 minutes you would go wow as well. It's definitely the most exciting "new" thing I've seen along with React.
Basically, the important question to ask when being dazzled by impressively easy deployment demos is: is this representative of what my experience will be like developing a real-world medium to large scale production app?
So far my impression of Meteor has been that it's only achieving that "simplicity" by completely ignoring problems like initial page load. Delivering a placeholder on initial page load is an anti-pattern, especially for a technology pretending it's the only "truly isomorphic" technology out there.
Re: Integrating React with Meteor
#36Now with the way things have gone with an emphasis on mobile, most sites I'd want to make would be better written as REST-style app servers with pluggable clients.
Re: Integrating React with Meteor
#37I made a toy project once shortly after meteor had just been released. I just kept bricking myself that I'd overlook some security setting that would allow people to run arbitrary queries against my DB. When I also looked into scaling I gave up. Now with the way things have gone with an emphasis on mobile, most sites I'd want to make would be better written as REST-style app servers with pluggable clients.
Secondly, Meteor has several modules that allow you to expose Meteor methods as a REST frontend, so it's a trivial change to get that functionality added in.
Re: Integrating React with Meteor
#38Earlier quoted context omitted.
If you try building a realtime single page app using Meteor and measure the amount of time it took you to complete it, you'll find that the hype is justified.
But at the expense of performance? I've written a number of applications in Meteor and continually struggle to scale them, even to tens of concurrent users.
Re: Integrating React with Meteor
#39What advantages does a meteor+react setup have vs pouchdb+react (synced to couch in backend)? I would think, with meteor you get the backend rendering (for SEO), and with pouch you get a DB API on the fronted that's available offline.
I would say that the paradigms are a bit different between meteor+react and pouchdb+react. I can't say I am expert in either. I have never used pouchdb, but I am well versed in meteor. If I understand correctly pouchdb is an in browser implementation of couchdb and some api's which allow the pouchdb to synchronize with a remote, server side couchdb. It is lightweight, allows for easy set up and integration, and reall…
However, PouchDB have been making some serious progress to support complex offline apps with a lot of data, like full support for secondary map/reduce indexes.
Re: Integrating React with Meteor
#40What advantages does a meteor+react setup have vs pouchdb+react (synced to couch in backend)? I would think, with meteor you get the backend rendering (for SEO), and with pouch you get a DB API on the fronted that's available offline.
Meteor's story for backend rendering is the spiderable package, which works as follows: "When a spider requests an HTML snapshot of a page the Meteor server runs the client half of the application inside phantomjs, a headless browser, and returns the full HTML generated by the client code." That's not really a good solution for all the obvious reasons. (Speed, resource usage, dependencies.) Plus, by that logic every…