4 ms·
Yes, I want to highlight what you say about large companies. ruby really shines, I think, if you are a solo dev or a small team, where everybody is on the same
by vlz 3y ago
Yes, I want to highlight what you say about large companies. ruby really shines, I think, if you are a solo dev or a small team, where everybody is on the same page and the codebase is completely understood. It is also good for libraries with a clear focus. For larger projects, it might work too, but you would need some good culture of "keep it simple" around it. A few ego-trips of supposedly smart devs and things can get hard to understand and hard to work with fast.
- cutler 3y agoHere we go again with the Ruby isn't suitable for large projects nonsense. Github, Shopify and Stripe seem to be managing perfectly fine with Ruby, thank you very much.
- vlz 3y agoSure, but as I said, probably not without establishing some culture around it. Just for fun, let's look at shopify's Ruby Style Guide under "General"[0]: Avoid mutating arguments. Avoid monkeypatching. ... Avoid needless metaprogramming. Prefer public_send over send so as not to circumvent private protected visibility. Write ruby -w safe code. ... [0]: https://ruby-style-guide.shopify.dev/#general https://ruby-style-guide.shopify.dev/#general
- mokkol 3y agoEvery big company has (and if they don't, they should) style guides. In Ruby people tend to use something like Rubocop (which is a static code analyzer/linter) to agree on a style. That will even be added as a default in Rails 8.