Re:Using Rust at a Startup: A Cautionary Tale
by josephcsible on Thursday November 24, 2022 @12:57PM
(#33734237)
If "import ctypes;ctypes.string_at(0xdeadbeef)" in Python doesn't count as memory unsafety, then I don't see why the equivalent in Unsafe Rust would.
[ Parent
| on HN ]
Re:Using Rust at a Startup: A Cautionary Tale
by 3a2d29 on Thursday November 24, 2022 @04:13PM
(#33736304)
Okay I can see you are a beginner.
Those security vulnerabilities found in those rust crates are not possible in python/Elixir/etc
If memory safety doesn’t matter, then let’s stop saying “replace C++ with rust”. Or it does and then you shouldn’t use a security risk like rust in a place you don’t need to.
Re:Using Rust at a Startup: A Cautionary Tale
by josephcsible on Thursday November 24, 2022 @05:06PM
(#33736764)
I am not a beginner.
Those sorts of security vulnerabilities are possible in Python/Elixir/etc. In both Rust and Python/Elixir/etc., they're only possible when you do certain unusual things. You are claiming that the Rust way does count, but that the other languages' ways don't count, with no justification.
Memory safety does matter. Rust is memory-safe and C++ is not, so your conclusion doesn't follow.