Unless civet's compiled output is hard to read you could always just check in the compiled Typescript source and continue from there if it gets abandoned. Not much of a risk when the migration is built in by the way the tool works in normal use.
There's plenty to criticize about Protonmail but this article is sensationalist bullshit. I'm surprised the HN population is letting itself be goaded like this.
I'd like to posit that getting rewarded for forwarding traffic in combination with the lack of maintenance over the node list makes Sybil attacks on this network the default instead of just a concern.
IMHO your editor should be formatting your Lisp with this kind of indentation anyway, parentheses or not. If you have that, Z-expressions seem kinda moot.
As far as I am aware from the last time I tried to find such a thing the packet-based interactive nature of modern display standards prevents the cheap implementation of these devices, as opposed to the non-interactive, older standards.
Very interesting! Too bad this is only for finding instruction materials. An even bigger problem than finding learning materials I often have when autodidactically diving into a new topic is having to build a concept map, which is always extremely hard.
That definitely is the first thing that comes to mind, but applications need to be built under that model.
Currently all applications assume they get access to everything by default, so even if one was to be able to implement a confirmation dialog, the user would be victim to a battery of requests.
This is not to mention that isolation excludes discoverability, so users would have to manually make files visible to other applications beforehand.
I'm running Qubes 3.2 on my laptop right now (Dell Latitude E5470) and it also fulfills all the requirements to run 4.0.
The certification requirements are higher, but that's basically if people want to stick the Qubes-certified label on their devices, signaling to customers that it measures up to the highest standards of security.
They're not necessary to run Qubes, they're just ideal.
What a coincidence. I've actually been trying to sketch out how to do this in the past few days.
I've also been looking at how projects like Hypercontainer and Clear Containers achieve minimal VM overhead to expand the model to a per-application-instance VM.
Another interesting enabling technology is VirtFS, which can be used for filesystem-level storage virtualization to gain the many benefits of COW and shared caching.
The principal question then is how to allow interaction between different application instances without the user having to manually ferry files between them, as it currently happens with AppVMs on Qubes.
For anyone interested in implementations of the Sieve of Erastothenes, here is a very interesting paper about functional ones, which are harder than they appear at first:
https://www.cs.hmc.edu/~oneill/papers/Sieve-JFP.pdf