11 ms·

Meteor hits 1.0

573 points by debergalis 12y ago

niix 12y ago
Yay! Congrats to the Meteor team!
andreasklinger 12y ago
i am super excited to see the launch quick feedback: this scares me off a bit: 200 open issues / 150 stale branches / 42 open pull requests might be normal for open source projects of that size though
- johnjwang 12y ago
  On the contrary, I think that is a good sign. It means there is an active community that is opening and contributing to issues. If you check out Rails' repo (https://github.com/rails/rails https://github.com/rails/rails) you'll see the same thing. If you've ever been an open source maintainer, you'll know that you'll inevitably write bugs and so you'll always have open issues. The scary thing would be if no one filed any issues or had any pull requests.
  - andreasklinger 12y ago
    good point cycle times might be better indications
- yesimahuman 12y ago
  This is pretty normal. The community is creating enough issues/questions/possible improvements but the project can't possibly fix or incorporate all of them right away. Many of them are probably even bad, or just not the right approach. This stuff is hard and is something we've been dealing with at Ionic. No great solution yet, and I'm coming to terms with the fact that successful OSS projects have a high volume of issue and pr traffic.
maxharris 12y ago
Congratulations and thanks, Meteor team!
wasd 12y ago
Hey Meteor Folks, https://www.meteor.com/main https://www.meteor.com/main says Preview 0.9.4. First place I went after I checked the git repo.
- imslavko 12y ago
  The release 1.0 is pushed to git but there is still work to do: docs, web-site, announcements, etc. It is not done yet :)
tomcam 12y ago
Kudos, Meteor team! Now, SQL, please...
- swartkrans 12y ago
  You can have SQL already, use ddp methods to query a database on the backend. It's not reactive, but it enables you to use SQL.
  - 1qaz2wsx3edc 12y ago
    The data isn't reactively loaded in realtime, but Meteor itself is still reactive. What I mean to point out is that even if you're depending on say classic JSON APIs, the meteor app within itself can still do reactive-features (templates, local collections, etc). And depending how you implement things, you could still take advantage of push capabilities for your data from a legacy endpoint. But yes, I agree, it's not ideal until a SQL adapter is available.
freefrancisco 12y ago
Congrats Meteor team!
desireco42 12y ago
Congrats Meteor, great times!
dia80 12y ago
Thank you Meteor team - you have done fantastic work, what an achievement. I've had a blast building my meteor hobby site [1] [1] http://quantpapers.com http://quantpapers.com
decidertm 12y ago
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!
taternuts 12y ago
Congrats to the team - maybe it's just me, but it seems like you guys to to 1.0 pretty quickly 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!
sferoze 12y ago
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.
- deleted 12y ago
  [deleted]
zura 12y ago
If only this was built in Dart... or at least TypeScript.
- treehau5 12y ago
  I am grateful that it was built in neither.
- JamesLefrere 12y ago
  I'm preferentially a CoffeeScript user, but for the sake of inclusivity, it really shouldn't be anything other than JavaScript.
saym 12y ago
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. Sure the git commit is a landmark, but there's nothing to offer other than 'kudos' with this link as the discussion point.
- dang 12y ago
  saym's comment refers to the original post, which pointed to a GitHub commit: https://news.ycombinator.com/item?id=8522106 https://news.ycombinator.com/item?id=8522106. We merged the stories (in our ghetto way) and moved the comments over here.
  - saym 12y ago
    Sneaky! Glad to have a better discussion focus point. Thanks for providing context to my comment.
logicalman 12y ago
How did Meteor get to 1.0 when node.js is still at 0.10? I congratulate the Meteor team, but can anyone confirm it is actually stable?
- akbar501 12y ago
  Meteor hit 1.0 b/c their APIs are stable. I'd also guess that the software has hit a level of maturity where the Meteor team is comfortable with a supported release. As for Node, there are some within the Node community who would like to bump it to 1.0 as it is clearly production ready. In Node's case, .1 vs. 1. is a just a numbering scheme issue, not a production ready issue.
Lauricio 12y ago
Congratulations!!
Everhusk 12y ago
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.
1qaz2wsx3edc 12y ago
Not official but here is the a change log: https://github.com/meteor/meteor/blob/fb7466078ec5da90321bdca3f08ddf085775e947/History.md#v10 https://github.com/meteor/meteor/blob/fb7466078ec5da90321bdc... 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.
j_k_s 12y ago
Congratulations, and great pun for the title. :)
sferoze 12y ago
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.
rglover 12y ago
Awesome! Really excited for this.
donutdan4114 12y ago
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.
- sferoze 12y ago
  "The company plans to monetize the product by selling enterprise support and services." - [1] [1] - http://techcrunch.com/2012/07/25/andreessen-horowitz-keeps-eating-the-software-world-with-11-2-million-investment-in-javascript-framework-company-meteor/ http://techcrunch.com/2012/07/25/andreessen-horowitz-keeps-e...
- mmcclellan 12y ago
  The wired article, currently at HN here: https://news.ycombinator.com/item?id=8522381 https://news.ycombinator.com/item?id=8522381 is interesting with regards to your questions.
- cjbarber 12y ago
  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
  - polarix 12y ago
    "I think you should be more explicit here in step 3" http://i.imgur.com/uvulagb.jpg http://i.imgur.com/uvulagb.jpg
swartkrans 12y ago
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?
- sgdesign 12y ago
  We fixed that. Thanks for pointing it out!
state 12y ago
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 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 https://www.youtube.com/watch?v=QzhtQzAX_6k
- Everhusk 12y ago
  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.
  - state 12y ago
    What would concern me is if you ever reach a scale where you need to optimize in ways that Meteor can't support. But, that probably falls into the 'problems you want to have' bucket.
  - swartkrans 12y ago
    At last months devshop in SF a speaker discussed straining the system and reaching the limits of Meteor with just hundreds of simultaneous connections: https://www.youtube.com/watch?v=cJbGNpmE7f0&t=8m30s https://www.youtube.com/watch?v=cJbGNpmE7f0&t=8m30s Hundreds isn't really exactly "webscale", but I'm sure they'll iron it out, or it could have just been the application that was at fault. It's one data point however on how meteor scales.
    - 12y ago
rdtsc 12y ago
Trying 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...?
- aroman 12y ago
  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.
  - rdtsc 12y ago
    MongoDB? I think to be accepted and taken more seriously they'd have to at least have an option for something else.
    - sarciszewski 12y ago
      I say PostgreSQL. Not only can it do everything MongoDB can do (and faster* too), it's time-tested technology. * http://blogs.enterprisedb.com/2014/09/24/postgres-outperforms-mongodb-and-ushers-in-new-developer-reality/ http://blogs.enterprisedb.com/2014/09/24/postgres-outperform...
- TylerE 12y ago
  It's super-webscale MongoDB, of course!
  - rdtsc 12y ago
    Sorry, that's a nope for me then
    - 12y ago
waitingkuo 12y ago
Awesome, really excited to the 1.0!!!
akhatri_aus 12y ago
Congrats to the Meteor team on 1.0! We're building our app http://servicelocale.com http://servicelocale.com on it for high quality services & crafts in Australia.
- staticelf 12y ago
  Looks great but the site doesn't feel very snappy.
  - djm_ 12y ago
    I haven't found a Meteor site that does yet, I would love to see an example of one where I don't have to sit at a loading wheel. Anyone?
    - dandv 12y ago
      http://meteor.com http://meteor.com is very snappy. So are sites using fast-render, see https://meteorhacks.com/fast-render/ https://meteorhacks.com/fast-render/
  - uptownJimmy 12y ago
    Slow to load. Too slow.
