Live data from Hacker News

Meteor Raises $20M

techcrunch.com

91–100 of 163 posts

Re: Meteor Raises $20M

#91

I looked into Meteor and it's amazing how everything clicks together. It's just such a drastic change in complexity and feels like a breath of fresh air. The one thing that made me drop it as the choice for a primary stack was the fact that it's tied so heavily into MongoDB. Meteor has a mongodb 'server' replicated client side, that's how they can actually make Meteor so god damn snappy, it's latancy compensation. If…

I've heard the sales pitch for ember and ember-cli and I've seriously begun developing with Ember for the past 2 weeks. So far, I really like the tooling around Ember but am not a huge fan of the actual framework itself. I mean, you have routers, routes, controllers, views, templates, and components - how many concepts do you need to display a ui? Maybe it's just that I can't see the forest through the trees. Perhaps…

You have just one router, and that's only a config file that maps URLs to routes.

They're dropping controllers and views in a month, with Ember 2.0. They're being replaced by components.

So really you will only work with routes and components - which should make things much easier to understand.

Re: Meteor Raises $20M

#92
post #88
post #47

Earlier quoted context omitted.

When Meteor is no longer commercially viable and runs out of venture capital brewed hype-juice everyone will jump to the Next Big Thing and companies that listened to their Meteor evangelist will have to furiously find someone to port from Meteor to ANYTHING so they can continue to build features and support new services. Bless me with your downvotes Meteor zealots! I'll still be here when Meteor is has gone the way…

As mentioned, it's open source and gaining traction. If MDG goes away, I see no reason why meteor could not or would not stand as a viable web framework.

Gaining traction because of the venture capital hype juice I mentioned.

There are lots of open-source and "viable" web frameworks out there.

People want Meteor because it makes a lot of promises regarding productivity, but (as the presence of this article and multiple comments prove) the real interest is in a framework that has money for continued development.

So without the financial backing Meteor is just another open-source web framework. Except if that happens, instead of just replacing it with Angular, Ember, Knockout, etc, you'll also have to replace the entire backend too!

I've already had to do this and while I enjoyed it in some ways and learned a bunch... I really don't think that my company enjoyed paying me to rebuild a platform that they already paid for because the Meteor evangelist they hired before me decided they wanted to be an overpaid consultant instead.

Re: Meteor Raises $20M

#93
post #21
post #20

Earlier quoted context omitted.

Hmm, I didn't know that apps that use websockets needed a different kind of auto-scaling and monitoring. That's interesting. Thanks!

Yep, that's... interesting. For sure real time web application needs better reactivity when scaling up and down. But you can already achieve this kind of reaction time on existing platforms that uses Docker for example (disclaimer: I'm working on the Scalingo PaaS that already supports MeteorJS app, see https://scalingo.com/meteorjs-hosting ).

Meteor's solution will also use containerization: http://info.meteor.com/blog/meteor-and-a-galaxy-of-container...

Re: Meteor Raises $20M

#94
post #59

Not trying to sound like a jerk, but I'm just wondering is it really a good thing to put on your homepage that there are nearly 12K questions posted on StackOverflow about Meteor? Seeing a number like that makes me wonder if maybe the documentation and or APIs are not very well done if it's generated that kind of activity on SO.

Maybe you're right and everyone else on this comment thread are suffering from some cognitive dissonance?

I'd be willing to bet much of those SO questions and replies are a part of keeping up the Meteor hype with most questions being answered by a core group of devs.

The PR machine for Meteor is crazy. It's funny because this 20M will go to generating more hype and PR opportunities, while the actual development will fall to these wide-eyed open-source evangelists who will give up their time for free to make it better.

Then Meteor will be sold to Facebook and all these open source developers will realize that their work was driving up the valuation for a bunch of investors who couldn't care less about their code or the products it powered.

I'm having a relatively cynical day, I can't tell if I woke up this way or if this Meteor news is what set me off.

Re: Meteor Raises $20M

#95

Is anyone here running Meteor in production? I've seen so many intro's and demo's and prototypes but have yet to see any actual products / companies built around it yet.

A couple months ago we launched edgee, a platform for sharing high-quality content in carefully curated collections, called edgees. The app runs on Meteor and we're very happy with it. http://www.edgee.com

Great site, awesome UI. I'm also working on a web app using Meteor. This just gave me some inspiration.

Re: Meteor Raises $20M

