4 ms·
Apart from "safe" and "unsafe" we should also have "trusted" and "untrusted". Software is getting complicated and supply chain attacks are real.
by amelius 3y ago
Apart from "safe" and "unsafe" we should also have "trusted" and "untrusted".
Software is getting complicated and supply chain attacks are real.
- GuB-42 3y agoIsn't it what "git blame" is for?
- amelius 3y agoBasically, if you use a library that you don't trust, you have to run it inside a sandbox so that it cannot do stuff that you don't want it to do, e.g. access the entire filesystem or peek/poke in another library's memory. The sandbox should be part of the language.
- massysett 3y agoSafe Haskell sort of addressed this, though I didn’t find it useful in practice. https://downloads.haskell.org/~ghc/7.8.4/docs/html/users_guide/safe-haskell.html https://downloads.haskell.org/~ghc/7.8.4/docs/html/users_gui...
- ReactiveJelly 3y agoAgreed. 5 years ago I thought that Haskell's IO monad was genius. I hope it trickles into a mainstream language before I retire. Sure, it's an extra arg to every non-pure function. So what? Write more pure functions! If a function shouldn't use the network, pass it an IO that can't do so. If it shouldn't touch disk, pass it an IO that can't do so. This may complicated printf logging... Or maybe there is an IO that only allows passing messages to a logging module, and the logging module can write to disk. So the logging module gets more auditing attention than pure functions.
- empath-nirvana 3y agoI think where this is headed is algebraic effects, not using an io monad.
- c_crank 3y agoAll of the hardware your machine runs on would be 'untrusted'. We sit on a swiss cheese palace. Might as well get used to it.
- deleted 3y ago[deleted]