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

Getting Meteor to 1.0

meteor.com

Post reply on HN
Print view View original

11–20 of 54 posts

Re: Getting Meteor to 1.0

#11

Post by sonnym »

geoffschmidt wrote: post #7
sonnym wrote: post #3

After seeing the first, extremely slick demo of meteor, I was, as I believe a lot of people were, extremely excited to see where the project would go. Then came the funding, and some twelve or sixteen months of development, and I finally decided to dive in. I really wanted to like it. I was predisposed to do so. But from the very beginning, I was confronted with something I consider a deal breaker. While I am wary an…

Meteor is a lot more than an npm package. For example, if you type these four commands.. $ curl https://install.meteor.com | /bin/sh; meteor create myapp; cd myapp; meteor you're up and running with a complete stack including MongoDB, node, the dozen-ish core packages that make up the Meteor pubsub and realtime templating stack, and the 'meteor' build tool (which can do things like compile coffeescript and less, gene…

I want to like meteor.

It sounds like the installation script, aside from handling the MongoDB and node setup, could be treated like a typical node package. Based on the fact that meteor has no package.json, seemingly none of those core packages are installed via npm either.

I may be alone in this, but I guess I would just prefer if my web framework expected me to have the interpreter and database installed, and used the package manager already provided for this environment.

Re: Getting Meteor to 1.0

#12

Post by sgdesign »

sonnym wrote: post #3

After seeing the first, extremely slick demo of meteor, I was, as I believe a lot of people were, extremely excited to see where the project would go. Then came the funding, and some twelve or sixteen months of development, and I finally decided to dive in. I really wanted to like it. I was predisposed to do so. But from the very beginning, I was confronted with something I consider a deal breaker. While I am wary an…

Seems to me like you're throwing the baby out with the bath water. I personally think that's a mistake, but in any case if you don't want to run that command on your own machine, you can always try out Meteor with something like https://www.nitrous.io/

Re: Getting Meteor to 1.0

#14

Post by sonnym »

sgdesign wrote: post #12
sonnym wrote: post #3

After seeing the first, extremely slick demo of meteor, I was, as I believe a lot of people were, extremely excited to see where the project would go. Then came the funding, and some twelve or sixteen months of development, and I finally decided to dive in. I really wanted to like it. I was predisposed to do so. But from the very beginning, I was confronted with something I consider a deal breaker. While I am wary an…

Seems to me like you're throwing the baby out with the bath water. I personally think that's a mistake, but in any case if you don't want to run that command on your own machine, you can always try out Meteor with something like https://www.nitrous.io/

It is not about the running of the command - I read the installation script, and it looks fine.

It is about my desire to work on a node application in what I consider to be a standard way. I want to be able to treat my entire application as a node package, leveraging npm for dependency resolution.

Think of it like a rails application. For local development, you probably use rbenv (or rvm), bundler, and have the version of rails you need listed in your Gemfile. You allow the package manager provided with the language and maybe a layer to keep environments separated (already provided by npm) to take care of dependency resolution and updates.

I want a node framework where I can use the package.json file as one does the Gemfile for ruby applications.

Re: Getting Meteor to 1.0

#15

Post by sgdesign »

sonnym wrote: post #14
sgdesign wrote: post #12

Earlier quoted context omitted.

Seems to me like you're throwing the baby out with the bath water. I personally think that's a mistake, but in any case if you don't want to run that command on your own machine, you can always try out Meteor with something like https://www.nitrous.io/

It is not about the running of the command - I read the installation script, and it looks fine. It is about my desire to work on a node application in what I consider to be a standard way. I want to be able to treat my entire application as a node package, leveraging npm for dependency resolution. Think of it like a rails application. For local development, you probably use rbenv (or rvm), bundler, and have the versi…

Well, Meteor isn't really just a Node framework. Why not evaluate it on its own merits?

Re: Getting Meteor to 1.0

#16

Post by akbar501 »

Congrats to the MDG team on having 1.0 within reach, and thanks for releasing an amazing platform.

Meteor is one of those platforms that you should try. I could give you a menu of features, but the productivity boost from Meteor is one of those things you really should experience. The productivity boost is very real and its quantifiable.

An experienced developer can get a very good feel for Meteor over a single weekend: 1. Buy the book: http://www.discovermeteor.com (the book is $39...I did not purchase the other packages) 2. Spend a weekend doing nothing but coding

Come Monday morning you'll know what Meteor is about.

PS: I am not part of MDG, and I have nothing to do with the book (other than having bought a copy).

Re: Getting Meteor to 1.0

#17

Post by akbar501 »

sonnym wrote: post #3

After seeing the first, extremely slick demo of meteor, I was, as I believe a lot of people were, extremely excited to see where the project would go. Then came the funding, and some twelve or sixteen months of development, and I finally decided to dive in. I really wanted to like it. I was predisposed to do so. But from the very beginning, I was confronted with something I consider a deal breaker. While I am wary an…

Don't get too hung up on the installation. I think their point was to make setup/installation/getting excessively simple.

With regard to why not "npm install -g meteor", I think the short answer is that the Meteor installation setups up/installs a lot more than just one node package.

Re: Getting Meteor to 1.0

#18

Post by puller »

akbar501 wrote: post #16

Congrats to the MDG team on having 1.0 within reach, and thanks for releasing an amazing platform. Meteor is one of those platforms that you should try. I could give you a menu of features, but the productivity boost from Meteor is one of those things you really should experience. The productivity boost is very real and its quantifiable. An experienced developer can get a very good feel for Meteor over a single weeke…

When you say it is quantifiable - can you actually quantify it for us, or is this just hyperbole?

Re: Getting Meteor to 1.0

#19

Post by parasj »

I've been using Meteor since its release and its been great at making apps at maximum velocity.

You mentioned that some people are already scaling Meteor across multiple servers. Looking at it, round robin load balancing won't work given requests to a server seem to be stateful. How is that being done as of now? Do you guys have any guidance on how to do that?

Re: Getting Meteor to 1.0

#20

Post by 1qaz2wsx3edc »

geoffschmidt wrote: post #4
pdfcollect wrote: post #2

Any hope of writing/supporting meteor with python backend? :)

Sure! The Meteor client and the Meteor server speak a protocol called DDP, which runs over websockets or HTTP long polling. Meteor clients can connect to any DDP server and vice versa. So you just need to implement a DDP server for Python. DDP is pretty simple (just a few messages) and the spec for the 'pre1' version of the protocol is in Git: https://github.com/meteor/meteor/blob/devel/packages/livedat... This is pr…

I love the DDP as a concept. It's akin to REST-on-steroids, over a websocket with pubsubhubbub sprinkled on top. I really wish more people knew about it, I hope drivers are adapted quickly (some have been). Interoperability & extensibility will make it a killer web feature.
Post reply on HN