From: Alexander D. <al...@mu...> - 2014-01-09 15:21:45
|
Hi Dominique, > Did you also considered PNaCl : > http://www.infoq.com/news/2013/05/pnacl-google-chrome-llvm > > http://www.chromium.org/nativeclient/pnacl/introduction-to-portable-native-client > This approach could save you a lot of effort, also with the benefit of > compiled and optimized LLVM code. > The drawback is that it is restricted to Google Chrome but I think the > future (or at least a great part of it) relies on technologies like LLVM. > I did not try PNaCl, looks like an interesting approach! I might experiment with this for a little bit. If I do, I'll be sure to report back here with what I find. Or if anyone else has already tried this, I'd love to hear what your results were like. > In addition, rewriting the engine in javascript is a kind of fork, in the > sense that further improvements of the code, whatever side it is, won’t > benefit to the other implementation. That’s currently my main concern for > the deployment of Guido (and of INScore too) on the web. > Hmm. I think that's a very reasonable concern, one that I hadn't really considered. On one hand, I don't want to dilute development efforts. Or make more work by having to re-implement updates separately in both languages. But on the other hand, a fork could let us experiment with different approaches. And it could let us tap in to the large pool of javascript/node.js developers. I'm not yet sure how these balance out. I think I will continue to work on the javascript port, as long as it doesn't detract from the principal Guido effort. If you find that the fork every does become a problem, please do let me know. I don't want to do anything that works against the great projects that you all are doing. > ps: concerning the web service, it is running on > http://guidoservice.grame.fr (in case you want to experiment) > It differs from the NoteServer since all the library API is available and > thus, one could potentially build real applications over the web. > The guido station is not very stable and could be temporarily unavailable > because it has recently suffered of piracy. > The service documentation is available at http://guido.grame.fr/ > > Cool! I'd love to try this out, thanks for sharing it with me! This could be very helpful for making some initial lessons at Musikata. One of the reasons I got into Guido was to generate both audio and visual outputs from the same encoding. I think this service could be a nice way to experiment with that. -Alex |