What part of Rust compilation is the bottleneck?

Re:What part of Rust compilation is the bottleneck? by andenacitelli on Saturday March 16, 2024 @11:39AM (#39726852)

Woah, 200k LoC is considered medium? I work at a Series A startup and our entire product (which is actually much more than a CRUD app) is only in the high tens of thousands, so that’s just a funny thought for me.

My theory is that because Rust is a low level language you tend to miss out on higher level primitives that promote more code reuse. Another theory is that Rust is mature but not quite as mature as something like Java, so there are fewer mature dependencies for you to delegate your work to.

Thoughts on what’s accurate? For context, I’ve written a bit of Rust myself, but am definitely a beginner.

[ Parent | on HN ]

Re:What part of Rust compilation is the bottleneck? by pornel on Saturday March 16, 2024 @05:09PM (#39729475)

Rust is very good at code reuse.

Generics and cross-crate inlining enable zero-(runtime)cost abstractions, meaning there’s usually no perf downside to using 3rd party code instead of your own.

Strict type system, standardized error checking, thread safety in interfaces, and built in tooling for API documentation makes using libraries relatively easy.

The ecosystem is pretty large now, and has a culture of respecting semver, and focus on safety and reliability.

Cargo makes adding dependencies easy (the most common complaint is that it’s too easy, and people use too many dependencies).

[ Parent | on HN ]

Re:What part of Rust compilation is the bottleneck? by paulddraper on Sunday March 17, 2024 @01:34PM (#39736210)

You know Series A is early stage, right?

[ Parent | on HN ]