Conversation

Jarkko Sakkinen

all sort of glitch with #rustlang community comes to personally in the end how you look at a programming language: a language or purely just an opcode generator. one example of such glitch is IMHO unrobust handling of OOM conditions. So you end up getting safe but and super fat and resource wasteful user space programs. But still memory-safe in the language level, which does not provide safety for e.g. any possible DoS attack.
1
0
1
Unrobust meaning that you can do all of this but would have to put unrealistic amount of effort to accomplish any possible e,g. business or even academic goals.
1
0
1

Jarkko Sakkinen

Edited 1 year ago
Rust is robust in the sense how it can respond to different memory safety issues but it is robust to the limits "as long as you accept the default response". If you don't agree with the response, there's way to go around it but is sort of "not recommended for most". It is a bit like you would limit email only pre-defined template responses.

So the stimulus part of the safe systems programming language equation is gotten right but hard coded response as defaults is not a great thing tbh.
1
0
0

@jarkko how is this done in a more robust way elsewhere

0
0
0