You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rust is blazingly fast and memory-efficient: with no runtime or garbage collector, it can power performance-critical services, run on embedded devices, and easily integrate with other languages.
This is not totally true, as Rust has a minimal, pre-startup runtime, similar to behavior provided by crt0.o in languages like C.
It does not have an "active runtime" or "interpreter", like Python, Java, or Go, but it does still have a runtime to the same level that languages like C/C++ do.
This one is hard, because "runtime" is an overly loaded and in-specific term. We are trying to get across the point that there is "nothing behind the scenes" (which would also be considered a "runtime"), but this did cause confusion at least once on twitter.
What needs to be fixed?
The main site states:
This is not totally true, as Rust has a minimal, pre-startup runtime, similar to behavior provided by
crt0.o
in languages like C.It does not have an "active runtime" or "interpreter", like Python, Java, or Go, but it does still have a runtime to the same level that languages like C/C++ do.
Page(s) Affected
Main webpage, https://www.rust-lang.org/
Suggested Improvement
This one is hard, because "runtime" is an overly loaded and in-specific term. We are trying to get across the point that there is "nothing behind the scenes" (which would also be considered a "runtime"), but this did cause confusion at least once on twitter.
The old FAQ did address this point directly.
The text was updated successfully, but these errors were encountered: