Maybe we would get a microphone on mars.
Just kidding i know air pressure is vastly different, but still it would be cool to listen to ambient sound from there
i think so. The biggest hurdle with new languages is that you are cut off from a 3rdparty library ecosystem. Being compatible with C 3rd party libraries is a big win.
Tangential, but Flash had a nice side effect that the "app" could be exported in a self contained way via SWF.
Exporting this site for example in a future proof way is not that obvious. (Exporting as pdf wont work with the webgl applets, exporting the html page might work but is error prone depending in the website structure)
50 years from now, flash emulators will still work on swf files, but these sites might be lost. Or is there a way to archive sites like this?
>The user writes the data to CPU mapped GPU memory first and then issues a copy command, which transforms the data to optimal compressed format.
Wouldnt this mean double gpu memory usage for uploading a potentially large image? (Even if just for the time the copy is finished)
Vulkan lets the user copy from cpu (host_visible) memory to gpu (device_local) memory without an intermediate gpu buffer, afaik there is no double vram usage there but i might be wrong on that.
Great article btw. I hope something comes out of this!
My takeaway is that sandboxing should be more readily available, and integrated into the OS.
I used sandboxie a while ago for stuff like this, but afaik windows has some sandbox built into it since a few years which I didnt think about until now.
Thing is (correct.me if Im wrong), that if you use modules, all of your code need to use modules (e.g. you cant have mixed #include <vector> and import <vector>; in your project). Which rules out a lot of 3rd party code you might want to depend on.