Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming • Hacker News Board

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#21

Post by faceyspacey » Thu, Mar 07, 2013, 2:09 AM UTC

gfodor wrote: post #18

amadeus wrote: post #17

Earlier quoted context omitted.

I prefer to be interested in things that are ACTUALLY interesting; think Google's Spanner, SpaceX, etc, developed by neckbeards who know what they are doing. Not some silly NodeJS/MongoDB API.

It's generally unkind to come in and trash other peoples' work, especially when it's work that is something designed to help make others' jobs easier and is being open sourced.

Amadeus doesn't know what he's talkin about and hasn't analyzed Meteor. At least add some anecdotes that show you have analyzed the product to give you the right to be so harsh.

Meteor is fantastic and has changed the way we should develop web products forever, and more importantly has opened up a whole new set of expectations for what websites should be capable of. Websites are going to become living breathing creatures as a result. Meteor will lead to a truly collaborative realtime web--one where viewing any website is a group activity, rather than a private one.

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#22

Post by asdfadsfasdf » Thu, Mar 07, 2013, 2:17 AM UTC

do the links (pictures of famous news sites like they they actually mentioned your site) link to something? or are they just random pics?

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#23

Post by ibudiallo » Thu, Mar 07, 2013, 2:20 AM UTC

I guess your blog doesn't allow mobile, so I'm out. What's up with under construction just le the mobile user view it.

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#24

Post by orangethirty » Thu, Mar 07, 2013, 2:20 AM UTC

First time it did not load after waiting 32 seconds. Second time it did load, but after waiting 7 seconds.

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#25

Post by svachalek » Thu, Mar 07, 2013, 2:41 AM UTC

I think Meteor is fantastic in most respects but the REST-unfriendliness of it is a little puzzling in this day and age. It would be really nice to see it play well with others.

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#26

Post by stavrianos » Thu, Mar 07, 2013, 2:42 AM UTC

Volpe wrote: post #14

aroman wrote: post #3

Earlier quoted context omitted.

The last few lines of the article shed some light on OP's opinion of browsing with JavaScript disabled: "you need to support browsers that don't have JavaScript enabled. ... ok, that last one was sufficiently low-probability that I'll stop there before I start telling you not to use Meteor if your customers gave up their computers in favor of the abacus."

I don't quite understand the whole "I cripple my browser" thing. Like, if you are going to disable javascript, why not CSS, and if you disable both of those... by not disable the renderer and just read the html... or demand people write plain text websites. Javascript seems rather arbitrary... But I do wonder about the accessibility ramifications of only supporting javascript. Do all browsers support javascript?

For a sufficiently lax definition of "browser", no.

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#27

Post by stavrianos » Thu, Mar 07, 2013, 2:43 AM UTC

saint-loup wrote: post #4

I'm sorry, but why would you put something like this in your CSS: text-shadow: 0 1px 0 rgba(0,0,0,.5); It makes the text blurred and jarring.

Perhaps an attempt to force/fake font smoothing?

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#28

Post by debergalis » Thu, Mar 07, 2013, 3:01 AM UTC

svachalek wrote: post #25

I think Meteor is fantastic in most respects but the REST-unfriendliness of it is a little puzzling in this day and age. It would be really nice to see it play well with others.

[meteor dev]

Thanks. We're getting close to implementing a principled approach to REST endpoints and server-side routing. https://trello.com/card/page-model-server-side-rendering-res...

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#29

Post by mcot2 » Thu, Mar 07, 2013, 3:13 AM UTC

I would be a lot more interested in meteor if it took more of a library approach and wasn't tied specifically to node.js and mongodb.

I understand they are moving towards this by having a protocol and different adapters for other databases.

Re: Meteor in the Wild: How I Learned to Stop Worrying and Love Reactive Programming

#30

Post by Wilya » Thu, Mar 07, 2013, 3:23 AM UTC

Volpe wrote: post #14

aroman wrote: post #3

Earlier quoted context omitted.

The last few lines of the article shed some light on OP's opinion of browsing with JavaScript disabled: "you need to support browsers that don't have JavaScript enabled. ... ok, that last one was sufficiently low-probability that I'll stop there before I start telling you not to use Meteor if your customers gave up their computers in favor of the abacus."

I don't quite understand the whole "I cripple my browser" thing. Like, if you are going to disable javascript, why not CSS, and if you disable both of those... by not disable the renderer and just read the html... or demand people write plain text websites. Javascript seems rather arbitrary... But I do wonder about the accessibility ramifications of only supporting javascript. Do all browsers support javascript?

> why not CSS

Disabling useless CSS stuff is pretty much what Readability is all about.

Besides, CSS generally doesn't claim much of my CPU to display peripheral stuff. Javascript, on the other hand ...