- aryehof 12y ago
  This site takes about 15 seconds to load on my iPad in Europe, which is so slow someone is likely to tab away. I haven't looked into fast-render mentioned elsewhere, but initial load time has always been a issue, and it seemingly gets worse as you add more functionality to your 'app'. Personally, I'd only consider betting on Meteor for anything non-trivial once some form of incremental/optional loading of functionality was included.
roshanj 12y ago
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. Also check out a catalog of the best Meteor learning resources at http://MeteorHelp.com http://MeteorHelp.com
coffeemug 12y ago
Congrats to the team! This is a very serious engineering achievement. I'd imagine it wasn't nearly as easy as they made it look.
jeswin 12y ago
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. A sea change in how web software gets built and consumed, in the same way Britannica yielded (had to) to Wikipedia.
hardwaresofton 12y ago
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. 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) 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. I'm going to use it in my next project for sure now, just need to see how template/module composition works
- brentjanderson 12y ago
  Phonegap development is still phonegap development, even with Meteor. That said, I built a prototype chat app and deployed to iOS in about an hour. It really was that easy, and the app runs terrifically well. The "write once, run anywhere" mantra is a little more real with Meteor than with other approaches I've used before.
  - hardwaresofton 12y ago
    Thanks for sharing -- that's awesome to hear, yeah, Phonegap definitely has it's warts, but I like the idea of being able to at least get SOMETHING up so quick (to match the web interface
dasmithii 12y ago
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.
- chm 12y ago
  Because Meteor hides much of what's really going on, it's sometimes hard to understand just how the app is working. At least that was my impression of it when I tried it about 9 months ago. Choosing a stack on your own means more time is spent making things work, but then you know how it works. That's why I went for a MEAN stack instead of Meteor. But I'm going to try Meteor again soon!
  - emgee3 12y ago
    While Meteor does do a lot for you out of the box, it doesn't really prevent you from seeing what's going on. There are some good resources for seeing what Meteor is doing behind the scenes (meteorhacks.com and eventedmind.com) if one does want to dig in.
- brentjanderson 12y ago
  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.
  - mononcqc 12y ago
    If you can swap out the drivers to solve the problem, chances are this is not "especially large scale."
xs 12y ago
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!
- TylerE 12y ago
  Basically, yes to all. In terms of scope it's roughly as encompassing as something like Rails - it's full stack.
  - xs 12y ago
    Ah thanks. But if Rails is my coding platform of choice how does this integrate into it?
    - chm 12y ago
      Meteor uses NodeJS.
    - cjbarber 12y ago
      It doesn't.
    - pepr 12y ago
      It doesn't, this is a separate coding platform. If your coding platform is Rails, you don't integrate Django into it.
- sbking 12y ago
  It is a full stack web framework, where you write in 100% JavaScript on the client and server, sharing much of the code with isomorphic APIs. It is not meant to be used on top of Rails, but rather as a full replacement for the combination of, say, Rails+Ember.
perlmonkey 12y ago
This is about books as learning resources. 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 :) https://book.discovermeteor.com/starter https://book.discovermeteor.com/starter 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. http://manning.com/hochhaus/?a_aid=yauh&a_bid=aeff5509 http://manning.com/hochhaus/?a_aid=yauh&a_bid=aeff5509 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. http://www.apress.com/9781430268369 http://www.apress.com/9781430268369 All Packt titles are hopelessly outdated for version 1.0, so you better stay away from them.
- dturnbull 12y ago
  Also, as a shameless plug, beginning web developers are quite fond of my book about Meteor: http://meteortips.com/book http://meteortips.com/book It'll be a couple of days before a (completely) revised version is released for 1.0 though. (Reviews can be found on Amazon: http://www.amazon.com/dp/B00MA8KVAY http://www.amazon.com/dp/B00MA8KVAY)
char_pointer 12y ago
FYI: this link gets me into a redirect loop (probably because of something NoScript related)
- q3k 12y ago
  Don't expect to see meteor-based sites work with JS disabled. Not a huge fan of this turn of events, either...
frequentflyeru 12y ago
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.
- thathonkey 12y ago
  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.
  - cjbarber 12y ago
    [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.
    - brentjanderson 12y ago
      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.
bkruse 12y ago
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.
- thinkcontext 12y ago
  Check out http://hood.ie/ http://hood.ie/ its CouchDB based and has some similar concepts to Meteor
moondowner 12y ago
Here's the official blog post announcement for Meteor 1.0: https://www.meteor.com/blog/2014/10/28/meteor-1-0 https://www.meteor.com/blog/2014/10/28/meteor-1-0
- ljlolel 12y ago
  And here's a quick way to try it out in a click interactively in the browser: https://www.terminal.com/tiny/F4bHKa1XiB https://www.terminal.com/tiny/F4bHKa1XiB
  - dandv 12y ago
    Or http://meteorpad.com http://meteorpad.com - the JSFiddle/Plunkr of Meteor.
    - pihentagy 12y ago
      Hehe, not yet supports 1.0 :)
- dorian-graph 12y ago
  Changelog too: https://github.com/meteor/meteor/blob/devel/History.md https://github.com/meteor/meteor/blob/devel/History.md
nojvek 12y ago
Congrats Meteor! but I really find it loading a bazillion javascript files a bit of an overkill. Also debugging is a pain in the butt.
- dandv 12y ago
  Client-side, you have Chrome DevTools, the best JS debugger there is. Meteor has extensive debugging support. See https://github.com/meteor/meteor/blob/devel/History.md#v094 https://github.com/meteor/meteor/blob/devel/History.md#v094. Also, the popular IDE WebStorm has just released full support for Meteor, including debugging.
- sbking 12y ago
  In production in bundles and minifies all JS and HTML into one file that is sent to the client. Then all further communication happens with JSON over WebSockets/SockJS. If changes are made to the JS/HTML, the server will send down a new application bundle and hot-reload the app without interrupting the user if you are storing the user's app state in the Session. The CSS is also bundled in production. When further changes are made to the CSS, the new stylesheet is live-injected into the running apps without reloading the browser.
