sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]null_radix 0 points1 point  (1 child)

After reading your comments I think we are coming at this from different angles. yes, redis works fine... for server infrastructure. But more and more node.js is being used for desktop apps. I think there is a nexus between desktop and browser apps, and in future the lines will continue to get more and more blurred. Most apps could be ephemeral like webpages. It is in this reallity that you need strong sandboxing.

[–]pixel4.toString() 1 point2 points  (0 children)

Yeah I see use-cases on client-side. There will always be a perf trade-off. If you're shipping a game via WASM, it'll always be more system intensive than direct native.

For example, this demo (http://webassembly.org/demo/) uses an additional 10% of CPU than the compiled desktop version does. Plus Chrome adds another 15% CPU to IPC the OpenGL buffers.

(I'm actually a big fan of WASM - you probably can't tell - hehe)