4 ms·
> If you can't stomach Rust for some reason, and I'm one of those people, there are plenty of choices out there without all the pitfalls of C++ or C. Unless yo
by ivmaykov 1y ago
> If you can't stomach Rust for some reason, and I'm one of those people, there are plenty of choices out there without all the pitfalls of C++ or C.
Unless you are doing embedded programming ...
- fsloth 1y agoI think embedded is one of the specific buckets. You target the compiler your client uses for their platform. There is very little choice there.
- int_19h 1y agoEven then you're probably better off using something safer that transpiles to C.
- fsloth 1y ago”Transpiles to c” - how do you generally optimize single line performance hotspots in that case?
- int_19h 1y agoI don't see why that would make any difference? The generated C code is just a build artifact in this case, similar to IRs often used by compilers internally. You don't think about e.g. gcc IR when you optimize hotspots in code written in C, though - you just look at the C source and the generated asm code. If you have, say, Zig transpiling to C (which it can do with `-ofmt=c`), you'd similarly look at the Zig source and the generated asm code.