killertypo 12y ago
Congratulations on 1.0 but these kinds of buzzwordy lines 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. Really bother me. 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. 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?
- djmashko2 12y ago
  (Disclaimer: I work at Meteor) That box is referring to the data syncing, event handling, and view rendering code that you don't have to write when you use Meteor, compared to some of the previous generation frameworks. If you put together the right list of cutting-edge components like React, Firebase, Bootstrap, and some build tools, you might get a similar improvement in code simplicity. Our goal at Meteor is to give you the same benefits without making you write code to plumb between several different frameworks.
  - mrcwinn 12y ago
    I'm doing a rebuild of a personal project over the holidays and I spent some time looking into binding together React, Airbnb's Rendr, and JSX through Browserify and Grunt. It's possible, but it's a nightmare. Meteor definitely succeeds and just delivering that. (Not that that is the only requirement you might have.)
    - pluma 12y ago
      I'm using React. My server-side rendering is essentially `React.renderComponentToString(App(data))`. The only difference between how I invoke my app on the server vs on the client is that instead of `React.renderComponent` I use `React.renderComponentToString`. On the client, React just uses the pre-rendered HTML and binds itself to that without re-rendering a single DOM node. All my scripts are in `package.json`. I don't use Grunt or Gulp. If I want to re-bundle my client, I invoke a script that essentially does `browserify -g uglifyify lib/browser.js > dist/main.min.js`. My JSX build script and the bundler script are automatically invoked by a watcher. This[0] is my entire build script and the only reason it's verbose is because I like to be able to execute each task separately if I want to. The only problem with React is that it is only a view library. It only does components. The blessed solution is a Flux-like architecture as implemented by Fluxxor or Reflux, but you can integrate React into nearly anything you already have. I like the immutable/unidirectional approach React and Flux share and ended up writing my own library[1] because there were things I didn't like about the existing Flux implementations, but you don't have to do that. I have to admit that Flux has a steep learning curve. And if you've never dealt with immutability before it can really melt your brain. But I don't see how Meteor is any easier to pick up, especially considering that it comes with its own entirely separate ecosystem (the only non-node library I use in my React app is an XHR-wrapper that replaces `request` on the client). [0]: https://gist.github.com/pluma/61a1639906e188be8423 https://gist.github.com/pluma/61a1639906e188be8423 [1]: https://github.com/foss-haas/flox https://github.com/foss-haas/flox
sarciszewski 12y ago
https://www.meteor.com/install https://www.meteor.com/install curl https://install.meteor.com/ https://install.meteor.com/ | sh This despicable habit rears its ugly head again.
- sooheon 12y ago
  Just curious. What is wrong with this?
  - dandv 12y ago
    Executing arbitrary commands on your machine?
  - anonfunction 12y ago
    http://blog.existentialize.com/dont-pipe-to-your-shell.html http://blog.existentialize.com/dont-pipe-to-your-shell.html
mrcwinn 12y ago
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. 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. 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. 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. 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!
- jakozaur 12y ago
  Yeah, one of the common critique is that "Meteor" does too much and doesn't integrate well with other stuff. For me it's a main advantage, I don't need to use "other" stuff to get the final effect. I wrote few projects and it's the best framework if you start from scratch. Though it's hard to swell if you need to add it later to some existing project.
  - pluma 12y ago
    I absolutely agree, but I don't understand why Meteor is frequently seen as a competitor to React or AngularJS or Ember. It's a competitor to combinations like node/browserify and full-stack solutions like Wakanda. Meteor doesn't integrate with anything, but that was never a design goal. If you switch from Meteor, you can likely discard your entire stack (well, except the database obviously). It's based on node, sure, but that's an implementation detail. Meteor is not a node-based stack. That's why it now has its won package manager instead of npm. It's a competitor to node with its own ecosystem. And that's fine.
dsyko 12y ago
Congratulations to everyone on the Meteor team on 1.0! I feel this is just the beginning of many great things to come!
findjashua 12y ago
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?
- rco8786 12y ago
  You can ask it either way. seems like their selling point is data binding + client syncing. Considering I can do that with Meteor, what's the advantage of using Ractive/React + Firebase?
  - findjashua 12y ago
    For starters: 1. You can reuse your existing API, or choose the stack you're comfortable with (I prefer Python to Javascript and Postgres to Mongo) 2. They are being used in production by high traffic websites (Guardian and Instagram respectively), so they're more battle tested 3. Their press releases aren't loaded with buzzwords and hyperbole
    - dandv 12y ago
      You still need JavaScript on the client, so you have to switch context between Python and JS if you're a single dev, or have different team members work on the client vs. the server. Meteor is JavaScript everywhere. Anyway, Meteor offers much more than data binding and client syncing. See http://www.meteorpedia.com/read/Why_Meteor http://www.meteorpedia.com/read/Why_Meteor
    - sbking 12y ago
      The reasons I prefer Meteor (in no particular order): * Fully automated build chain. No matter what kind of preprocessors I use, all my code is compiled, bundled, and hot reloaded into the application. CSS updates are automatically live injected into running applications without a browser refresh. I don't have to write any build chain code, just application code. * Isomorphic client/server APIs, with code sharing built into the build chain. I'm using the same language with the same APIs in both environments, drastically decreasing redundant code. Clients can simulate server RPCs using the same function as the server while it waits for the server's response. If I want, I can easily make the client's simulation code different from the server's such as when I want to obfuscate something, or simply disable client simulation for certain RPCs. The package system incorporates both server and client assets, allowing drop-in full-stack components, such as... * The Accounts UI component. A drop-in, automated SRP+OAuth authentication system that's easy to customize and restyle, or build from scratch using the simple JS authentication APIs. It takes minutes to make a web application with a fully-featured and secure authentication system with password-based and 3rd party OAuth login methods. And logging in never requires a refresh. * Already glued together. Endpoints don't have to be hooked up; they're hooked up from default. Publish data on the server. Subscribe on the client. Add authorization rules, and I have a fully functional web application with realtime data updates, with virtually no glue code.
ofcapl_ 12y ago
congrats to meteor team!
dfischer 12y ago
I absolutely love Meteor. I've been evangelizing it a lot this year. I wish someone at Meteor would reply to my emails. wink ;) me@danielfischer.com
- dandv 12y ago
  I applied too, they were in a hiring freeze before 1.0 :-)
callesgg 12y ago
Nice i love meteor, i hope that there will be some work on a sql backend. I want defined database strucures ;)
- uptownJimmy 12y ago
  Absolutely necessary, I agree.
