My FP protocol is designed to make it indifferent to run an application on local hardware or to distribute its execution among remote machines.
That's why the licensing issue is so important: the user has the right to know what is running on the remote end.
But frankly, I don't think this "Java done right with Electron" is going to work in practice as a portability layer.
It will be portable to... Chrome.
And won't be better for security because it will be overcomplicated.
Sorry, I don't know to what are you referring with "my FP protocol" :)
Not only Chrome supports WebAssembly, Firefox is a major proponent and the speaker in the video is from Mozilla. If I understand that explaination correctly WebAssembly is not intended to be run only by Web browsers
@Shamar seems reasonable, maybe a bit too radical than what I imagined :-)
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!