I have the same concern. Something might be worth looking into is replacing docker with Podman because it runs as the authenticated user rather than using a daemon running as root. Also, I believe Podman desktop allows for multiple VMs.
Also consider QubesOS. Where everything runs in a VM (if you can find appropriate hardware on which to run it).
Less flexible but easier to install is ChromeOS FLEX (or a high end Chromebook). Like QubesOS, ChromeOS lets you run Linux in a VM but with the ability to open native windows.
I can see it being useful in a corporate setting to limit which sites you can visit with Chrome to just your secure admin panels and internal apps. Then use Firefox to go to dangerous places like… the Internet.
That way if one of your users clicks a link in a phishing email Chrome simply won’t open it.
I'd be interested to hear if anyone has learned Rust without first understanding memory addressing and pointers.
Although I think Rust is a better way to write safe code and the industry is right to adopt it, it seems like a heavy lift to learn about heaps, stacks and pointers whilst also learning about ownership and lifetimes.
I don't really think that C++ is worth learning unless you have to work on an existing C++ codebase.
The reason usually cited for why not BitTorrent for software packages is because it makes public what package versions you have and haven’t downloaded.
You don’t need to wait for web-assembly to solve these problems.
TA mentions 3 languages (Elm, Reason & Purescript) that combine sound type-checking and immutability right now.
None of these bring the cognitive overhead of Rust’s borrow checker and, in the case of Reason at least, compile at lightning speed to readable (though optimised) JS.
Also consider QubesOS. Where everything runs in a VM (if you can find appropriate hardware on which to run it).
Less flexible but easier to install is ChromeOS FLEX (or a high end Chromebook). Like QubesOS, ChromeOS lets you run Linux in a VM but with the ability to open native windows.