adam_h 12y ago
Thank you Meteor team. I really enjoy working on my web app that I made with Meteor.
AndyKelley 12y ago
I see this in example code: if (Meteor.isClient) { I don't get it. Are we shipping server side code to the client?
- arbesfeld 12y ago
  Not unless you want to. Anything in a `server/` or `private/` directory is not sent to the client. This pattern is sometimes used to group similar functions in a single file. Relevant section of the docs: https://docs.meteor.com/#/basic/filestructure https://docs.meteor.com/#/basic/filestructure
- pluma 12y ago
  If you use browserify for your "isomorphic" code (i.e. JS that runs on client and server), you may have situations in which you need to run different code depending on whether the code executes on the client and server (think XMLHttpRequest vs `require('http')`). In node you do that by extracting the code in a separate module and telling browserify to use the browser-specific module via your package.json. In Meteor you can just check whether you're running in the client or server at runtime and execute different code accordingly. That's what `Meteor.isClient` is for.
nathan-muir 12y ago
Congrats to the Meteor team! 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. 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. I then ended up reading about how their latency-compensation API system worked [Meteor Methods]; And instantly knew that it was for me. 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). If you are building a real-time, collaborative tool. Meteor is the framework. That being said, there are a few questions about integration & scalability. Opportunities to use Meteor: * If you can make something small, eg. an internal tool [Free mobile app with cordova!] * If it matches a certain feature of your app - and you can segment it based on URL (eg, it's a separate app) * You're a sadist, and you're going to port your whole app to meteor... * You're writing an MVP and you're going to scrap it later * You're product has realtime/ collaborative elements that are a SELLING feature [not just for your personal enjoyment]. Scalability: * Client are always connected via websocket. Great for realtime data (no polling), crap for a website. * 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. * 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. * Perform heavy lifting somewhere else. Plenty of "web workers" out there, or roll your own using Celery & Meteor-Celery package [shameless plug]. All in all. Meteor is great at what it does; and what it does, is going to be the next generation of web apps.
- notastartup 12y ago
  > * You're product has realtime/ collaborative elements that are a SELLING feature [not just for your personal enjoyment]. What opportunities exist in the enterprise market that specifically benefits from this feature?
richardofyork 12y ago
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: http://javascriptissexy.com/learn-meteor-js-properly/ http://javascriptissexy.com/learn-meteor-js-properly/
lukb 12y ago
UI & API in one go? I just went through the tutorial on meteor.com, and I'm impressed with the speed of getting results. 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 and the web API. Is Meteor a good choice for this approach?
- dandv 12y ago
  You can create REST points from Meteor collection very easily - http://www.meteorpedia.com/read/REST_API http://www.meteorpedia.com/read/REST_API
liscovich 12y ago
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 (https://www.youtube.com/watch?v=nYkdrAPrdcw&list=PLb0IAmt7-GS188xDYE-u1ShQmFFGbrk0v#t=622 https://www.youtube.com/watch?v=nYkdrAPrdcw&list=PLb0IAmt7-G...) 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? 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?
- jlu 12y ago
  You are not.
  - liscovich 12y ago
    This is quite surprising to me. I know that Pete Hunt -- one of the authors of ReactJS -- and one of the main proponents of using it in conjunction with Flux, gave a talk at Meteor Devshop 11 earlier this year (http://youtu.be/Lqcs6hPOcFw?t=48m7s http://youtu.be/Lqcs6hPOcFw?t=48m7s), and didn't say a word about the problems associated with two-way data binding. To me that would seem to be the elephant in the room. Is that because he treats Meteor as a framework for prototyping and smaller scale apps?
- kfinley 12y ago
  I don't believe Meteor has two-way data binding. You have to update the model manually using events[0]. 0: https://docs.meteor.com/#/full/eventmaps https://docs.meteor.com/#/full/eventmaps
  - imslavko 12y ago
    Two way data-bindings are not a Core feature and they are implemented in packages. My favorite one is this: http://viewmodel.meteor.com/ http://viewmodel.meteor.com/
notastartup 12y ago
So last time I used this was back in August 2013. The main concerns we had was scalability and reliability. How does 1.0 address the previous concerns that was enough to abandon meteor.js altogether?
- dandv 12y ago
  See this previous reply: https://news.ycombinator.com/item?id=8522918 https://news.ycombinator.com/item?id=8522918
ajhit406 12y ago
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: http://blog.nitrous.io/2014/10/28/meteor-template-on-nitrous-io.html http://blog.nitrous.io/2014/10/28/meteor-template-on-nitrous...
arunoda 12y ago
congrats guys :) Very excited to be a part of the community.
aliakhtar 12y ago
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? 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. http://www.gwtproject.org/overview.html http://www.gwtproject.org/overview.html
- swartkrans 12y ago
  If you read the docs you will see it's not implemented in an insecure way. The core meteor devs are pretty brilliant people, creator of etherpad, svn core contributer, early asana employee, these people aren't dummies they wouldn't do something that silly. Such a dumb thing would have been called out way before 1.0 wouldn't you think? Maybe give it a moment of thought before you comment.
  - deleted 12y ago
    [deleted]
  - lsiebert 12y ago
    Well to be fair, even smart people can make mistakes and miss things. But Meteor is open source, so if the person you responded to is going to question the security model, they can look at the actual code and see if there is an issue. That's the best way to prevent security issues, looking at the code for bugs, mistakes, and assumptions.
  - d23 12y ago
    > Such a dumb thing would have been called out way before 1.0 wouldn't you think? Maybe give it a moment of thought before you comment. To be fair, I'm pretty sure the previous versions did have this issue -- it was just supposed to be ultimately fixed. I could be recalling incorrectly though.
deleted 12y ago
[deleted]
jakelin 12y ago
Well done, Meteor team. My project based on Meteor is going to finished this Friday.
general_failure 12y ago
What is meteor's revenue model? What am I missing...
- 1qaz2wsx3edc 12y ago
  Currently none, but I think some of the things planned are: support, addons, SLAs, deployment, hosting, etc...
- dandv 12y ago
  Galaxy, an enterprise-grade, multi-tenant hosting environment for Meteor apps - https://www.meteor.com/blog/2012/07/25/meteors-new-112-million-development-budget https://www.meteor.com/blog/2012/07/25/meteors-new-112-milli...
  - KhalPanda 12y ago
    For a second there I was like "Woah! $112M?". Damn friendly-URL's.
deleted 12y ago
[deleted]
resca79 12y ago
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? 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. Client side, there are great js frameworks like React, Ember and Angular that are great modular libraries.
- prottmann 12y ago
  I hoped they change meteor and opened it to other databases. The mongodb only option was the reason for us to stop using meteor. Most of our customer projects use "old school" sql and only a few nosql-databases. Waiting for Version 2 ;-)
  - lachgr 12y ago
    SQL support is on the roadmap [1], along with other great features [2]. By the way, it is also possible to use Meteor mostly for the backend and use a framework like React or Angular for the frontend, although I don't know if there are big advantages with such a setup. I think Meteor is a great concept because of their seven principles [3], which I haven't seen in any other framework. I haven't worked with Meteor yet but will start a project in short term which uses Meteor, so I'm very excited to see how this works out. [1] https://trello.com/c/Gf6YxFp2/42-sql-support https://trello.com/c/Gf6YxFp2/42-sql-support [2] https://trello.com/b/hjBDflxp/meteor-roadmap https://trello.com/b/hjBDflxp/meteor-roadmap [3] https://docs.meteor.com/#/basic/sevenprinciples https://docs.meteor.com/#/basic/sevenprinciples
  - resca79 12y ago
    I'm not really confident about new version the releasing of version 1 was too long. Also I do not see a strong open community that support them like Rails, Django o Node. Of course I wish them to grow in terms of contributors
    - pluma 12y ago
GordyMD 12y ago
I am excited to give Meteor a go and take advantage of its isomorphic nature. I am particularly excited by the potential of being able to swap out Mongo for RethinkDB (https://github.com/tuhinc/rethink-livedata https://github.com/tuhinc/rethink-livedata).
- mrcwinn 12y ago
  That project has been abandoned, it seems, and wouldn't work with 1.0.
ForFreedom 12y ago
Are there any similar applications like meteor?
- tarcon 12y ago
  I think http://derbyjs.com http://derbyjs.com can be seen as a competing framework.
ambhaiji 12y ago
The inevitable will come soon News headline: Google buys meteor
coldcode 12y ago
What is the status of supporting Redis. I'd be more excited if I could use my favorite instead of Mongo.
- sbking 12y ago
  Eventually. It's on the roadmap: https://trello.com/c/sWcxRwxN/31-redis-support https://trello.com/c/sWcxRwxN/31-redis-support One of the core developers seems to be working on it: https://github.com/meteor/redis-livedata https://github.com/meteor/redis-livedata
- imslavko 12y ago
  I and another Core Dev Justin SB worked on the Redis support for a month: https://atmospherejs.com/slava/redis-livedata https://atmospherejs.com/slava/redis-livedata It has seamless support for hashes and strings, miniredis, latency compensation, user input validations - similar features to MongoDB integration. Right now you need to start the Redis server and set up the KV observations manually once for every Redis server you intend to use. This support was experimental and we didn't develop it further from there. We told our community about it on a Meteor Devshop but there wasn't much interest. If there will be more interest, we will continue developing it.
landland 12y ago
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.
emmanueloga_ 12y ago
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. 1: https://github.com/Atmosphere https://github.com/Atmosphere
thewhiteox 12y ago
Grats Meteor!

573 points by debergalis 12y ago

niix 12y ago

Yay! Congrats to the Meteor team!

i am super excited to see the launch quick feedback: this scares me off a bit: 200 open issues / 150 stale branches / 42 open pull requests might be normal for open source projects of that size though

johnjwang 12y ago
On the contrary, I think that is a good sign. It means there is an active community that is opening and contributing to issues. If you check out Rails' repo (https://github.com/rails/rails https://github.com/rails/rails) you'll see the same thing. If you've ever been an open source maintainer, you'll know that you'll inevitably write bugs and so you'll always have open issues. The scary thing would be if no one filed any issues or had any pull requests.
- andreasklinger 12y ago
  good point cycle times might be better indications
yesimahuman 12y ago
This is pretty normal. The community is creating enough issues/questions/possible improvements but the project can't possibly fix or incorporate all of them right away. Many of them are probably even bad, or just not the right approach. This stuff is hard and is something we've been dealing with at Ionic. No great solution yet, and I'm coming to terms with the fact that successful OSS projects have a high volume of issue and pr traffic.

maxharris 12y ago

Congratulations and thanks, Meteor team!

wasd 12y ago

Hey Meteor Folks, https://www.meteor.com/main https://www.meteor.com/main says Preview 0.9.4. First place I went after I checked the git repo.

imslavko 12y ago
The release 1.0 is pushed to git but there is still work to do: docs, web-site, announcements, etc. It is not done yet :)

tomcam 12y ago

Kudos, Meteor team! Now, SQL, please...

swartkrans 12y ago
You can have SQL already, use ddp methods to query a database on the backend. It's not reactive, but it enables you to use SQL.
- 1qaz2wsx3edc 12y ago
  The data isn't reactively loaded in realtime, but Meteor itself is still reactive. What I mean to point out is that even if you're depending on say classic JSON APIs, the meteor app within itself can still do reactive-features (templates, local collections, etc). And depending how you implement things, you could still take advantage of push capabilities for your data from a legacy endpoint. But yes, I agree, it's not ideal until a SQL adapter is available.

freefrancisco 12y ago

Congrats Meteor team!

desireco42 12y ago

Congrats Meteor, great times!

dia80 12y ago

Thank you Meteor team - you have done fantastic work, what an achievement. I've had a blast building my meteor hobby site [1] [1] http://quantpapers.com http://quantpapers.com

decidertm 12y ago

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!

taternuts 12y ago

Congrats to the team - maybe it's just me, but it seems like you guys to to 1.0 pretty quickly 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!

sferoze 12y ago

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.

deleted 12y ago
[deleted]

zura 12y ago

If only this was built in Dart... or at least TypeScript.

treehau5 12y ago
I am grateful that it was built in neither.
JamesLefrere 12y ago
I'm preferentially a CoffeeScript user, but for the sake of inclusivity, it really shouldn't be anything other than JavaScript.

saym 12y ago

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. Sure the git commit is a landmark, but there's nothing to offer other than 'kudos' with this link as the discussion point.

dang 12y ago
saym's comment refers to the original post, which pointed to a GitHub commit: https://news.ycombinator.com/item?id=8522106 https://news.ycombinator.com/item?id=8522106. We merged the stories (in our ghetto way) and moved the comments over here.
- saym 12y ago
  Sneaky! Glad to have a better discussion focus point. Thanks for providing context to my comment.

logicalman 12y ago

How did Meteor get to 1.0 when node.js is still at 0.10? I congratulate the Meteor team, but can anyone confirm it is actually stable?

akbar501 12y ago
Meteor hit 1.0 b/c their APIs are stable. I'd also guess that the software has hit a level of maturity where the Meteor team is comfortable with a supported release. As for Node, there are some within the Node community who would like to bump it to 1.0 as it is clearly production ready. In Node's case, .1 vs. 1. is a just a numbering scheme issue, not a production ready issue.

Lauricio 12y ago

Congratulations!!

Everhusk 12y ago

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.

1qaz2wsx3edc 12y ago

Not official but here is the a change log: https://github.com/meteor/meteor/blob/fb7466078ec5da90321bdca3f08ddf085775e947/History.md#v10 https://github.com/meteor/meteor/blob/fb7466078ec5da90321bdc... 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.

j_k_s 12y ago

Congratulations, and great pun for the title. :)

