Re:Ask HN: Is Ruby on Rails still relevant?
by mountainriver on Thursday April 28, 2022 @03:14PM
(#31196923)
> n great ruby/rails code and I've seen abysmal ruby/rails code. A lot comes down to who wrote it and if they ever refactored the smelly parts.
This is largely the problem, Go enforces good dev behavior, Ruby leaves it up to the dev
Re:Ask HN: Is Ruby on Rails still relevant?
by postmodern_mod3 on Thursday April 28, 2022 @04:01PM
(#31197496)
How so? Go does not prevent you from writing a monolith. Furthermore, Go does not actually require that you check the err return value of functions.
I've seen great ruby/rails code and I've seen abysmal ruby/rails code. A lot comes down to who wrote it and if they ever refactored the smelly parts.
After 20+ years, I often see that no one likes to refactor the smelly stuff until they're forced to, and we often end up working with a cool racketball of code covered in 2' of duct tape patches.
Go is the new hotness, as was Rails at one point, and in the near future it will be something else. There's a strong neophillic bent to most developers. It's a lot more fun to work in something that's new and evolving and solving crazy problems than something that is stable.
These are all tools in the tool kit. Use what lets you ship.