For now, flatpack and snap sandboxes perf hit are quite significant, and devs don't manage the permissions well so you often end up with software that can't open the files you want.
When you fire and electron app from a sandbox, it's a hog riding a slug, then you try to open your files only to find yourself in a temp folder or chrooted to a config subdir.
It think those tech can bring a lot, but there is still work to do.
Flatpak doesn't hurt performance any worse than something like Docker. It's Snap that's slower since they keep the entire app compressed on disk. Permissions are also up to the app developer in the case of Flatpak so if they don't use portals like they're supposed to then they can just allow the app to access the whole host filesystem. You can change this easily too through your terminal or an app like Flatseal.
Don’t generalize your problems with a specific software (Veracrypt) to all drive encryption software. Plenty of drive encryption solutions are fast, reliable, and resilient. (You could also be having a hardware problem exacerbated by adding an abstraction layer.)
I’ve used LUKS, GELI, ZFS encryption, FileVault, and BitLocker across numerous drives over the past decade (albeit in different individual proportions and timelines) with no corruption problems.
I’ve not used verycrypt, only normal Linux LUKS device mapper encryption, ZFS encryption and windows bitlocker full disk encryption with a paraphrase entered on boot (no tpm). But I haven’t had this problem with any of those.
I’d suggest either your SSD just loses data on power off which is a problem with some SSDs or it’s some veracrypt specific issue that I wouldn’t be familiar with.
Id encourage you to try out one of the above options.
You probably have some fun disk caching turned on in the OS or your disk has a built in cache that it’s not properly flushing. I’ve seen this before with cheap SSDs.
Maybe a dumb question, but are you on windows? Check that Defender isn't scanning every single time data is written to your veracrypt drive. When I was on windows, the most painful slowdowns were almost invariably caused by Windows Defender.
No. I run a server in my basement, and for the past 5+ years, every one of its drives have been LUKS encrypted, including external backup drives. I've had no issues with encryption (corruption, speed, or otherwise), only disk hardware failing outright.
Servers and consumer laptop are very different beast though, so not sure the comparison hold. You don't shut them off often, they don't go to sleep, rarely undergo shock, plane travel or forced shut down...
Friend, LUKS is reliable. LUKS doesn't just eat data in those edgecases you talk about, there would be tons of reports if that were the case. LUKS is used all over the place for non-server uses too.
I can count at least 3 devices that are all LUKS-encrypted that are used as consumer devices daily. I trip over the power cord, I let the battery die, I drop it, I fly regularly, etc, etc. Never once had a single issue.
In fact, the single time that I've had FS issues under Linux was running under Hyper-V but that's because of the slowly-being-uncovered serious issues w/ Hyper-V.
The better solution to these kind of problems is having a backup concept with an implementation and regular testing of backups.
The encryption exposed a problem with your disks or system in general. Depending on what the problem was, the problem is still there but you are not seeing it. Now you have a possible problem and unencrypted files.
Same but I already find ajax based app very slow if they implement optimist updates, now with this system, you have to wait a round trip for each interactions. This means click a counter will round trip before updating?
You can apply this to any interaction where you have to wait for a round-trip anyway. It saves you coming up with a JSON schema and endpoint for the request, and then gluing it all together.
It doesn't mean that you don't use javascript at all, you just use it in a limited fashion for enhancing specific bits of your website. Just like it was in the 2000s when making websites was easy.
If you want to save state for the counter to the server you would do a round trip. Otherwise you’d use some light weight JS lib, most popular one for simple interactions is Alpine.js.
So simple ui JavaScript use Alpine and something like form validation and showing errors will do a round trip and save you writing validation twice (on the client and on the server).
Ok, so the trade off is a less snappy UI as soon as you have a state, because you can't do optimistic updates on the view, send the request, then deal with the error.
But you write only the code of the validation, and the vue, once, so it's more productive, and the state is always consistent.
I assume this means no PWA mode, although I don't really miss this.
The round trip is very quick, websocket with a tiny payload in most cases.
This video does a great job of discussing the advantages (skip forward to 6:50) https://youtu.be/8xJzHq8ru0M
Payload size doesn't matter that much, a ping is ping.
Currently my ping to this website is 167 ms:
ping news.ycombinator.com
PING news.ycombinator.com (209.216.230.240) 56(84) bytes of data.
64 bytes from news.ycombinator.com (209.216.230.240): icmp_seq=1 ttl=49 time=167 ms
64 bytes from news.ycombinator.com (209.216.230.240): icmp_seq=2 ttl=49 time=167 ms
64 bytes from news.ycombinator.com (209.216.230.240): icmp_seq=3 ttl=49 time=167 ms
Which means it's a cost I have to pay, before payload matters, before parsing matters, before rendering matters.
I'm at home, on fiber, on an ethernet cable, so ping should be very fast. And it can be:
ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=114 time=5.63 ms
Unfortunately, the network is not uniform.
It's of course, worse on Wifi, and even worse on mobile phone, on the go. Depending on your location, YMMV quite a lot as well. Then you have hardware quality playing a role, the user may use other software (torrenting, streaming, playing) that can also affect that.
Bottom line, you cannot assume the internet connection is snappy. Or stable (which is a problem with websocket, as you have to implement robust automatic reconnect, and it is slow and expensive, but then your use cannot use your software).
So knowing the trade off you make is important. On a local network in the corporate world, life view seems like a terrific deal. On a heavy mobile user centric app, it will probably hinder your app ergonomics.
It's a tough ethical choice. On one hand, you want a company to avoid leaking data to bad actors, on the other hand, this would probably first used against legitimate whistleblowers.
As the basis we offer our technology that works as a converter, it has only a positive effect. You can use our platform to upload documents, share with contractors, with the internal team and be sure that all these sensitive documents are marked with invisible marks, and in case of a leak using an investigation tool, you will be able to find the source of the leak. Additionally, we can help to mark documents sent via email our printed out, once again it has just a positive function for the company to be sure that all their info is under the control. With our technology, we want to help to create a preventive effect.