Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Meteor, a realtime JavaScript framework

meteor.com

Post reply on HN
Print view View original

211–220 of 350 posts

Re: Show HN: Meteor, a realtime JavaScript framework

#211

Post by alexro »

I'm at risk of sounding offensive, but I don't mean it. I just want to point out that to me many recent accomplishments in the realm of web frameworks sound similar to how Microsoft was making noise back in the day with their frameworks.

The MS frameworks were great in themselves, they even cooperated somewhat. But they ultimately lacked in the ability to support long-term development, you know, when people just drop out of the project and you suddenly need to bring someone in ASAP.

Keeping this in mind will allow the new generation of "web guys" do better than us, the "desktop guys".

Re: Show HN: Meteor, a realtime JavaScript framework

#212

Post by binarymax »

geoffschmidt wrote: post #203
AdleyEskridge wrote: post #92

Earlier quoted context omitted.

I somewhat disagree. I want to preface my post by saying I'm smiling ear to ear—I loved the screencast, and I look forward to using this tomorrow on a project I've been thinking about for a while. Here's my concern: If I use Meteor as it is intended, and I also want a my application to have API, I'll have to re-implement all of my logic server-side[1]. This seems like a step back, unless I'm misreading things. I'd lo…

Hey, one of the Meteor authors here. Meteor's architecture makes it super easy to make an API. It's one of the advantages of building your architecture around sending data around rather than HTML. We couldn't go into everything in the video (it was already too long!), but the piece you're missing is Meteor.methods(). This lets you define methods, which are functions that the client can invoke on the server by calling…

Thanks. What does DDP stand for? I found several possible definitions.

Re: Show HN: Meteor, a realtime JavaScript framework

#213

Post by ig1 »

kragen wrote: post #114
ig1 wrote: post #68

Earlier quoted context omitted.

Ditto. The whole point of the LGPL is to allow linking code not to be GPL'd. It pretty much kills the usefulness of this project.

It kills its usefulness for proprietary software , unless you're willing to pay the Meteor guys whatever they ask for a license. But I'd like to point out that there's actually a lot of software out there that isn't proprietary, and Meteor looks like a dramatically better way to write it.

Let's assume you have Meteor on your website:

Want to use google analytics ? - nope you can't.

Want to offer third-party oauth login ? - nope you can't.

Want to use like/tweet/+1 buttons ? - nope you can't.

GPL essentially means your website can't have anything on the client-side which is not GPL compatible. And from reading the Meteor guys website that's not what they intend, their choice of GPL was to ensure and changes to Meteor get contributed back and for that LGPL is a much better licence.

Meteor's own website violates the GPL licence of Meteor as it stands (assuming it contains code from any third-party contributor).

Re: Show HN: Meteor, a realtime JavaScript framework

#214

Post by ig1 »

olalonde wrote: post #196
AdleyEskridge wrote: post #168

Earlier quoted context omitted.

This looks fantastic. I genuinely got giddy watching the screencast! If I were to use Meteor for a partially closed source app earning around $1000 per month, how much could I expect to pay you? From the FAQ: > If the GPL doesn't work for your project, get in touch (contact@meteor.com) and we will write you a commercial license to your specifications.

How is your application distributed? If it's a web app that you run on your own servers, GPL doesn't apply to you (only AGPL would).

That part of the GPL faq refers to server side code, not client side code. Client side code very clearly gets distributed to third parties.

Re: Show HN: Meteor, a realtime JavaScript framework

#216

Post by nacker »

geoffschmidt wrote: post #26
chime wrote: post #8

Just watched the entire demo. First time I heard two people present a product together - definitely makes it a lot more interesting and much less monotonous. After the first 30seconds, I went "pfft, live reload isn't new." But I'm glad I stayed till the very end because it is indeed so much more. It looks very promising, especially if you offer app hosting of some kind (or make it easy on Heroku etc.) I am curious ab…

Thanks for the feedback about the beginning of the demo. We had a really tough time with the site and the video because the people who are interested in frameworks like Meteor come from a lot of different backgrounds. Some people have written half a dozen Backbone applications and have written their own highly scalable node.js cache invalidation servers, while other people have suggested that we take the word "REST"…

Amazing stuff! Would 'add pyjamas' (pyjs.org) be possible in future for those of us who prefer to generate their Javascript from Python?

Re: Show HN: Meteor, a realtime JavaScript framework

#217

Post by danmaz74 »

micheljansen wrote: post #208

My first impression of this: wow. If Meteor is all it appears to be, this is nothing short of revolutionary. My second reaction: what happens when the magic ends? When I was new to Rails, I really loved how easy it was to get started with scaffolding, a nice DSL for specifying relations, nifty form helpers. However, the first time I veered a little off the golden path and wanted to do something a little more complica…

This was my first concern too. I didn't have time to study the documentation, but I hope it is easy to integrate custom solutions both around and on top of the magic whenever it's necessary.

Re: Show HN: Meteor, a realtime JavaScript framework

#218

Post by csomar »

micheljansen wrote: post #208

My first impression of this: wow. If Meteor is all it appears to be, this is nothing short of revolutionary. My second reaction: what happens when the magic ends? When I was new to Rails, I really loved how easy it was to get started with scaffolding, a nice DSL for specifying relations, nifty form helpers. However, the first time I veered a little off the golden path and wanted to do something a little more complica…

I can't upvote this enough. When I saw the screencast, I said "Good,we are looking for that". But I want to know how this work, and how I can hack the core. At some point of building my app, I'll need finer degree of control.

Re: Show HN: Meteor, a realtime JavaScript framework

#219

Post by Afal »

binarymax wrote: post #212
geoffschmidt wrote: post #203

Earlier quoted context omitted.

Hey, one of the Meteor authors here. Meteor's architecture makes it super easy to make an API. It's one of the advantages of building your architecture around sending data around rather than HTML. We couldn't go into everything in the video (it was already too long!), but the piece you're missing is Meteor.methods(). This lets you define methods, which are functions that the client can invoke on the server by calling…

Thanks. What does DDP stand for? I found several possible definitions.

I think it might be "Dynamic Decoupling Protocol"

Re: Show HN: Meteor, a realtime JavaScript framework

#220

Post by entropy_ »

micheljansen wrote: post #208

My first impression of this: wow. If Meteor is all it appears to be, this is nothing short of revolutionary. My second reaction: what happens when the magic ends? When I was new to Rails, I really loved how easy it was to get started with scaffolding, a nice DSL for specifying relations, nifty form helpers. However, the first time I veered a little off the golden path and wanted to do something a little more complica…

Joel Spolsky coined a term for this type of problem. The "leaky abstraction". See here: http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...
Post reply on HN