|
|
|
|
|
by emidln
2228 days ago
|
|
That's not true. Source: I work at an HFT. Rust is very interesting for Greenfield work. The major down side is millions of lines of legacy C++, the more useful already using C++17 or C++2a, which typically provides a lot of what you'd get out of Rust's stdlib and ecosystem but already packaged and integrated. When you choose Rust at an HFT you have to worry about integration with codegen tools (generating efficient Java/C++/$HDL and reasonable throughput Python for protocol definitions is table stakes at any HFT I've heard of) and build pipelines (which might already have distributed building/caching infrastructures and fancy packaging/deployment. Rust has some benefits (and still integrates reasonably well at the ABI level), but modern C++ compilers are no slouches. Rust provides a friendly dev experience, which is a valuable thing, but a lot of the ecosystem advantages are old hat at companies with mature codebases. |
|
Just curious to find out