#96
post #51

Earlier quoted context omitted.

It's way too late for that anyway. AFAIK DerbyJS was better than Meteor all along but no one has heard of it.

I've heard of it and have used both and disagree. Keep in mind both are open source projects. The community has been immensely successful filling up Meteor's gaps.

The investors are extremely appreciative of that... it'd be a shame if they had to invest in actual filling out their own gaps with the 20M they've raised.

That money is better spent convincing other developers that Meteor has no gaps.

Re: Meteor Raises $20M

#97
post #92
post #88

Earlier quoted context omitted.

As mentioned, it's open source and gaining traction. If MDG goes away, I see no reason why meteor could not or would not stand as a viable web framework.

Gaining traction because of the venture capital hype juice I mentioned. There are lots of open-source and "viable" web frameworks out there. People want Meteor because it makes a lot of promises regarding productivity, but (as the presence of this article and multiple comments prove) the real interest is in a framework that has money for continued development. So without the financial backing Meteor is just another o…

> People want Meteor because it makes a lot of promises regarding productivity, but (as the presence of this article and multiple comments prove) the real interest is in a framework that has money for continued development.

I can't speak for others, but the reason I find meteor interesting is because it's one of the only frameworks to address isomorphic javascript, and because it has some really interesting realtime features out of the box. The fact that it's backed by a team that has some venture funding (and therefore some runway to continue improving it) is a definite plus.

> So without the financial backing Meteor is just another open-source web framework.

I don't understand this point. Even _with_ the funding meteor is just another open source framework. Isn't it great that we have a number of open source framework options to suit different needs?

> I really don't think that my company enjoyed paying me to rebuild a platform that they already paid for because the Meteor evangelist they hired before me decided they wanted to be an overpaid consultant instead.

You haven't really explained _why_ you needed to rebuild it. Perhaps meteor didn't suit the use case for this project or perhaps you felt more comfortable/productive in another framework. You haven't really made a case against meteor or a convincing argument about why adopters would need to switch to another framework if MDG failed as a commercial business.

Re: Meteor Raises $20M

#98

Earlier quoted context omitted.

I've heard the sales pitch for ember and ember-cli and I've seriously begun developing with Ember for the past 2 weeks. So far, I really like the tooling around Ember but am not a huge fan of the actual framework itself. I mean, you have routers, routes, controllers, views, templates, and components - how many concepts do you need to display a ui? Maybe it's just that I can't see the forest through the trees. Perhaps…

You have just one router, and that's only a config file that maps URLs to routes. They're dropping controllers and views in a month, with Ember 2.0. They're being replaced by components. So really you will only work with routes and components - which should make things much easier to understand.

I know that there are talking about "routable components" with one-way data flow (ala react/flux), which hopefully comes soon. Are templates still being kept?

It seems like Ember is going to become a bit more like React (which I'm very fine with).

Re: Meteor Raises $20M

#99

Has anyone seen DDP used outside of Meteor? https://github.com/meteor/meteor/blob/devel/packages/ddp/DDP...

(I work at Meteor).

There have been some discussions with Asana (asana.com) teams who are building their new data store with a DDP API published for their clients.

Re: Meteor Raises $20M

#100

Earlier quoted context omitted.

> For intance, when is it ever OK to let your client write directly in the database, even for their own data? If you're going to pass their calls through a deny and allow call, why not just expose RPCs to the client that will handle any writing? If you have a client-side mirror of your server-side database whose changes are monitored by the templating engine, you can execute what Meteor calls "latency compensation",…

Sure you remove the autopublish package, but then your app stops working. You need to explicitely publish what you want published, you need to explicitely check and validate every input from the client... and that's fine, but then what exactly have you gained from using meteor over, say, socket.io or autobahn? Fast prototyping, yes, you've definitely gained that, but have you gained anything else? I'm genuinely askin…

> I also don't know what you mean by "you express most of these in code". The problem isn't writing a piece of code that expresses that constraint... the problem is doing so without introducing a race condition!

I agree, and this also exposes a weakness of javascript as a backend language. If you use Java/Scala, you have multithreading support and can sync the threads + concurrently verify that an item isn't being purchased more than X times. Which makes this problem solvable even with a NoSQL database. Javascript is single threaded though, which makes this problem a lot harder and I don't know how you'd solve it without an RDBMS with transactional support.

Post reply on HN