sferoze 12y ago

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.

rglover 12y ago

Awesome! Really excited for this.

donutdan4114 12y ago

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.

sferoze 12y ago
"The company plans to monetize the product by selling enterprise support and services." - [1] [1] - http://techcrunch.com/2012/07/25/andreessen-horowitz-keeps-eating-the-software-world-with-11-2-million-investment-in-javascript-framework-company-meteor/ http://techcrunch.com/2012/07/25/andreessen-horowitz-keeps-e...
mmcclellan 12y ago
The wired article, currently at HN here: https://news.ycombinator.com/item?id=8522381 https://news.ycombinator.com/item?id=8522381 is interesting with regards to your questions.
cjbarber 12y ago
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
- polarix 12y ago
  "I think you should be more explicit here in step 3" http://i.imgur.com/uvulagb.jpg http://i.imgur.com/uvulagb.jpg

swartkrans 12y ago

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?

sgdesign 12y ago
We fixed that. Thanks for pointing it out!

state 12y ago

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 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 https://www.youtube.com/watch?v=QzhtQzAX_6k

Everhusk 12y ago
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.
- state 12y ago
  What would concern me is if you ever reach a scale where you need to optimize in ways that Meteor can't support. But, that probably falls into the 'problems you want to have' bucket.
- swartkrans 12y ago
  At last months devshop in SF a speaker discussed straining the system and reaching the limits of Meteor with just hundreds of simultaneous connections: https://www.youtube.com/watch?v=cJbGNpmE7f0&t=8m30s https://www.youtube.com/watch?v=cJbGNpmE7f0&t=8m30s Hundreds isn't really exactly "webscale", but I'm sure they'll iron it out, or it could have just been the application that was at fault. It's one data point however on how meteor scales.
  - 12y ago

rdtsc 12y ago

Trying 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...?

aroman 12y ago
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.
- rdtsc 12y ago
  MongoDB? I think to be accepted and taken more seriously they'd have to at least have an option for something else.
  - sarciszewski 12y ago
    I say PostgreSQL. Not only can it do everything MongoDB can do (and faster* too), it's time-tested technology. * http://blogs.enterprisedb.com/2014/09/24/postgres-outperforms-mongodb-and-ushers-in-new-developer-reality/ http://blogs.enterprisedb.com/2014/09/24/postgres-outperform...
TylerE 12y ago
It's super-webscale MongoDB, of course!
- rdtsc 12y ago
  Sorry, that's a nope for me then
  - 12y ago

waitingkuo 12y ago

Awesome, really excited to the 1.0!!!

akhatri_aus 12y ago

Congrats to the Meteor team on 1.0! We're building our app http://servicelocale.com http://servicelocale.com on it for high quality services & crafts in Australia.

staticelf 12y ago
Looks great but the site doesn't feel very snappy.
- djm_ 12y ago
  I haven't found a Meteor site that does yet, I would love to see an example of one where I don't have to sit at a loading wheel. Anyone?
  - dandv 12y ago
    http://meteor.com http://meteor.com is very snappy. So are sites using fast-render, see https://meteorhacks.com/fast-render/ https://meteorhacks.com/fast-render/
