Yes I’m obviously a huge Rust fan too but for this use case, at this point in time it doesn’t feel like an easy sell.
-
-
Replying to @wezm
Well, if correctness and confidence in refactoring is the important point though, I _do_ see good chances, as many who do it have a great track record.
1 reply 0 retweets 0 likes -
Replying to @Argorak
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.
1 reply 0 retweets 1 like -
Replying to @wezm
This is an unpopular opinion, but in a business context, I don't think this is a good case for too much focus on likes, wants and consensus. It's a question of goals and evaluations. I've seen too many projects fail by getting that wrong.
2 replies 0 retweets 0 likes -
Replying to @Argorak
By likes do you mean what the team like versus what is a good tool for building robust software that can sustain the business?
1 reply 0 retweets 0 likes -
Replying to @wezm
Yes. What the tool gives your company is the most important part of it.
2 replies 0 retweets 0 likes -
Replying to @Argorak
Right. Thing is many are convinced that the time to market, and expressiveness of Ruby are business benefits that trump the features other tools can bring.
1 reply 0 retweets 0 likes -
Replying to @wezm
Well, then stick with Ruby and don't switch to anything. You will never practically migrate away from it anyways, so all you can practically search for is a co-language that gives you different guarantees.
2 replies 0 retweets 0 likes -
Replying to @Argorak
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.1 reply 0 retweets 0 likes -
Replying to @wezm
Sure, my point is that you can still consult and that means to hit those arguments head-on :). If you have frequent issues with critical things blowing at runtime, that's a good thing to start a discussion about.
1 reply 0 retweets 0 likes
-
-
Replying to @wezm
Great, happy to give any practical help, I'm very used to those discussions. A good starting point would be "I don't feel confident in writing this backend in Ruby, because I'm sure it will wake up Ops at night :)." If a senior says that, it has some weight.
1 reply 0 retweets 0 likes -
Replying to @Argorak
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.
2 replies 0 retweets 0 likes - 1 more reply
New conversation -
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.
this I feel I am doing 