On Mon, Jun 30, 2014 at 11:58 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
[...]
And what's the point of running a concert hall
reverb in a web
browser ?
[...]
I don't know what *this* particular thing is all about, but generally
speaking, the main point of running stuff in the browser is that the
exact same build works on any operating system, any CPU and (in a
perfect world) any non-ancient standards compliant browser. It's a
platform where an easy-to-optimize subset of JavaScript is your target
CPU architecture, and the browser APIs serve as your interface to the
hardware and the outside world.
It's potentially relevant to pretty much anything people actually want
to use on a computer or similar device...
As to Google and all that, it's no different from distributing
binaries for any other platform. These binaries just happen to run on
most of them out of the box, requiring no extra VMs, guest OSes,
emulators or anything. If you don't like any random company making
money off of it, you use a license that doesn't allow that. If you
have nightmares about piracy, you're still free to fuck your paying
customers over with DRM that the freeloaders will be happily unaware
of. Nothing new there.
You just reach many more users with less effort. I don't see any (new)
problems here, really.
But, perspectives... I develop games and stuff - not embedded realtime
applic... Actually, I do that too. :-)
--
//David Olofson - Consultant, Developer, Artist, Open Source Advocate
.--- Games, examples, libraries, scripting, sound, music, graphics ---.
|
http://consulting.olofson.net http://olofsonarcade.com |
'---------------------------------------------------------------------'