Live data from Hacker News

Meteor hits 1.0

meteor.com

111–120 of 250 posts

Re: Meteor hits 1.0

#111

seems like their selling point is data binding + client syncing. Considering I can do that with Ractive/React + Firebase, what's the advantage of using Meteor?

You can ask it either way. seems like their selling point is data binding + client syncing. Considering I can do that with Meteor, what's the advantage of using Ractive/React + Firebase?

For starters:

1. You can reuse your existing API, or choose the stack you're comfortable with (I prefer Python to Javascript and Postgres to Mongo)

2. They are being used in production by high traffic websites (Guardian and Instagram respectively), so they're more battle tested

3. Their press releases aren't loaded with buzzwords and hyperbole

Re: Meteor hits 1.0

#112

seems like their selling point is data binding + client syncing. Considering I can do that with Ractive/React + Firebase, what's the advantage of using Meteor?

You can ask it either way. seems like their selling point is data binding + client syncing. Considering I can do that with Meteor, what's the advantage of using Ractive/React + Firebase?

This is a completely fair question to ask, from either direction.

Re: Meteor hits 1.0

#113
post #91

Earlier quoted context omitted.

Do you have any posts on how you scaled Meteor?

We will be sharing more soon. We've been developing with Meteor since the winter of 2012 and two main scaling issues have crept up: (1) the web tier was a bottleneck prior to 0.7.0's implementation of oplog tailing; and (2) post oplog tailing, mongo actually became our bottleneck with the write locks. We were able to get to about 3300 concurrent users (in our very data-intensive application) against a single beefy mo…

Did/have you tried tokumx ?

Re: Meteor hits 1.0

#115
post #92

Earlier quoted context omitted.

No, not at all. It's the other way around, really. Those who don't use Meteor for their projects may not be able to without trashing existing codebases.

What I'm hearing is that Meteor doesn't play well with others and that you should make the decision to go with Meteor carefully since changing your mind later will require a ground-up refactor. This is pretty much my experience as someone who started working on a project where the lead dev had decided to use Meteor and then quit leaving a wonky prototype with "reactive data", poor performance and missing functionalit…

Meteor does make things easier, by making things simpler.

It is much simpler dealing with Meteor's API's then working with documentation from 3 or 4 different frameworks that you need to accomplish the same kind of stuff Meteor does.

Meteor gives you a set of clean coherent APIS to work with to get stuff done.

Re: Meteor hits 1.0

#116
post #90
post #44

Earlier quoted context omitted.

Meteor just hit 1.0 and is not the type of framework you can just start including in your stack. You really have to build a meteor app from the ground up, so it is hard for established tech companies to get into Meteor when they already have spent years coding on another stack. As new startups who use Meteor grow you will see those large-scale projects come about.

So is it a PaaS like Google App Engine? Is it just an MVC like angular or ember?

It's basically something like Java Server Face in javascript,which can be a good and a bad idea...

Re: Meteor hits 1.0

#117
post #77

First of all - absolutely love meteor. Couchbase/CouchDB support would be fantastic! More (NoSQL) database support would be fantastic. I worry that it's so MongoDB specific now and the "scale" technologies are MongoDB specific (Oplog tailing only) that adding other databases in the future will become a lot more difficult.

Check out http://hood.ie/ its CouchDB based and has some similar concepts to Meteor

Re: Meteor hits 1.0

#118

I haven't looked at Meteor in a while, but am really impressed with how the vision of Meteor and the code (and of course the website) have evolved. Meteor looks extremely simple to get up and started with, and I was thoroughly impressed by the implicit modularity of it all ("meteor create" makes like 3 files, I think that's awesome) They really try (and succeed) to rid ourselves of the duplication on server and clien…

Phonegap development is still phonegap development, even with Meteor. That said, I built a prototype chat app and deployed to iOS in about an hour. It really was that easy, and the app runs terrifically well. The "write once, run anywhere" mantra is a little more real with Meteor than with other approaches I've used before.

Thanks for sharing -- that's awesome to hear, yeah, Phonegap definitely has it's warts, but I like the idea of being able to at least get SOMETHING up so quick (to match the web interface
Post reply on HN