- uptownJimmy 12y ago
  Slow to load. Too slow.
aryehof 12y ago
This site takes about 15 seconds to load on my iPad in Europe, which is so slow someone is likely to tab away. I haven't looked into fast-render mentioned elsewhere, but initial load time has always been a issue, and it seemingly gets worse as you add more functionality to your 'app'. Personally, I'd only consider betting on Meteor for anything non-trivial once some form of incremental/optional loading of functionality was included.

roshanj 12y ago

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. Also check out a catalog of the best Meteor learning resources at http://MeteorHelp.com http://MeteorHelp.com

coffeemug 12y ago

Congrats to the team! This is a very serious engineering achievement. I'd imagine it wasn't nearly as easy as they made it look.

jeswin 12y ago

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. A sea change in how web software gets built and consumed, in the same way Britannica yielded (had to) to Wikipedia.

hardwaresofton 12y ago

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. 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) 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. I'm going to use it in my next project for sure now, just need to see how template/module composition works

brentjanderson 12y ago
Phonegap development is still phonegap development, even with Meteor. That said, I built a prototype chat app and deployed to iOS in about an hour. It really was that easy, and the app runs terrifically well. The "write once, run anywhere" mantra is a little more real with Meteor than with other approaches I've used before.
- hardwaresofton 12y ago
  Thanks for sharing -- that's awesome to hear, yeah, Phonegap definitely has it's warts, but I like the idea of being able to at least get SOMETHING up so quick (to match the web interface

dasmithii 12y ago

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.

chm 12y ago
Because Meteor hides much of what's really going on, it's sometimes hard to understand just how the app is working. At least that was my impression of it when I tried it about 9 months ago. Choosing a stack on your own means more time is spent making things work, but then you know how it works. That's why I went for a MEAN stack instead of Meteor. But I'm going to try Meteor again soon!
- emgee3 12y ago
  While Meteor does do a lot for you out of the box, it doesn't really prevent you from seeing what's going on. There are some good resources for seeing what Meteor is doing behind the scenes (meteorhacks.com and eventedmind.com) if one does want to dig in.
brentjanderson 12y ago
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.
- mononcqc 12y ago
  If you can swap out the drivers to solve the problem, chances are this is not "especially large scale."

xs 12y ago

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!

TylerE 12y ago
Basically, yes to all. In terms of scope it's roughly as encompassing as something like Rails - it's full stack.
- xs 12y ago
  Ah thanks. But if Rails is my coding platform of choice how does this integrate into it?
  - chm 12y ago
    Meteor uses NodeJS.
  - cjbarber 12y ago
    It doesn't.
  - pepr 12y ago
    It doesn't, this is a separate coding platform. If your coding platform is Rails, you don't integrate Django into it.
sbking 12y ago
It is a full stack web framework, where you write in 100% JavaScript on the client and server, sharing much of the code with isomorphic APIs. It is not meant to be used on top of Rails, but rather as a full replacement for the combination of, say, Rails+Ember.

perlmonkey 12y ago

This is about books as learning resources. 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 :) https://book.discovermeteor.com/starter https://book.discovermeteor.com/starter 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. http://manning.com/hochhaus/?a_aid=yauh&a_bid=aeff5509 http://manning.com/hochhaus/?a_aid=yauh&a_bid=aeff5509 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. http://www.apress.com/9781430268369 http://www.apress.com/9781430268369 All Packt titles are hopelessly outdated for version 1.0, so you better stay away from them.

dturnbull 12y ago
Also, as a shameless plug, beginning web developers are quite fond of my book about Meteor: http://meteortips.com/book http://meteortips.com/book It'll be a couple of days before a (completely) revised version is released for 1.0 though. (Reviews can be found on Amazon: http://www.amazon.com/dp/B00MA8KVAY http://www.amazon.com/dp/B00MA8KVAY)

char_pointer 12y ago

FYI: this link gets me into a redirect loop (probably because of something NoScript related)

q3k 12y ago
Don't expect to see meteor-based sites work with JS disabled. Not a huge fan of this turn of events, either...

frequentflyeru 12y ago

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.

thathonkey 12y ago
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.
- cjbarber 12y ago
  [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.
  - brentjanderson 12y ago
    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.

bkruse 12y ago

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.

thinkcontext 12y ago
Check out http://hood.ie/ http://hood.ie/ its CouchDB based and has some similar concepts to Meteor

moondowner 12y ago

Here's the official blog post announcement for Meteor 1.0: https://www.meteor.com/blog/2014/10/28/meteor-1-0 https://www.meteor.com/blog/2014/10/28/meteor-1-0

ljlolel 12y ago
And here's a quick way to try it out in a click interactively in the browser: https://www.terminal.com/tiny/F4bHKa1XiB https://www.terminal.com/tiny/F4bHKa1XiB
- dandv 12y ago
  Or http://meteorpad.com http://meteorpad.com - the JSFiddle/Plunkr of Meteor.
  - pihentagy 12y ago
    Hehe, not yet supports 1.0 :)
dorian-graph 12y ago
Changelog too: https://github.com/meteor/meteor/blob/devel/History.md https://github.com/meteor/meteor/blob/devel/History.md

nojvek 12y ago

Congrats Meteor! but I really find it loading a bazillion javascript files a bit of an overkill. Also debugging is a pain in the butt.

dandv 12y ago
Client-side, you have Chrome DevTools, the best JS debugger there is. Meteor has extensive debugging support. See https://github.com/meteor/meteor/blob/devel/History.md#v094 https://github.com/meteor/meteor/blob/devel/History.md#v094. Also, the popular IDE WebStorm has just released full support for Meteor, including debugging.
sbking 12y ago
In production in bundles and minifies all JS and HTML into one file that is sent to the client. Then all further communication happens with JSON over WebSockets/SockJS. If changes are made to the JS/HTML, the server will send down a new application bundle and hot-reload the app without interrupting the user if you are storing the user's app state in the Session. The CSS is also bundled in production. When further changes are made to the CSS, the new stylesheet is live-injected into the running apps without reloading the browser.

killertypo 12y ago

Congratulations on 1.0 but these kinds of buzzwordy lines 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. Really bother me. 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. 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?

