For those than learn it yes. For folks used to working with a language like Ruby it’s a huge leap. Don’t get me wrong though, I’m running a weekly Rust session at work and trying to help people make that leap.
Yes I’ve done more or less that. Problem is this is an 6 year old, 50k line Ruby codebase bound to JRuby for concurrency. Change is a hard and big decision that’s being worked through at the moment.
-
-
Yeah, no need to rush it. Existing code has also proven its worth. The core of what I'm saying is: don't get defensive early because you don't want to impose things on your colleagues because they might not want.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If bound to JRuby for concurrency then it might be worth looking at other JVM languages? That’s on the assumption you’re happy with the JVM in production. Or maybe wait until Stripes type checker for Ruby is available? https://medium.com/byteconf/stripe-is-building-a-ruby-typechecker-d6cd7cee6abf …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
to be clear I’m not the one making this decision. I am the one who would like to be able to write software knowing that it’s not going to unexpectedly blow up at runtime. We’ll see how it plays out.
this I feel I am doing 