« Return to Thread: building csound into Chrome OS
Re: Re: Re: Re: Re: building csound into Chrome OS
by Brian Redfern-2
::
Rate this Message:
Well if the OLPC can have both python and csound together I don't know
why they couldn't be ported to the Chrome OS. But since its
essentially vaporware at the moment there's no way to know until a
developer edition gets open sourced, which may not be for another
year.
The main point is that they need to look at Sugar if they want to beat
MS. The reason why Windows is popular on netbooks is not just because
of the familiarity. Its that you have to be a hacker to put a usable
OS on a netbook. People don't just want to be consumers, a lot of
people would like to record sound or edit images. For Chrome to really
take on MS it has to enable creative computing. With windows XP on a
netbook or windows 7 you might not be running adobe photoshop, but you
could run Inkscape for windows or audacity for windows. The mistake
with the EEEPc version of Linux is that it is too limited and too hard
for ordinary people to do creative tasks.
Sugar on my OLPC is really slow, but it does enable me to write csound
music on a netbook. There's no reason why Chrome OS couldn't enable
creative computing, but there is an assumption on the part of creators
of things like Mobilelin, Chrome OS, etc... that ordinary people just
want to surf the web and consume data and maybe just want to only edit
office documents.
It might be possible to take something like Chrome OS and tweek it for
a multimedia appliance as some people have done with 64Studio.
On Wed, Jul 8, 2009 at 8:30 PM, David Akbari<dakbari@...> wrote:
> Possible, but not practical.
>
> Currently it seems that Csound and Python are too inseparably
> intertwined to make this practical, with the current build system.
>
> Your best bet with their Chrome OS is to make use of the online Csound
> rendering capability that has been graciously kept alive by John
> ffitch.
>
> http://dream.cs.bath.ac.uk/netcsound/
>
>
>
> -David
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"
why they couldn't be ported to the Chrome OS. But since its
essentially vaporware at the moment there's no way to know until a
developer edition gets open sourced, which may not be for another
year.
The main point is that they need to look at Sugar if they want to beat
MS. The reason why Windows is popular on netbooks is not just because
of the familiarity. Its that you have to be a hacker to put a usable
OS on a netbook. People don't just want to be consumers, a lot of
people would like to record sound or edit images. For Chrome to really
take on MS it has to enable creative computing. With windows XP on a
netbook or windows 7 you might not be running adobe photoshop, but you
could run Inkscape for windows or audacity for windows. The mistake
with the EEEPc version of Linux is that it is too limited and too hard
for ordinary people to do creative tasks.
Sugar on my OLPC is really slow, but it does enable me to write csound
music on a netbook. There's no reason why Chrome OS couldn't enable
creative computing, but there is an assumption on the part of creators
of things like Mobilelin, Chrome OS, etc... that ordinary people just
want to surf the web and consume data and maybe just want to only edit
office documents.
It might be possible to take something like Chrome OS and tweek it for
a multimedia appliance as some people have done with 64Studio.
On Wed, Jul 8, 2009 at 8:30 PM, David Akbari<dakbari@...> wrote:
> Possible, but not practical.
>
> Currently it seems that Csound and Python are too inseparably
> intertwined to make this practical, with the current build system.
>
> Your best bet with their Chrome OS is to make use of the online Csound
> rendering capability that has been graciously kept alive by John
> ffitch.
>
> http://dream.cs.bath.ac.uk/netcsound/
>
>
>
> -David
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"
« Return to Thread: building csound into Chrome OS
| Free embeddable forum powered by Nabble | Forum Help |