djmashko2 12y ago
(Disclaimer: I work at Meteor) That box is referring to the data syncing, event handling, and view rendering code that you don't have to write when you use Meteor, compared to some of the previous generation frameworks. If you put together the right list of cutting-edge components like React, Firebase, Bootstrap, and some build tools, you might get a similar improvement in code simplicity. Our goal at Meteor is to give you the same benefits without making you write code to plumb between several different frameworks.
- mrcwinn 12y ago
  I'm doing a rebuild of a personal project over the holidays and I spent some time looking into binding together React, Airbnb's Rendr, and JSX through Browserify and Grunt. It's possible, but it's a nightmare. Meteor definitely succeeds and just delivering that. (Not that that is the only requirement you might have.)
  - pluma 12y ago
    I'm using React. My server-side rendering is essentially `React.renderComponentToString(App(data))`. The only difference between how I invoke my app on the server vs on the client is that instead of `React.renderComponent` I use `React.renderComponentToString`. On the client, React just uses the pre-rendered HTML and binds itself to that without re-rendering a single DOM node. All my scripts are in `package.json`. I don't use Grunt or Gulp. If I want to re-bundle my client, I invoke a script that essentially does `browserify -g uglifyify lib/browser.js > dist/main.min.js`. My JSX build script and the bundler script are automatically invoked by a watcher. This[0] is my entire build script and the only reason it's verbose is because I like to be able to execute each task separately if I want to. The only problem with React is that it is only a view library. It only does components. The blessed solution is a Flux-like architecture as implemented by Fluxxor or Reflux, but you can integrate React into nearly anything you already have. I like the immutable/unidirectional approach React and Flux share and ended up writing my own library[1] because there were things I didn't like about the existing Flux implementations, but you don't have to do that. I have to admit that Flux has a steep learning curve. And if you've never dealt with immutability before it can really melt your brain. But I don't see how Meteor is any easier to pick up, especially considering that it comes with its own entirely separate ecosystem (the only non-node library I use in my React app is an XHR-wrapper that replaces `request` on the client). [0]: https://gist.github.com/pluma/61a1639906e188be8423 https://gist.github.com/pluma/61a1639906e188be8423 [1]: https://github.com/foss-haas/flox https://github.com/foss-haas/flox

sarciszewski 12y ago

https://www.meteor.com/install https://www.meteor.com/install curl https://install.meteor.com/ https://install.meteor.com/ | sh This despicable habit rears its ugly head again.

sooheon 12y ago
Just curious. What is wrong with this?
- dandv 12y ago
  Executing arbitrary commands on your machine?
- anonfunction 12y ago
  http://blog.existentialize.com/dont-pipe-to-your-shell.html http://blog.existentialize.com/dont-pipe-to-your-shell.html

mrcwinn 12y ago

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. 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. 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. 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. 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!

jakozaur 12y ago
Yeah, one of the common critique is that "Meteor" does too much and doesn't integrate well with other stuff. For me it's a main advantage, I don't need to use "other" stuff to get the final effect. I wrote few projects and it's the best framework if you start from scratch. Though it's hard to swell if you need to add it later to some existing project.
- pluma 12y ago
  I absolutely agree, but I don't understand why Meteor is frequently seen as a competitor to React or AngularJS or Ember. It's a competitor to combinations like node/browserify and full-stack solutions like Wakanda. Meteor doesn't integrate with anything, but that was never a design goal. If you switch from Meteor, you can likely discard your entire stack (well, except the database obviously). It's based on node, sure, but that's an implementation detail. Meteor is not a node-based stack. That's why it now has its won package manager instead of npm. It's a competitor to node with its own ecosystem. And that's fine.

dsyko 12y ago

Congratulations to everyone on the Meteor team on 1.0! I feel this is just the beginning of many great things to come!

findjashua 12y ago

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?

rco8786 12y ago
You can ask it either way. seems like their selling point is data binding + client syncing. Considering I can do that with Meteor, what's the advantage of using Ractive/React + Firebase?
- findjashua 12y ago
  For starters: 1. You can reuse your existing API, or choose the stack you're comfortable with (I prefer Python to Javascript and Postgres to Mongo) 2. They are being used in production by high traffic websites (Guardian and Instagram respectively), so they're more battle tested 3. Their press releases aren't loaded with buzzwords and hyperbole
  - dandv 12y ago
    You still need JavaScript on the client, so you have to switch context between Python and JS if you're a single dev, or have different team members work on the client vs. the server. Meteor is JavaScript everywhere. Anyway, Meteor offers much more than data binding and client syncing. See http://www.meteorpedia.com/read/Why_Meteor http://www.meteorpedia.com/read/Why_Meteor
  - sbking 12y ago
    The reasons I prefer Meteor (in no particular order): * Fully automated build chain. No matter what kind of preprocessors I use, all my code is compiled, bundled, and hot reloaded into the application. CSS updates are automatically live injected into running applications without a browser refresh. I don't have to write any build chain code, just application code. * Isomorphic client/server APIs, with code sharing built into the build chain. I'm using the same language with the same APIs in both environments, drastically decreasing redundant code. Clients can simulate server RPCs using the same function as the server while it waits for the server's response. If I want, I can easily make the client's simulation code different from the server's such as when I want to obfuscate something, or simply disable client simulation for certain RPCs. The package system incorporates both server and client assets, allowing drop-in full-stack components, such as... * The Accounts UI component. A drop-in, automated SRP+OAuth authentication system that's easy to customize and restyle, or build from scratch using the simple JS authentication APIs. It takes minutes to make a web application with a fully-featured and secure authentication system with password-based and 3rd party OAuth login methods. And logging in never requires a refresh. * Already glued together. Endpoints don't have to be hooked up; they're hooked up from default. Publish data on the server. Subscribe on the client. Add authorization rules, and I have a fully functional web application with realtime data updates, with virtually no glue code.

ofcapl_ 12y ago

congrats to meteor team!

dfischer 12y ago

I absolutely love Meteor. I've been evangelizing it a lot this year. I wish someone at Meteor would reply to my emails. wink ;) me@danielfischer.com

dandv 12y ago
I applied too, they were in a hiring freeze before 1.0 :-)

callesgg 12y ago

Nice i love meteor, i hope that there will be some work on a sql backend. I want defined database strucures ;)

uptownJimmy 12y ago
Absolutely necessary, I agree.

adam_h 12y ago

Thank you Meteor team. I really enjoy working on my web app that I made with Meteor.

AndyKelley 12y ago

