2 ms·
> It's a painful problem to crack once you hit those limits. If you hit that doing something novel and obscure, sure. If it is literally parsing JSON, you spen
by dragonwriter 4y ago
> It's a painful problem to crack once you hit those limits.
If you hit that doing something novel and obscure, sure. If it is literally parsing JSON, you spend a little effort researching non-stdlib JSON parsing libraries, pick one of the several stable much-faster-than-stdlib ones, and move on.
- hannofcart 4y agoLike I mentioned we did that. You can get a small arithmetic multiple speed up. But moving these services to rust basically made our instance counts drop from 32 to 2. Once the team has the know-how to write a service in Rust/Golang or even the modern pleasant to write Java, it becomes hard to justify why we'd pick Python for a new service at all.
- superbatfish 4y agoHe explicitly mentioned that path…
- dragonwriter 4y agoHe explicitly mentioned some of the troubles you might have implementing and maintaining that yourself via FFI. He very much did not explicitly mention that its already done, with established results, and that the described “pain” isn’t something you have to take on at all.