Hacker News Reader

Comment by cageface | Hacker News Reader

Rails still wins on one very important metric: development speed. Thanks to the rich ecosystem of gems and succinct API I can get something up and running on Rails fast. In the early stages of a project that often counts for more than anything else. Even for a pure JSON API backend Rails still beats anything else I've tried.

View on HN

I don't think so. Development speed in the Rails ecosystem is slowed down by the gems tendency to mess things up with very liberal monkey patching.

Continuing to use Rails today is like staying with PHP yesterday, you continue because that's what you know the best and that you have heavily invested in, not because it's the best out there.

EDIT:

* My best alternative for now: Django

* The Rails community is awesome

* Ruby is awesome

It's just that Rails grew too much as a hairy ball now.

And what's the best out there ?

I think Django is winning in a lot of points compared to rails now: Small API, simple to use and deploy, nice performances, comparable ecosystem,...

I believe Rails can be as modular and stripped down ?

And, FWIW, Ruby is still a lot of fun to develop with. Not sure if developer happiness is a good metric for selecting frameworks though.

It is for the developer.

Development speed? Getting shitty insecure apps out there at web speed?

Your comment lacks of arguments and facts, isn't it? :-)

First of all: you can make shitty insecure apps with whatever language/framework/system out there without worrying about development speed. And you can usually avoid this by knowing what you're doing.

Ruby/Rails lets me to build a prototype/MVP in a weekend (while having a lot of fun too). I can fix/iterate or even switch stack later, if needed.

Reply on news.ycombinator.com