6 ms·

Nice read. I understand the sentiment but I find the "win declaration" a bit too weird. How can one say "Rails won"? It's not like people will stop making web

by kinkdr 10y ago

Nice read. I understand the sentiment but I find the "win declaration" a bit too weird. How can one say "Rails won"? It's not like people will stop making web frameworks. Like any other software it will eventually be made obsolete by something newer and better. Maybe I am just nitpicking.

vonklaus 10y ago
Yeah, I found that weird. However, if I think deeply about it, given the move to micro-services and soa type architectures I can see elixir winning longer term which is really railsy. regardless, rails has a ton of influence and some great usecases, but I would say nodejs is about as vogue as rails was and will dominate for another several years. as a nodejs dev, it is super annoying managing the asynchornicity of node and the horrifying dependencies. I suppose rails had stability issues as well. If you read rails is a ghetto by zed shaw, it is interesting (albeit super biased) look at how and why rails developed. edit: As noted, elixir isn't comparable to rails the framework in that arena is phoenix which is similar (at least in function). Thanks!.
- jghn 10y ago
  Elixir isn't comparable to rails, it's comparable to ruby. Phoenix is the thing comparable to rails Edit: I don't mean comparable as similar per se, but that one set are languages and the other are web frameworks
- deleted 10y ago
  [deleted]
- kinkdr 10y ago
  > rails is a ghetto by zed shaw Hilarious! :D
untog 10y ago
I think the "Rails won" sentiment is that 90% of the time, when you talk about a "Ruby job", it's a "Ruby on Rails" job. Not always, but the vast majority of the time. Now, that doesn't apply to any language other than Ruby. But this post might well be aimed at Rubyists exclusively.
dragonwriter 10y ago
Rails won the past. There's a lot of legacy in it that's impractical to replace, which guarantees a sizable community, which makes it viable for new projects, if not always ideal, for quite some time. It's become what J2EE was when Rails was new. Decades from now, even if it's completely fallen out of favor for new development, there'll be people getting paid handsomely to maintain legacy Rails apps. It's won an important spot in history. But technology moves on. And just as the Java stack dominant when Rails emerged has lost ground to Rails, other non-Java stacks, and even newer Java stacks, is wire likely Rails will lose ground to other Ruby and non-Ruby stacks.
- zeemonkee3 10y ago
  J2EE wasn't even that old when Rails was new - maybe 4 or 5 years? But it offered an optimal path between the Scylla of J2EE architecture astronautism and the Charybdis of PHP spaghetti.

by kinkdr 10y ago

vonklaus 10y ago

Yeah, I found that weird. However, if I think deeply about it, given the move to micro-services and soa type architectures I can see elixir winning longer term which is really railsy. regardless, rails has a ton of influence and some great usecases, but I would say nodejs is about as vogue as rails was and will dominate for another several years. as a nodejs dev, it is super annoying managing the asynchornicity of node and the horrifying dependencies. I suppose rails had stability issues as well. If you read rails is a ghetto by zed shaw, it is interesting (albeit super biased) look at how and why rails developed. edit: As noted, elixir isn't comparable to rails the framework in that arena is phoenix which is similar (at least in function). Thanks!.

jghn 10y ago
Elixir isn't comparable to rails, it's comparable to ruby. Phoenix is the thing comparable to rails Edit: I don't mean comparable as similar per se, but that one set are languages and the other are web frameworks
deleted 10y ago
[deleted]
kinkdr 10y ago
> rails is a ghetto by zed shaw Hilarious! :D

untog 10y ago

I think the "Rails won" sentiment is that 90% of the time, when you talk about a "Ruby job", it's a "Ruby on Rails" job. Not always, but the vast majority of the time. Now, that doesn't apply to any language other than Ruby. But this post might well be aimed at Rubyists exclusively.

dragonwriter 10y ago

Rails won the past. There's a lot of legacy in it that's impractical to replace, which guarantees a sizable community, which makes it viable for new projects, if not always ideal, for quite some time. It's become what J2EE was when Rails was new. Decades from now, even if it's completely fallen out of favor for new development, there'll be people getting paid handsomely to maintain legacy Rails apps. It's won an important spot in history. But technology moves on. And just as the Java stack dominant when Rails emerged has lost ground to Rails, other non-Java stacks, and even newer Java stacks, is wire likely Rails will lose ground to other Ruby and non-Ruby stacks.

zeemonkee3 10y ago
J2EE wasn't even that old when Rails was new - maybe 4 or 5 years? But it offered an optimal path between the Scylla of J2EE architecture astronautism and the Charybdis of PHP spaghetti.