60 points by ibobev 5 days ago | 16 comments | View on ycombinator
Panzerschrek about 5 hours ago |
yeureka about 17 hours ago |
KolmogorovComp about 13 hours ago |
Traditional where allocations matters, like for embedded devices you would use no-std.
An alternative standard library with a different focus is entirely possible.
Or as a middle ground a lint flagging allocations.
As an aside I believe the last ‘expect’ issue to triggers an existing clippy lint.
krukah about 14 hours ago |
TBF Rust v1.100 makes a big leap in permitting custom allocators, but mandating would be ideal in the spirit of "explicit is better implicit". I like adding lints to defend against some of these footguns, but more compiler-driven transparency around quiet allocations would be so nice.
fwlr about 17 hours ago |
ngriffiths about 16 hours ago |
In hindsight, it would be pretty funny if "hey can you rewrite this game in Rust" is sufficient instructions to end up with memory-efficient code. In fact it would be pretty funny if it were enough to get this thing written in Rust, for all the specific details of what you actually mean when you say "this game"
daxfohl about 14 hours ago |
alfiedotwtf about 18 hours ago |
ElUncivio about 14 hours ago |
Chromium-based applications consume so much memory, not because they don't use manual memory management, but because JS used for application code isn't nearly as efficient in memory usage as any other proper language. Also the browser engine itself is optimized in such a way, that it sacrifices memory usage to gain more speed.