| It's important to note that this is or will be a W3C standard.
Therefore, it is likely to actually be implemented, to actually be
adopted, and to be reasonably stable once adopted.
For people wanting to write applications for wasm, when running in a
browser, browser security restrictions will apply. That would mean
Csound pieces running in a browser would not have access to the local
file system.
However, this restriction can be avoided either (a) by running Csound
pieces on a local Web server (very easy to do) or (b) targeting an
environment such as NW.js, which, perhaps after some lag time, will
very likely adopt wasm, as they already have adopted PNaCl.
The roadmap for wasm is ambitious and would eventuate in a platform
able to run industrial strength system software at native speed in the
browser on in something like NW.js, including dynamic link libraries,
threading, and a large linear address space.
In my view this would be an absolutely ideal platform for Csound (not
to mention much other software). Csound would be able to run along
with its plugins and with LuaJIT not to mention fast JavaScript and
all capabilities of HTML5.
If wasm eventuates as envisioned, I think that could up being a really
big deal. Computing might become be a social utility without
proprietary gateways and obfuscations: as the W3C says "WebAssembly is
designed to maintain the versionless, feature-tested, and
backwards-compatible nature of the web." I wonder if ultimately HTML5
would not take over the upper layers of the operating system and much
of the software development toolchain.
I remain somewhat concerned about transparency and whether wasm will
really be open source. I suspect the four major browser vendors are
pretty determined to do things their way.
Perhaps one of us should consider getting a W3C account and joining
the WebAssembly Community Group in order to encourage the standard to
be suitable for audio and music in general, and Web Csound in
particular. Low latency, high-resolution, multi-channel, output and
input audio; MIDI; OSC; etc.
Regards,
Mike
-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com
On Wed, Mar 16, 2016 at 12:14 PM, Victor Lazzarini
wrote:
> yes, that’s probably where we’ll go next. I think, at the moment, it’s quite ready yet. The audio integration etc is probably not
> going to be there right away as well, so we will need to wait for that.
>
> ========================
> Dr Victor Lazzarini
> Dean of Arts, Celtic Studies and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 16 Mar 2016, at 09:43, Hlöðver Sigurðsson wrote:
>>
>> I've been hearing people around me getting excited about Webassembly coming out now. Is it compatible with Csound, can we now finally have a standard way of running csound in the browser that will work on all devices (in return "abandoning" emscripten and pnacl)?
>>
>> http://webassembly.github.io/
>>
>> Hlöðver
>> Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
> https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here |