5 ms·
Could Native Client be the way forward for this approach? Link: http://code.google.com/p/nativeclient-sdk/ http://code.google.com/p/nativeclient-sdk/
by jb3 16y ago
Could Native Client be the way forward for this approach?
Link: http://code.google.com/p/nativeclient-sdk/ http://code.google.com/p/nativeclient-sdk/
- leoc 16y agoYes. http://news.ycombinator.com/item?id=1056391 http://news.ycombinator.com/item?id=1056391 (later update: http://labs.qt.nokia.com/2010/06/25/qt-for-google-native-client-preview/ http://labs.qt.nokia.com/2010/06/25/qt-for-google-native-cli... , transcript of Kay talk: http://blog.moryton.net/2007/12/computer-revolution-hasnt-happened-yet.html http://blog.moryton.net/2007/12/computer-revolution-hasnt-ha... ) WebGL wouldn't hurt either.
- Detrus 16y agoThe development team proposed NaCl as a potential solution to many of the format problems. We could make a lot of custom compression formats that would be better than gzip. A multitude of image formats tuned for various categories of images or videos. Fast JavaScript could go a long way in that direction too https://github.com/antimatter15/weppy https://github.com/antimatter15/weppy With types and WebGL hardware access who knows. NaCl project has social forces going against it. People want a homogenous platform. Platforms solve a social problem, developers become familiar with the same API, make libraries for it, make development easier, etc.. NaCl would have to play that game and it takes a long time. By the time it's done it won't be a good fit for problems of the day, just like high level VMs today.