Live data from Hacker News

Why I believe Rails is still relevant in 2019

devbrett.com

71–80 of 264 posts

Re: Why I believe Rails is still relevant in 2019

#71
post #29

Earlier quoted context omitted.

> Popularity of a framework or paradigm seems largely driven by marketing and memes. I think a whole lot of developers choose technologies because they are popular at the moment for two reasons: they lack the technical knowledge and experience or maybe just confidence and/or they avoid some responsibility this way (since everyone is doing it). Of course this is most acute in web development because it attracts younge…

Not going to defend choosing what’s popular just because it’s popular but the main argument for using something popular IMO is that most of the sorts of things you want to do is likely to have been done by someone else already and some of those other people will have written about their solution or made libraries etc that you can reuse. Whereas if not many people are using something then the amount of information you…

"popular tech is safe because someone will have done what you want to do" is phrased negatively in this excellent opinion piece: with a new technology/tool, you don't know what can go wrong. With boring technology, there's enough community experience around it. https://mcfunley.com/choose-boring-technology

It also seems like 'boring = popular & old', 'hype = popular & new'.

Re: Why I believe Rails is still relevant in 2019

#73
post #70

I have this joke that I noticed ruby/rails developers seems to use a lot of their extra time (which they get with the high productivity you seem to get with rail) talking about how great ruby and rails are and how efficient they are with it ^^

Take a look at how many non-rails developers spend their time proving that Ruby and Rails are dead.

Re: Why I believe Rails is still relevant in 2019

#74
post #29

Earlier quoted context omitted.

> Popularity of a framework or paradigm seems largely driven by marketing and memes. I think a whole lot of developers choose technologies because they are popular at the moment for two reasons: they lack the technical knowledge and experience or maybe just confidence and/or they avoid some responsibility this way (since everyone is doing it). Of course this is most acute in web development because it attracts younge…

Not going to defend choosing what’s popular just because it’s popular but the main argument for using something popular IMO is that most of the sorts of things you want to do is likely to have been done by someone else already and some of those other people will have written about their solution or made libraries etc that you can reuse. Whereas if not many people are using something then the amount of information you…

> the main argument for using something popular IMO is that most of the sorts of things you want to do is likely to have been done by someone else already and some of those other people will have written about their solution or made libraries etc that you can reuse.

Yes but this holds true for something older that was popular at some other time (like Rails) and is no longer as widely promoted. Those are way safer choices.

Re: Why I believe Rails is still relevant in 2019

#77
Why are people saying stupid things like this? I'm doing rails 24/7 for the past 5 years in MANY different projects and I can say its the BEST and very relevant in 2019. I have to deal with other platforms written in different languages/frameworks like php/laravel and I can only pity developers that have to do that by choice.

Re: Why I believe Rails is still relevant in 2019

#78
I think for what it is - for its paradigm if you will - ruby on rails is an extremely well-designed platform. But I think things have moved on and what was back then seen as the right way (or just fresh new way) is now seen differently.

For example - is it really "better" to say 7.even? rather than isEven(7)? (Strict OO vs multi-paradigm/functional programming).

Or is the article's example of a data model migration really better than a series of alter table sql statements? (Putting OO on top of a relation database using an ORM.)

And why not go for a pure SPA rather than an AJAX-sprinkled compromise between a traditional server-side rendered html app and a SPA?

Re: Why I believe Rails is still relevant in 2019

#79
post #41

Rails is fine but didn't age well, specially the lack of strong functional programming support. Other nag is that it's hard to not do things the rails way - this monoculture reinforces the appearance that is fine because people looking to do something different just don't use rails. And when you "scale" rails is not really rails that scales as much as it is the architecture - it could be applied to other frameworks.…

Feel free to downvote, but please present counterarguments so everyone can learn.

Re: Why I believe Rails is still relevant in 2019

#80
post #78

I think for what it is - for its paradigm if you will - ruby on rails is an extremely well-designed platform. But I think things have moved on and what was back then seen as the right way (or just fresh new way) is now seen differently. For example - is it really "better" to say 7.even? rather than isEven(7)? (Strict OO vs multi-paradigm/functional programming). Or is the article's example of a data model migration r…

And PS: Everything is relevant today if you are stuck with it. The question is if you would start a new project on it if you didn't already had a lot invested in it?
Post reply on HN