Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Meteor hits 1.0

meteor.com

Post reply on HN
Print view View original

81–90 of 250 posts

Re: Meteor hits 1.0

#81

Post by cjbarber »

thathonkey wrote: post #72
frequentflyeru wrote: post #71

Just started using Meteor + Telescope on my site TravelMo.re and love it so far. Really easy to use, kind of a pain in the butt to deploy.

Could you elaborate on why it is a pain to deploy? I've never used Meteor but I thought one of the selling points is ease of deploy, hot code pushes, stuff like that.

[Not the op] Meteor is extremely easy to deploy.

Disclaimer: I think Meteor is fantastic.

Never really had an issue - I can't say the same about rails! Obviously Meteor has the advantage of being younger and so less cruft has built up, but I'd bet on it still being insanely easy to deploy 4 years from now.

The Meteor team is doing an awesome job spending the VC money on making an experience that is fantastic for devs. Major props to Geoff et al.

Re: Meteor hits 1.0

#82

Post by brentjanderson »

dasmithii wrote: post #60

At this point, what percentage of web development can't/shouldn't be done with Meteor? It seems like everything else is obsolete in comparison. The only non-Meteor cases I can think of involve especially large scale.

Even at "especially large scale" there are things that can be done to support unique scale cases, including swapping out database drivers and other components that don't work as well as you might need.

Although this may be corrected in 1.0, single page applications in Javascript like this (whether in Angular or other tools) tend to underperform in SEO (Or not perform at all). Meteor has a sort of hack that handles SEO at the moment, but it's not particularly terrific.

Meteor's database support is presently focused on MongoDB exclusively. Expect relational and other data stores to have improved support in the near future. If you were starting a project that depended on a relational database (Postgres, MySQL, MS SQL, Oracle, etc.), Meteor would probably be a poor choice today. For many use cases, however, Meteor is terrific in my experience.

Re: Meteor hits 1.0

#84

Post by cjbarber »

donutdan4114 wrote: post #30

How does one start a project like this and get paid? What are the revenue sources for the team? It's a great product, and the fact that it's open source is amazing.

Step number one:

Create an awesome framework that people want to use (Meteor started out as a travel guide site, I believe, and other YC batchmates wanted to use their web framework)

Step number two:

Keep building the web framework

Step number three:

Raise money to keep building that framework, with a partner who believes for the long term

Step number four:

Keep being awesome, and become the tool that a ton of devs want to use

Step number five:

Monetize with your own enterprise support and hosting

Re: Meteor hits 1.0

#85

Post by brentjanderson »

cjbarber wrote: post #81
thathonkey wrote: post #72

Earlier quoted context omitted.

Could you elaborate on why it is a pain to deploy? I've never used Meteor but I thought one of the selling points is ease of deploy, hot code pushes, stuff like that.

[Not the op] Meteor is extremely easy to deploy. Disclaimer: I think Meteor is fantastic. Never really had an issue - I can't say the same about rails! Obviously Meteor has the advantage of being younger and so less cruft has built up, but I'd bet on it still being insanely easy to deploy 4 years from now. The Meteor team is doing an awesome job spending the VC money on making an experience that is fantastic for devs…

Deployment depends on where you want to run it. Builds into tarballs that can be deployed pretty directly onto EC2 or other hosting services. It does require a VPS or equivalent system (LAMP hosts won't run Meteor). I understand Heroku can be a little more complicated as well. That said, Meteor's self-hosting option is pretty good for getting started, and Amazon instances run it very well.

Also +1 on the Major Props to the Meteor team. They are a model team.

Re: Meteor hits 1.0

#86

Post by polarix »

cjbarber wrote: post #84
donutdan4114 wrote: post #30

How does one start a project like this and get paid? What are the revenue sources for the team? It's a great product, and the fact that it's open source is amazing.

Step number one: Create an awesome framework that people want to use (Meteor started out as a travel guide site, I believe, and other YC batchmates wanted to use their web framework) Step number two: Keep building the web framework Step number three: Raise money to keep building that framework, with a partner who believes for the long term Step number four: Keep being awesome, and become the tool that a ton of devs w…

"I think you should be more explicit here in step 3"

http://i.imgur.com/uvulagb.jpg

Re: Meteor hits 1.0

#87

Post by bsilvereagle »

theckel wrote: post #65
state wrote: post #33

I'm still a bit unclear on what the target market for Meteor is. Is this just for small to medium sized projects, or is it intended to be used for large-scale projects as well? Since it seems like everyone wants to think of themselves as doing something huge, I'm sure the answer can't be 'no' to the second question — but I don't see any examples of significant projects being built on the platform. Actually, with that…

We've built a huge meteor app that has scaled to 1000s of concurrent users and still growing -- there have been some sticky points along the way, but overall, we're extremely pleased. Meteor is an amazing engineering feat.

Do you have any posts on how you scaled Meteor?

Re: Meteor hits 1.0

#88

Post by swartkrans »

thathonkey wrote: post #76
imslavko wrote: post #49

Earlier quoted context omitted.

[I work at Meteor and contributed to the MongoDB realtime driver] Scaling low-latency data synchronization is a challenge for scalability for sure! We are gradually building better and better drivers with persistence to MongoDB. The scalability can vary greatly depending on your application's data schema, usage patterns and amount of writes. If you watch the mentioned talk carefully, the speaker describes a collabora…

The "running from a single box" at the end seems like it could be the most important part of the equation. Would you agree? Or rather, would that be the recommended place to start optimizing if your app runs into scaling problems?

I don't know how you could load balance meteor easily, but you could put your mongodb instance anywhere and pass in its location to meteor. This doubles your risk for downtime because of hardware failure though, your uptime is no longer as good as a system that depends on the uptime of a single machine.

Re: Meteor hits 1.0

#89

Post by joshowens »

bsilvereagle wrote: post #87
theckel wrote: post #65

Earlier quoted context omitted.

We've built a huge meteor app that has scaled to 1000s of concurrent users and still growing -- there have been some sticky points along the way, but overall, we're extremely pleased. Meteor is an amazing engineering feat.

Do you have any posts on how you scaled Meteor?

I wrote something on scaling meteor: http://joshowens.me/how-to-scale-a-meteor-js-app/.

Re: Meteor hits 1.0

#90

Post by bduerst »

sferoze wrote: post #44
state wrote: post #33

I'm still a bit unclear on what the target market for Meteor is. Is this just for small to medium sized projects, or is it intended to be used for large-scale projects as well? Since it seems like everyone wants to think of themselves as doing something huge, I'm sure the answer can't be 'no' to the second question — but I don't see any examples of significant projects being built on the platform. Actually, with that…

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?
Post reply on HN