I see this in example code: if (Meteor.isClient) { I don't get it. Are we shipping server side code to the client?

arbesfeld 12y ago
Not unless you want to. Anything in a `server/` or `private/` directory is not sent to the client. This pattern is sometimes used to group similar functions in a single file. Relevant section of the docs: https://docs.meteor.com/#/basic/filestructure https://docs.meteor.com/#/basic/filestructure
pluma 12y ago
If you use browserify for your "isomorphic" code (i.e. JS that runs on client and server), you may have situations in which you need to run different code depending on whether the code executes on the client and server (think XMLHttpRequest vs `require('http')`). In node you do that by extracting the code in a separate module and telling browserify to use the browser-specific module via your package.json. In Meteor you can just check whether you're running in the client or server at runtime and execute different code accordingly. That's what `Meteor.isClient` is for.

nathan-muir 12y ago

Congrats to the Meteor team! 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. 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. I then ended up reading about how their latency-compensation API system worked [Meteor Methods]; And instantly knew that it was for me. 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). If you are building a real-time, collaborative tool. Meteor is the framework. That being said, there are a few questions about integration & scalability. Opportunities to use Meteor: * If you can make something small, eg. an internal tool [Free mobile app with cordova!] * If it matches a certain feature of your app - and you can segment it based on URL (eg, it's a separate app) * You're a sadist, and you're going to port your whole app to meteor... * You're writing an MVP and you're going to scrap it later * You're product has realtime/ collaborative elements that are a SELLING feature [not just for your personal enjoyment]. Scalability: * Client are always connected via websocket. Great for realtime data (no polling), crap for a website. * 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. * 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. * Perform heavy lifting somewhere else. Plenty of "web workers" out there, or roll your own using Celery & Meteor-Celery package [shameless plug]. All in all. Meteor is great at what it does; and what it does, is going to be the next generation of web apps.

notastartup 12y ago
> * You're product has realtime/ collaborative elements that are a SELLING feature [not just for your personal enjoyment]. What opportunities exist in the enterprise market that specifically benefits from this feature?

richardofyork 12y ago

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: http://javascriptissexy.com/learn-meteor-js-properly/ http://javascriptissexy.com/learn-meteor-js-properly/

lukb 12y ago

UI & API in one go? I just went through the tutorial on meteor.com, and I'm impressed with the speed of getting results. 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 and the web API. Is Meteor a good choice for this approach?

dandv 12y ago
You can create REST points from Meteor collection very easily - http://www.meteorpedia.com/read/REST_API http://www.meteorpedia.com/read/REST_API

liscovich 12y ago

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 (https://www.youtube.com/watch?v=nYkdrAPrdcw&list=PLb0IAmt7-GS188xDYE-u1ShQmFFGbrk0v#t=622 https://www.youtube.com/watch?v=nYkdrAPrdcw&list=PLb0IAmt7-G...) 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? 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?

jlu 12y ago
You are not.
- liscovich 12y ago
  This is quite surprising to me. I know that Pete Hunt -- one of the authors of ReactJS -- and one of the main proponents of using it in conjunction with Flux, gave a talk at Meteor Devshop 11 earlier this year (http://youtu.be/Lqcs6hPOcFw?t=48m7s http://youtu.be/Lqcs6hPOcFw?t=48m7s), and didn't say a word about the problems associated with two-way data binding. To me that would seem to be the elephant in the room. Is that because he treats Meteor as a framework for prototyping and smaller scale apps?
kfinley 12y ago
I don't believe Meteor has two-way data binding. You have to update the model manually using events[0]. 0: https://docs.meteor.com/#/full/eventmaps https://docs.meteor.com/#/full/eventmaps
- imslavko 12y ago
  Two way data-bindings are not a Core feature and they are implemented in packages. My favorite one is this: http://viewmodel.meteor.com/ http://viewmodel.meteor.com/

notastartup 12y ago

So last time I used this was back in August 2013. The main concerns we had was scalability and reliability. How does 1.0 address the previous concerns that was enough to abandon meteor.js altogether?

dandv 12y ago
See this previous reply: https://news.ycombinator.com/item?id=8522918 https://news.ycombinator.com/item?id=8522918

ajhit406 12y ago

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: http://blog.nitrous.io/2014/10/28/meteor-template-on-nitrous-io.html http://blog.nitrous.io/2014/10/28/meteor-template-on-nitrous...

arunoda 12y ago

congrats guys :) Very excited to be a part of the community.

aliakhtar 12y ago

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? 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. http://www.gwtproject.org/overview.html http://www.gwtproject.org/overview.html

swartkrans 12y ago
If you read the docs you will see it's not implemented in an insecure way. The core meteor devs are pretty brilliant people, creator of etherpad, svn core contributer, early asana employee, these people aren't dummies they wouldn't do something that silly. Such a dumb thing would have been called out way before 1.0 wouldn't you think? Maybe give it a moment of thought before you comment.
- deleted 12y ago
  [deleted]
- lsiebert 12y ago
  Well to be fair, even smart people can make mistakes and miss things. But Meteor is open source, so if the person you responded to is going to question the security model, they can look at the actual code and see if there is an issue. That's the best way to prevent security issues, looking at the code for bugs, mistakes, and assumptions.
- d23 12y ago
  > Such a dumb thing would have been called out way before 1.0 wouldn't you think? Maybe give it a moment of thought before you comment. To be fair, I'm pretty sure the previous versions did have this issue -- it was just supposed to be ultimately fixed. I could be recalling incorrectly though.

deleted 12y ago

[deleted]

jakelin 12y ago

Well done, Meteor team. My project based on Meteor is going to finished this Friday.

general_failure 12y ago

What is meteor's revenue model? What am I missing...

1qaz2wsx3edc 12y ago
Currently none, but I think some of the things planned are: support, addons, SLAs, deployment, hosting, etc...
dandv 12y ago
Galaxy, an enterprise-grade, multi-tenant hosting environment for Meteor apps - https://www.meteor.com/blog/2012/07/25/meteors-new-112-million-development-budget https://www.meteor.com/blog/2012/07/25/meteors-new-112-milli...
- KhalPanda 12y ago
  For a second there I was like "Woah! $112M?". Damn friendly-URL's.

deleted 12y ago

[deleted]

resca79 12y ago

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? 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. Client side, there are great js frameworks like React, Ember and Angular that are great modular libraries.

prottmann 12y ago
I hoped they change meteor and opened it to other databases. The mongodb only option was the reason for us to stop using meteor. Most of our customer projects use "old school" sql and only a few nosql-databases. Waiting for Version 2 ;-)
- lachgr 12y ago
  SQL support is on the roadmap [1], along with other great features [2]. By the way, it is also possible to use Meteor mostly for the backend and use a framework like React or Angular for the frontend, although I don't know if there are big advantages with such a setup. I think Meteor is a great concept because of their seven principles [3], which I haven't seen in any other framework. I haven't worked with Meteor yet but will start a project in short term which uses Meteor, so I'm very excited to see how this works out. [1] https://trello.com/c/Gf6YxFp2/42-sql-support https://trello.com/c/Gf6YxFp2/42-sql-support [2] https://trello.com/b/hjBDflxp/meteor-roadmap https://trello.com/b/hjBDflxp/meteor-roadmap [3] https://docs.meteor.com/#/basic/sevenprinciples https://docs.meteor.com/#/basic/sevenprinciples
- resca79 12y ago
  I'm not really confident about new version the releasing of version 1 was too long. Also I do not see a strong open community that support them like Rails, Django o Node. Of course I wish them to grow in terms of contributors
  - pluma 12y ago

GordyMD 12y ago

I am excited to give Meteor a go and take advantage of its isomorphic nature. I am particularly excited by the potential of being able to swap out Mongo for RethinkDB (https://github.com/tuhinc/rethink-livedata https://github.com/tuhinc/rethink-livedata).

mrcwinn 12y ago
That project has been abandoned, it seems, and wouldn't work with 1.0.

ForFreedom 12y ago

Are there any similar applications like meteor?

tarcon 12y ago
I think http://derbyjs.com http://derbyjs.com can be seen as a competing framework.

ambhaiji 12y ago

The inevitable will come soon News headline: Google buys meteor

coldcode 12y ago

What is the status of supporting Redis. I'd be more excited if I could use my favorite instead of Mongo.

sbking 12y ago
Eventually. It's on the roadmap: https://trello.com/c/sWcxRwxN/31-redis-support https://trello.com/c/sWcxRwxN/31-redis-support One of the core developers seems to be working on it: https://github.com/meteor/redis-livedata https://github.com/meteor/redis-livedata
imslavko 12y ago
I and another Core Dev Justin SB worked on the Redis support for a month: https://atmospherejs.com/slava/redis-livedata https://atmospherejs.com/slava/redis-livedata It has seamless support for hashes and strings, miniredis, latency compensation, user input validations - similar features to MongoDB integration. Right now you need to start the Redis server and set up the KV observations manually once for every Redis server you intend to use. This support was experimental and we didn't develop it further from there. We told our community about it on a Meteor Devshop but there wasn't much interest. If there will be more interest, we will continue developing it.

landland 12y ago

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.

emmanueloga_ 12y ago

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. 1: https://github.com/Atmosphere https://github.com/Atmosphere

thewhiteox 12y ago

Grats Meteor!