Hell, if I open a directory of photos and my OS tries to pull exif data for each one, it would be wild if that caused those files to be fully downloaded and consume disk space.

Tauri itself doesn't render web views. It uses wry under the hood. Dioxus isn't a web view at all and deserves a fundamentally different purpose.

> Can you name a few objective reasons against Blink/WebKit (the technology) that does not involve just not liking Google/Apple?

If you have a cross platform application, it sucks having to worry about which features work or don't work based on which engine is available and how old it is. You also don't know if there are user scripts being injected that are affecting the experience. It's impossible to debug and many users don't even know what browser engine is being used, they just know your app doesn't work.

If you build for Servo, it works exactly the same on every platform. You could use wry and test that Edge is good on Windows, WebKit works on the past few versions of Macos, gtk WebKit works, etc etc, or you can just use Servo.

Not to mention, Servo is probably much lighter than whatever flavor of chromium the user has installed under the hood.

We already have zero retention energy storage. The phenomenon in this paper isn't even all that new by the author's own admission—that's how it got to the fifty third revision. The tier 2 setup described here is purely speculative. Producing a single square centimeter of pure "fluorographane" (sic?) is still a task that would be exceedingly challenging for a research lab. And it's not clear how much energy it would take to read and write the data, or support the hardware necessary to do it at a speed that's makes it uniquely useful. Even if all of these problems are solved, and the cost is made reasonable, it's still completely unclear if it would be substantially better than what we have today.

Flash, on the other hand, had made steady incremental progress from the time it was first described until it was fully commercialized.

Demonstrating this stuff is possible isn't the hard part, it seems. Productionizing it is. You have to have exceedingly fast read and write speeds: who cares if it can store an exabyte if it takes all month to read it, or if you produce data faster than you can write it? It has to be durable under adverse conditions. It has to be practical to manufacture the medium and the drives. You probably don't want to have to need a separate device to read and a device to write. By the time most of these problems are worked out, most of these technologies aren't a whole lot better than existing tech.

Stick this on the "Wouldn't it be nice if graphene..." pile.

Moreover, you don't even need Linux and Wireguard. WebRTC accomplishes p2p encrypted traffic without libraries.