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

Why Meteor will kill Ruby on Rails

differential.io

Post reply on HN
Print view View original

21–30 of 336 posts

Re: Why Meteor will kill Ruby on Rails

#23

Post by joshowens »

carsongross wrote: post #18

"When a client asks us to build an app, they are really asking for a fully interactive web app that utilizes javascript to get rich client interfaces." Or maybe they really are just asking you for an app, but you'd rather build a fully interactive web app that utilizes javascript to get rich client interfaces.

No, the client that spawned this blog post was specifically asked for heavy google maps integration. We haven't had one client asking for just a server side app in years.

I've been doing this for 8-9 years, I have a good idea on how to talk with my clients :)

Re: Why Meteor will kill Ruby on Rails

#24

Post by edwinnathaniel »

programminggeek wrote: post #12

It depends on your definition of kill. If you mean for new project starts, it might severely diminish it, but I don't think it will flat out end its popularity any more than Rails killed Java. Also, it depends on what type of project you are talking about. For something at large scale, my guess is meteor won't be any more successful than Rails has been at huge scale (like Twitter). I do agree that using one language…

Definitely not today when the tools, the best practices, the state of the libraries are still below average and the developers have varying skill sets.

Who knows 5-10 years down the line...

Re: Why Meteor will kill Ruby on Rails

#26

Post by edwinnathaniel »

joshowens wrote: post #21
rimantas wrote: post #8

> What if you could spend your time in one language > and one framework? What if you eat everything with a fork?

Try it before you knock it, I would bet money you would enjoy it.

The last time I tried this it wasn't silver bullet and it was not an euphoria.

Re: Why Meteor will kill Ruby on Rails

#27

Post by lambda »

While I was reading this post, the page automatically reloaded to something that said "oops, this page can't be found", and then a few seconds later loaded back to the original. This is while I was simply reading the text, not interacting with the page at all.

Somehow, through the magic of JavaScript and Websockets, they managed break passively reading static content.

Re: Why Meteor will kill Ruby on Rails

#28

Post by joshowens »

vezzy-fnord wrote: post #15

How exactly did the author come to this Meteor and Rails dichotomy? What do they have alike besides being web application frameworks, of which there are endless? This makes about as much sense to me as "Why Flask will kill Zend".

I came from Rails after using it for 8 years, so it is my easiest comparison point.

Re: Why Meteor will kill Ruby on Rails

#29

Post by chestnut-tree »

acqq wrote: post #20

I can't read the site (there's nothing in HTML) but is this a framework that doesn't produce pages viewable without JavaScript? If it is against HTML, my vote is against it.

I'm against this too. Why do we want Javascript engines serving simple text pages instead of HTML? What about accessibility? Look at the source code of the linked article. What would a screenreader user encounter if they visited this page?
Post reply on HN