I get that for sure but…
This is the thinking that apply 100% also to any piece of user space code that I might do. I figure out the best possible solution that I can think of with my limited skills and then pick the tool that I try to nail it sometimes succeeding and sometimes failing. So yeah, my world is as plain and simple as that :-) Engineering problem at hand is the first priority, and obviously to pick the right tool I need to exactly compare pros and cons of them for that particular problem.
A recent example is an authentication module prototype that I’m developing for Ethereum ecosystem (and presenting possibly at ethprague). For that I’m most likely using Rust, and ended up to that outcome by comparing pros and cons of possible alternatives.
vm-memory
is really cool and should be IMHO part of stdlib :-) best way to map files and other memory so far in #Rust.
Some project types where you absolutely need memory mapped I/O are:
I.e. anything with high scalability, high availability and in real-time processing low latency.
Hey folks,
Danke für all the support. You can save 15% on everything on #BandcampFriday today, when you use the discount code "DANKE" at checkout, from today until Monday!
@calbaker No.
It has static and run-time checks for memory safety, which is not the same as being memory safe. Just like Go, Java, Python and what not have measures for memory safety but instead of borrow checker they use a garbage collector.
Rust is less safe than any of those languages because the result is an ELF binary, which is roughly a twist of what C++ source generates with fancy checks. Same attack techniques, like ROP (return-oriented programming) gadgets still apply as for any possible ELF binary ever compiled.