4 ms·
Excellent write up, and effective argument for Rust in this application and others. My cynical side sums it up as: "Go sucked for us because we refused to own
by h2odragon 7y ago
Excellent write up, and effective argument for Rust in this application and others. My cynical side sums it up as:
"Go sucked for us because we refused to own our tooling and make a special allocator for this service. Switching to Rust forced us to do that, and life got better"
- staticassertion 7y agoI'm confused. Build a special allocator for Go you mean? That feels like going well beyond typical "own your tooling".
- h2odragon 7y agoI'm outdated. I used to have 4 different python interpreter builds, for different purposes, where the modern world would be using lua as a glue language. I had nothing like the scale, staff, or budget of Discord; all I had was need and tools that could bend to fill it. I think this is a great write up of why they chose a different tool. I don't say it was the wrong decision, they make that argument pretty well too. I'm still surprised that either Go isn't malleable enough to have bent around the need, or they didn't feel it worth more effort than parameter tweaking to bend it so.
- monocasa 7y agoThey were already not allocating, they were just stuck with a GC cycle that'd scan, not find any garbage, and scan again in two minutes.