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

31–40 of 336 posts

Re: Why Meteor will kill Ruby on Rails

#31

Post by mindcrime »

Did not read TFA, but my immediate thought on seeing this headline is "No, it won't". Why? Because software never really seems to die. Look at the billions of lines of COBOL or PL/I or FORTRAN still in use around the world. Look at the fact that (a few) people still use OS/2, which is about as dead as software ever really gets.

Rails may well find it's popularity and prestige diminished, but I doubt it'll "die" anytime in any of our lifetimes.

Re: Why Meteor will kill Ruby on Rails

#32

Post by asdasf »

joshowens wrote: post #23
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 :)

And I haven't had a client ask for a javascript app ever. This is why anecdotes aren't very useful.

Re: Why Meteor will kill Ruby on Rails

#35

Post by davexunit »

Let's all hop on the next hip web trend, guys! Rails has become so boring and mature. There are many languages better than Javascript for server-side programs, but monoculture is so much cooler. One size fits all and you'll like it.

Re: Why Meteor will kill Ruby on Rails

#37

Post by asdasf »

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.

I have tried it. I enjoyed it slightly less than I enjoyed maintaining PHP3/mysql3 nightmares.

Re: Why Meteor will kill Ruby on Rails

#38

Post by meowface »

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.

I already hate writing Javascript for the frontend. If I had to write it on the backend, too, I'd probably go insane. Coffeescript makes things a bit better, but only to an extent (plus it has a few odd quirks of its own).

I'd much prefer if some day the reverse was possible: writing Python or Ruby on the backend AND the frontend. I imagine something like that would render Node rather useless. (And no, they did not invent the first or the last usable asynchronous web framework.)

Re: Why Meteor will kill Ruby on Rails

#39

Post by JPKab »

Kynlyn wrote: post #30

The link is now a 404..I hope it wasn't powered by Meteor...

The fact that its hosted at Modulus (the guys behind Demeteorizer, which allows you to host meteor apps on Node.js services) would indicate that its almost certainly a Meteor app to me.

I DO think that Meteor is fucking awesome, due to the sheer speed you can crank out commonly requested features (you can add a Google/Facebook/Github Oauth login widget with one line of code), but it sure as hell doesn't seem to scale well these days.

Post reply on HN