3 ms·
> 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
by mountainriver 5y ago
> 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
- postmodern_mod3 5y agoHow 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.