6 comments

[ 2.8 ms ] story [ 31.2 ms ] thread
Packaged this up based on https://github.com/SiPlus/WebQuake It was tough turning all the synchronous asset resource requests into async ones. Not sure why this is a necessity for Chrome Packaged apps for local resources anyway. :-(
Is there any performance difference between the Chrome app and the original JS port? What are the benefits?
Potentially, raw socket access. This could be a server as well as a client. But I need to do some more work porting it.
Thats really cool
It doesn't seem to work on Linux.
Great work! Loads quickly for me