Meteor hits 1.0 • Hacker News Board

Re: Meteor hits 1.0

#141

Post by notastartup » Wed, Oct 29, 2014, 12:23 AM UTC

nathan-muir wrote: post #132

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 [M…

> * 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?

Re: Meteor hits 1.0

#142

Post by ajhit406 » Wed, Oct 29, 2014, 12:23 AM UTC

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

Re: Meteor hits 1.0

#143

Post by jlu » Wed, Oct 29, 2014, 12:41 AM UTC

liscovich wrote: post #139

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-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…

You are not.

Re: Meteor hits 1.0

#144

Post by lourd » Wed, Oct 29, 2014, 1:10 AM UTC

lclarkmichalek wrote: post #56

sferoze wrote: post #44

Earlier quoted context omitted.

Meteor just hit 1.0 and is not the type of framework you can just start including in your stack. You really have to build a meteor app from the ground up, so it is hard for established tech companies to get into Meteor when they already have spent years coding on another stack. As new startups who use Meteor grow you will see those large-scale projects come about.

So, to put it glibly, the only people who will use Meteor for large-scale projects are those who have no choice?

Quite the opposite. Those who can choose anything choose Meteor.

Re: Meteor hits 1.0

#145

Post by arunoda » Wed, Oct 29, 2014, 1:16 AM UTC

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

Re: Meteor hits 1.0

#146

Post by arunoda » Wed, Oct 29, 2014, 1:22 AM UTC

thathonkey wrote: post #125

imslavko wrote: post #94

Earlier quoted context omitted.

Here is a very fine blog posts series on scaling Meteor horizontally, please consider looking at it: https://meteorhacks.com/pro-meteor/

Interesting, thanks. In that first blog post it mentions that Meteor serves static files. Is that a requirement? edit: posted too soon they talk about it here https://meteorhacks.com/does-meteor-scale.html

And you can use cloudflare or some other CDN very easily. See: https://meteorhacks.com/cloudflare-meets-meteor.html

Re: Meteor hits 1.0

#147

Post by kfinley » Wed, Oct 29, 2014, 1:27 AM UTC

liscovich wrote: post #139

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-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…

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

Re: Meteor hits 1.0

#148

Post by uptownJimmy » Wed, Oct 29, 2014, 1:28 AM UTC

callesgg wrote: post #119

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

Absolutely necessary, I agree.

Re: Meteor hits 1.0

#149

Post by uptownJimmy » Wed, Oct 29, 2014, 1:34 AM UTC

staticelf wrote: post #100

akhatri_aus wrote: post #46

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

Looks great but the site doesn't feel very snappy.

Slow to load. Too slow.

Re: Meteor hits 1.0

#150

Post by liscovich » Wed, Oct 29, 2014, 1:34 AM UTC

jlu wrote: post #143

liscovich wrote: post #139

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-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…

You are not.

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), 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?