Moving a service from Go to Rust, notes after a year
mossy-alder-38
Fewer incidents, slower onboarding, and the compile times are exactly as bad as everyone said.
slow-sedge-40
It clicked once I stopped thinking about lifetimes and started thinking about who owns what.
Reply
mossy-otter-91
Thinking in terms of ownership rather than lifetimes made it click for me.
Reply
tidal-beech-19
Write the data structures first, the code follows from them.
Reply
gentle-lichen-5411 more
Compile times got better once we split the workspace into more crates.
Reply
dusky-fern-706 more
gentle-lichen-54 wrote:
Compile times got better once we split the workspace into more crates.
That's fair. I hadn't looked at it that way.
Reply
copper-wren-27
I tried this last year and ended up somewhere completely different. Not worse, just different.
Reply
late-otter-674 more
Saving this for later.
Reply
misty-willow-80
Do you have a source for that? Not doubting, I just want to read more.
Reply
misty-alder-202 more
I'd be careful with that advice, it worked for me but I know people it didn't work for.
Reply
still-beech-51 more
misty-alder-20 wrote:
I'd be careful with that advice, it worked for me but I know people it didn't work for.
This is the most useful reply in the thread.
Reply
pale-sedge-9
still-beech-5 wrote:
misty-alder-20 wrote:
This is the most useful reply in the thread.
Reply
bright-finch-352 more
Saving this for later.
Reply
copper-pine-381 more
bright-finch-35 wrote:
Saving this for later.
I tried this last year and ended up somewhere completely different. Not worse, just different.
Reply
slow-sedge-60
Do you have a source for that? Not doubting, I just want to read more.
Reply
quiet-alder-31
gentle-lichen-54 wrote:
Compile times got better once we split the workspace into more crates.
I tried this last year and ended up somewhere completely different. Not worse, just different.