Slight tangent:
Hopefully, the next version of WebRTC standard removes the need for signaling servers and other server side infrastructure (ICE, STUN). I understand that ~35% of sessions would fail without them, but the server side needs to be a fallback, instead of a required step, during connection setup
While the attack is technically feasible, complexity and sophistication do not lend this to wide deployment. Someone with a lot of time, money and drive (think heist movie, or spy agency) to hack a person of interest might find this attack viable, assuming they find a line of sight to the mic. But if one's dealing with determined hackers, there is likely a multitude of other lower hanging fruit to first pick off.
Question to @syrusakbary - When is wasmer support in Windows likely to reach beta status? Would mingw-64 be a better Windows target than Win32, for porting unix-y wasmer code, especially related to WASI?
Thank you for the clarification. Some questions related to V8 perf:
1. WASM <--> JS/Host calls seem to have a higher cost on chrome than FF [1][2]. Is that in your optimization roadmap?
2. Wasmer tracks V8 perf against other backbends, and the LLVM backend consistently outperforms V8 [3]. Can anything be done to address this, especially for node, where the compile time cost of a super optimizing compiler might be beneficial in certain applications?
The answer to the question the headline poses, inferring from people sampled in the article is: "They mostly end up in a English related academic position in school or college setting"
I might be wrong, but I believe the glass is the output of an AI program, trained by observing multiple manually corrected iterations of glass making, to arrange impurities while making glass, for object recognition. The glass and impurities themselves aren't the AI here, the program that can repeatedly be used in mass production to make object-recognizing glass, is the AI
The only reason to use an IPC or go through the kernel is to expose the fs to the rest of the OS. If an app doesn't intend to expose the fs, the entirety of the fs can exist within the app process.
Quoting:
> "Unlike many other operating systems, the notion of “mounted filesystems” does not live in a globally accessible table. Instead, the question “what mountpoints exist?” can only be answered on a filesystem-specific basis -- an arbitrary filesystem may not have access to the information about what mountpoints exist elsewhere."
A userspace program can completely avoid kernel IPC if it has no intention to expose the fs to other processes. Client and server code can exist within same "app", without IPC, in the same process
libfs [1] is a userspace library offered by fuchsia abstracting the traditional vfs (virtual filesystem interface), allowing the fs to exist wholly in userspace, without a kernel component.
Quoting:
> Unlike more common monolithic kernels, Fuchsia’s filesystems live entirely within userspace. They are not linked nor loaded with the kernel; they are simply userspace processes which implement servers that can appear as filesystems
Fuchsia has an interesting take on filesystems [1]. One can write it completely in the user-space, avoiding expensive kernel<-->user-space switching. Additional benefit of storage sand-boxing comes for free, as each app can implement it's own fs, with the rest of the system unawares of it's existence.
I wish such a fully-user-space option existed for Linux. This work is philosophically in the opposite direction, moving more functionality into kernel space for perf benefits.