Live data from Hacker News

Meteor hits 1.0

meteor.com

171–180 of 250 posts

Re: Meteor hits 1.0

#171
post #33

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…

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.

I like this description; "a framework for hackathons and prototypes"

Re: Meteor hits 1.0

#174
post #91

Earlier quoted context omitted.

We will be sharing more soon. We've been developing with Meteor since the winter of 2012 and two main scaling issues have crept up: (1) the web tier was a bottleneck prior to 0.7.0's implementation of oplog tailing; and (2) post oplog tailing, mongo actually became our bottleneck with the write locks. We were able to get to about 3300 concurrent users (in our very data-intensive application) against a single beefy mo…

Okay, I'll bite: who is "We"?

"We" is [edSpring](https://www.odesk.com/o/jobs/job/_~0155480bf02dee46f3/), built by [TIES](https://www.linkedin.com/company/948661).

Re: Meteor hits 1.0

#175
post #169
post #90

Earlier quoted context omitted.

So is it a PaaS like Google App Engine? Is it just an MVC like angular or ember?

No, it's a full-stack framework, using Node.js on the server and sending down a client app bundle containing all HTML templates and JS. The client and server then communicate exclusively with JSON through a purpose-invented pubsub WebSockets/SockJS protocol they call DDP. The client has a simulated MongoDB database and thus much of the API is isomorphic, so the client will simulate the server's code while it awaits t…

Thanks for this info.

Does it have to use Node.js on the server can the client side framework work with any server side JSON service?

Re: Meteor hits 1.0

#176
post #83

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

And here's a quick way to try it out in a click interactively in the browser: https://www.terminal.com/tiny/F4bHKa1XiB

Or http://meteorpad.com - the JSFiddle/Plunkr of Meteor.

Re: Meteor hits 1.0

#177

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

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

[deleted]

Re: Meteor hits 1.0

#178

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?

I'm working on Google's Governance, Risk and Compliance management system.[1] Porting it to Meteor would accomplish several goals:

* clean and much simpler code base

* automatically (reactively) updated status reports on compliance across various systems depending on numerous components throughout Google in continuous flux

* ease of onboarding new developers in the team given the simplicity and ease of learning of Meteor

[1]: https://github.com/reciprocity/ggrc-core

Re: Meteor hits 1.0

#180

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…

Meteor doesn't use two-way data binding. You have template instances, which are wrapped domranges based on handlebars templates that call helper functions (one way binding). You then have event handlers for templates that you assign to class selectors, which will be delegated to each template instance that is created. You then manually change the data within event handlers.
Post reply on HN