I used my meteor developer account to get the free discover meteor book (via the limited time 1.0 promotion I guess), but I thought I did something wrong, tried again and ended up with two copies/purchases. It was free, but seems like a bug. Maybe detect if someone already got a book?
Meteor hits 1.0
31–40 of 250 posts
Re: Meteor hits 1.0
#32While I do enjoy the bleeding edge on which we live. I'd love to wait to have the discussion about the new Meteor features until their site and newsletter tells us about the release. Sure the git commit is a landmark, but there's nothing to offer other than 'kudos' with this link as the discussion point.
saym's comment refers to the original post, which pointed to a GitHub commit: https://news.ycombinator.com/item?id=8522106.
We merged the stories (in our ghetto way) and moved the comments over here.
Re: Meteor hits 1.0
#33I'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 in mind, what happened to the gallery of projects built on top of Meteor? Perhaps I'm missing it.
All that being said, congratulations on reaching 1.0. There's clearly a lot of great energy and thought that went in to the project.
edit: The videos on the site weren't obvious to me at first, but after finding them I think this one is a good counterpoint: https://www.youtube.com/watch?v=QzhtQzAX_6k
Re: Meteor hits 1.0
#34How 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.
"The company plans to monetize the product by selling enterprise support and services." - [1]
[1] - http://techcrunch.com/2012/07/25/andreessen-horowitz-keeps-e...
Re: Meteor hits 1.0
#35Trying to figure out how it works. And saw this in one of the paragraphs:
> No longer do you need to provision server resources, or deploy API endpoints in the cloud, or manage a database
So you don't manage a database, but what happens to the data.
Can anyone trace an example, I don't, order or cart update from client code to persisting it on the back-end somehow? Does it use flat files...?
Re: Meteor hits 1.0
#36Awesome, really excited to the 1.0!!!
Re: Meteor hits 1.0
#37If only this was built in Dart... or at least TypeScript.
I'm preferentially a CoffeeScript user, but for the sake of inclusivity, it really shouldn't be anything other than JavaScript.
Re: Meteor hits 1.0
#38I'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…
If you look at the main website there are 6 featured videos of real companies using Meteor in production.
Re: Meteor hits 1.0
#39I'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…
It's definitely a win for hackathons and getting a MVP out there that needs real time features. I can't speak much for large scale projects since I haven't had the fortune of reaching that scale yet with meteor, but I'd imagine it will be ideal for that eventually simply by extrapolating the current growth and improvement trends of the framework.
Re: Meteor hits 1.0
#40Trying to figure out how it works. And saw this in one of the paragraphs: > No longer do you need to provision server resources, or deploy API endpoints in the cloud, or manage a database So you don't manage a database, but what happens to the data. Can anyone trace an example, I don't, order or cart update from client code to persisting it on the back-end somehow? Does it use flat files...?
It uses a database, specifically MongoDB. But as I understand it, Meteor manages this for you itself, and abstracts the orchestration of those things into the Meteor platform itself.
It's just a higher level of abstraction, not a new technology. And certainly not flat files.