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?<p>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.<p>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.<p>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: <a href="https://www.youtube.com/watch?v=QzhtQzAX_6k" rel="nofollow">https://www.youtube.com/watch?v=QzhtQzAX_6k</a>
Congratulations on 1.0 but these kinds of buzzwordy lines<p><pre><code> Accomplish in 10 lines what would otherwise take 1000,
thanks to a reactive programming model that extends all
the way from the database to the user's screen.
</code></pre>
Really bother me.<p>Show me where you eliminated 1000 lines of code and how it was beneficial. Each line of code, to me, is placed with purpose and intent.<p>Are you eliminating thousands of lines of boilerplate? Or are you making best guess assumptions that fit the common need, and we still end up with those 1000 lines for something truly custom?
There's a lot to like about Meteor. Just compare setting up some kind of "dream team" of JavaScript: Rendr + React + Grunt + JSX = OMG WHERE DID MY FRIDAY NIGHT GO.<p>Meter out of the box "just works," but it only works with Mongo for now, and it only works if you are all-in with the platform — on both the client and the server side. Those are two pretty big bets to make.<p>I would say Meteor is ideal for learning, except that it's important to learn what the request-response lifecycle is all about, and I think it can be detrimental when a "magical" framework does so much for you.<p>And one thing I just can't get over -- page loads in Meteor.com feel super fast. Until you realize it actually downloaded the contents (not the unseen images, of course) of the entire website! DPP is doing some interesting things, but some of Meteor is some nice magic tricks that we've seen before. 600kb+ of JS on page load is certainly an interesting concept.<p>Huge amount of work by a talented team. A super nice community. As for the framework itself, give it some time, let it grow, but most importantly, understand objectively its strengths and risks. It has both!
I wonder if the criticism that the Flux team at Facebook has directed at two-way data binding is also applicable to Meteor. Jing Chen is her intro of Flux (<a href="https://www.youtube.com/watch?v=nYkdrAPrdcw&list=PLb0IAmt7-GS188xDYE-u1ShQmFFGbrk0v#t=622" rel="nofollow">https://www.youtube.com/watch?v=nYkdrAPrdcw&list=PLb0IAmt7-G...</a>) says that two-way data binding creates a major challenge for scaling applications because views can trigger changes in data, and data changes can trigger cascading changes in views, which makes it very difficult to predict the behavior of the app as a whole. Wouldn't Meteor face the same challenges?<p>In other words, if you believe that the Flux design pattern (which involves a central dispatcher as the only entity capable of updating the data) is sound, shouldn't you stay away from Meteor's model when building large applications? Or am I missing something?
I've read somewhere that a use-case of Meteor is to let you write your server-side logic in javascript, and then run the server-side logic on the client. Wouldn't that be clearly insecure, to trust the client with running server logic?<p>Also, this was accomplished years ago with Google Web Toolkit, which lets you write both the server & client in Java, and compiles the client-side java to very efficient, optimized javascript. That has the added advantage of letting you use a sane, strongly typed language, with all the productivity tools available for Java, and none of the quirks of javascript. <a href="http://www.gwtproject.org/overview.html" rel="nofollow">http://www.gwtproject.org/overview.html</a>
Here's the official blog post announcement for Meteor 1.0: <a href="https://www.meteor.com/blog/2014/10/28/meteor-1-0" rel="nofollow">https://www.meteor.com/blog/2014/10/28/meteor-1-0</a>
I haven't looked at Meteor in a while, but am really impressed with how the vision of Meteor and the code (and of course the website) have evolved.<p>Meteor looks extremely simple to get up and started with, and I was thoroughly impressed by the implicit modularity of it all ("meteor create" makes like 3 files, I think that's awesome)<p>They really try (and succeed) to rid ourselves of the duplication on server and client. And if the android/ios support is as easy as it looks, this is an insanely useful framework.<p>I'm going to use it in my next project for sure now, just need to see how template/module composition works
While 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.<p>Sure the git commit is a landmark, but there's nothing to offer other than 'kudos' with this link as the discussion point.
When the first release of meteor came out, I was really impressed by the product.
The real time update of the web page with zero code was an amazing feature.
Today why I need of Meter?<p>Server side I have multiple choices that guarantee me heigh scalability, performance, and real time.
Also the mongodb solo option, without sql is very restrictive.<p>Client side, there are great js frameworks like React, Ember and Angular
that are great modular libraries.
This is about books as learning resources.<p>For everyone looking to learn Meteor the first 8 chapters of Discover Meteor are available for free for the next week. It is probably the starting book for everyone :)
<a href="https://book.discovermeteor.com/starter" rel="nofollow">https://book.discovermeteor.com/starter</a><p>Also the Manning book Meteor in Action is 50% off the next week with the code jiafinal50
The book is in heavy development with updates every couple of weeks. However it is still not finished and lacks some advanced chapters still.
<a href="http://manning.com/hochhaus/?a_aid=yauh&a_bid=aeff5509" rel="nofollow">http://manning.com/hochhaus/?a_aid=yauh&a_bid=aeff5509</a><p>Apress also has a book called Beginning Meteor but it has almost no relevant content as of yet and no updates in the last months.
<a href="http://www.apress.com/9781430268369" rel="nofollow">http://www.apress.com/9781430268369</a><p>All Packt titles are hopelessly outdated for version 1.0, so you better stay away from them.
Thank you Meteor team - you have done fantastic work, what an achievement. I've had a blast building my meteor hobby site [1]<p>[1] <a href="http://quantpapers.com" rel="nofollow">http://quantpapers.com</a>
This is really awesome, I just checked out the new website and docs. Everything is so much more clear, I love the new docs. Stuff is laid out really well, people new to Meteor are gonna really like this.
Hey Meteor Folks, <a href="https://www.meteor.com/main" rel="nofollow">https://www.meteor.com/main</a> says Preview 0.9.4. First place I went after I checked the git repo.
Great job, Meteor has really helped me develop my programming skills as a beginner. It allows me to get instant feedback on the code I write. To see a real world prototype keeps me going!
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.
I absolutely love Meteor. I've been evangelizing it a lot this year. I wish someone at Meteor would reply to my emails. <i>wink</i> ;) me@danielfischer.com
Meteor is already easy to setup, but for those of you on Windows or who want a clean sandbox to develop meteor apps, we launched a custom Meteor template on Nitrous today. We also increased the free resources:<p><a href="http://blog.nitrous.io/2014/10/28/meteor-template-on-nitrous-io.html" rel="nofollow">http://blog.nitrous.io/2014/10/28/meteor-template-on-nitrous...</a>
Congratulations to the Meteor Development Group! I've been using Meteor for 16 months now and it's amazing how much it has changed/improved. It is a great tool to learn for any beginner web developer.<p>Also check out a catalog of the best Meteor learning resources at <a href="http://MeteorHelp.com" rel="nofollow">http://MeteorHelp.com</a>
UI & API in one go?<p>I just went through the tutorial on meteor.com, and I'm impressed with the speed of getting results.<p>When I were to build another online app, I'd split that in building the frontend and the API composed from microservices, so that I'd be able to offer access through the UI <i>and</i> the web API. Is Meteor a good choice for this approach?
First of all - absolutely love meteor. Couchbase/CouchDB support would be fantastic! More (NoSQL) database support would be fantastic. I worry that it's so MongoDB specific now and the "scale" technologies are MongoDB specific (Oplog tailing only) that adding other databases in the future will become a lot more difficult.
I am excited to give Meteor a go and take advantage of its isomorphic nature.<p>I am particularly excited by the potential of being able to swap out Mongo for RethinkDB (<a href="https://github.com/tuhinc/rethink-livedata" rel="nofollow">https://github.com/tuhinc/rethink-livedata</a>).
Congrats to the team - maybe it's just me, but it seems like you guys to to 1.0 pretty quickly<p>edit: random aside, I literally just saw the transition from the preview website to the 1.0 website as it was hotswapped in, and I have to say it looks _much_ nicer!
Wow that was fast, I can't believe Meteor is already at 1.0! This is really exciting times, so much progress has been made with Meteor. Ill upgrade my meteor app as soon as the official release is out.
Meteor is awesome, congrats to the Meteor team for their 1.0 release! I've been using Meteor for over a year now, and it is staggering how far it has come. They've addressed and continue to address just about any concerns the community has brought up, from security to speed to tools, etc. And where they haven't, the community has stepped up huge. Seriously, Meteor is amazing, but what makes it even better is the awesome community surrounding it. Congrats again.
seems like their selling point is data binding + client syncing. Considering I can do that with Ractive/React + Firebase, what's the advantage of using Meteor?
Not official but here is the a change log: <a href="https://github.com/meteor/meteor/blob/fb7466078ec5da90321bdca3f08ddf085775e947/History.md#v10" rel="nofollow">https://github.com/meteor/meteor/blob/fb7466078ec5da90321bdc...</a><p>It's a bit light on details. I wouldn't say Meteor is 1.0 yet, but preparing for it. Also Worldwide Meteor day is Nov 6th, I anticipate a more formal announcement then.
The importance of JavaScript as a Platform is not abt billions of browsers running JS, but abt how each one of them is also a JS IDE. If we could click the fork button, and start editing, testing and deploying right away, all within the browser, we'd probably get programmers to contribute to open source web apps in a way never seen before.<p>A sea change in how web software gets built and consumed, in the same way Britannica yielded (had to) to Wikipedia.
Amazing :D Great work, and hats off to the meteor team! I just finished a hackathon this weekend with a meteor app, and absolutely loved the framework.
For an unbiased overview of Meteor, including what it offers and how it differs from typical JavaScript frameworks (like Angular.js and Backbone.js) and ecosystems (like Mean.js and Yeoman), read this article:
<a href="http://javascriptissexy.com/learn-meteor-js-properly/" rel="nofollow">http://javascriptissexy.com/learn-meteor-js-properly/</a>
When I saw a link to an "Atmosphere" page I was curious what did meteor had to do with the Atmosphere project [1], a "real Time Client Server Framework for the JVM, supporting WebSockets and Cross-Browser Fallbacks Support". The answer: nothing.<p>1: <a href="https://github.com/Atmosphere" rel="nofollow">https://github.com/Atmosphere</a>
Trying to figure out how it works. And saw this in one of the paragraphs:<p>> No longer do you need to provision server resources, or deploy API endpoints in the cloud, or manage a database<p>So you don't manage a database, but what happens to the data.<p>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...?
Hi meteor.com team. I've scanned the home page and even looked at some other links on the site. I still don't know what this does. Is it a javascript library? Or template maker? A project packager? I have a lot to do and very little time. Can you make a quick video that describes why I should use Meteor and what it does for me? Thanks!
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?
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.
Congrats to the Meteor team on 1.0! We're building our app <a href="http://servicelocale.com" rel="nofollow">http://servicelocale.com</a> on it for high quality services & crafts in Australia.
i am super excited to see the launch<p>quick feedback:
this scares me off a bit:<p>200 open issues / 150 stale branches / 42 open pull requests<p>might be normal for open source projects of that size though
Congrats to the Meteor team!<p>We've built an enterprise/b2b app on meteor, and even through all of the hard yards, it's been a success & the right choice for us.<p>When I first heard about meteor, back at v0.5 or v0.6 - I watched the video from their home page, and thought it was full of buzzword bullshit. I didn't have a clue what it did.<p>I then ended up reading about how their latency-compensation API system worked [Meteor Methods]; And instantly knew that it was for me.<p>Having an API that simulates itself on the client, while simultaneously performing the same work on the server, is freaking awesome. (And then rolls back automatically if they don't agree).<p><i></i> If you are building a real-time, collaborative tool. Meteor is the framework. <i></i><p>That being said, there are a few questions about integration & scalability.<p>Opportunities to use Meteor:<p>* If you can make something small, eg. an internal tool [Free mobile app with cordova!]<p>* If it matches a certain feature of your app - and you can segment it based on URL (eg, it's a separate app)<p>* You're a sadist, and you're going to port your whole app to meteor...<p>* You're writing an MVP and you're going to scrap it later<p>* You're product has realtime/ collaborative elements that are a SELLING feature [not just for your personal enjoyment].<p>Scalability:<p>* Client are always connected via websocket. Great for realtime data (no polling), crap for a website.<p>* As meteor instances are single threads, you can run multiple instances on the one server. Design you code for this (eg, don't store state in regular JS variables on the server - all has to be in the database). Load balance between them.<p>* Once the "client" has booted up. You can then connect to as many other DDP servers [backed by their own mongo instance, or the same mongo instance] as you like. This gives you the ability to segment your application based on your core feature. EG; if you're a monitoring app, shard your data by client, if you're a document app, shard by project. Have a central listing which tells them which server to connect to.<p>* Perform heavy lifting somewhere else. Plenty of "web workers" out there, or roll your own using Celery & Meteor-Celery package [shameless plug].<p>All in all. Meteor is great at what it does; and what it does, is going to be the next generation of web apps.
So last time I used this was back in August 2013.<p>The main concerns we had was scalability and reliability.<p>How does 1.0 address the previous concerns that was enough to abandon meteor.js altogether?