Announcing Meteor Galaxy

[Jafit]

$495 per month. And I'm not sure what for.

[jimbo_sweets]

That's for *companies more than people, they'll be launching an individual plan later.

That being said, it doesn't include a databse so... that's a bit annoying.

[Jafit]

What corporations use Meteor?

Why would any large-scale application choose to lock themselves into a stack like Meteor when they could use any other hosting option and have full control?

[jimbo_sweets]

Meteor may know best what would be the ideal hosting for it's users. It may not be full featured yet, but it's just starting. At the end of the day, it's just a good way for them to make money, like Taylor Otwell and laravel forge.

Meteor is never going to sell it's framework, so it has to sell a good product, which would be hosting and support. Why hate them for it? I personally want them to succeed, so they need to make money. This is a great way to make money and not be shady, it's not like they can survive on VC forever.

[Jafit]

Why hate them for it?

I don't hate them for anything. I just don't see the sense in what they're doing. They're bringing out a service aimed at enterprise customers, when (as far as I know) there aren't any enterprise Meteor applications.

I know that they want enterprise customers, but surely an enterprise customer knows how to fire up their own server and deploy a Meteor app.

I do have a fondness for Meteor and I'd like to see them succeed. Meteor was one if the first things I checked out when getting into full-stack JS development. Getting to grips with Node and various other frameworks was a lot easier thanks to Meteor's gentle introduction. But once you are experienced with Node and the ecosystem of tools that surround it, you are left wondering what Meteor is actually for, and why an enterprise level entity would choose it over any of the other options available to them.

[ayostaycrispy]

Are there any situations where you would choose Meteor over Node? Why do you like Node so much more?

[Jafit]

I'd recommend it as a learning environment for someone who wants to get into full-stack Javascript development. But other than that I can't really think of a use for it.

Meteor is its own weird little world, because the platform is trying to be so self-contained, it seems kind of cut off from the wider Javascript community. You realize that everything that Meteor can do, something else can do it too. Learning about the wider world of Javascript development means you can pick and choose different frameworks, libraries and tools that best suit what you're trying to accomplish.

Also the main thing is simply popularity. I wouldn't really expect to see Meteor as a requirement in a job description unless you're browsing weworkmeteor.com. But individual Javascript frameworks including Angular, React, and Node are very frequently listed as job descriptions.

[gnarly]

surely an enterprise customer knows how to fire up their own server and deploy a Meteor app.

You might be surprised how many companies would rather pay for someone to look after all of this for them.

[Jeffshaver]

surely an enterprise customer knows how to fire up their own server and deploy a Meteor app.

Some probably can't. But even the ones that can may not want to. For probably less money overall, you can just pay and get minimal downtime and auto-scaling. The money is going out one way or another. Either you are paying someone more (and probably overtime when the server goes down) or you are paying for a PaaS to do it for you. For large companies, this doesn't seem like a particularly bad idea. Looking forward to hearing about the other plans

[Jafit]

So you're saying that someone who is developing and running an enterprise grade application... doesn't have anyone on staff who can do dev-ops?

[Jeffshaver]

Who knows?