[openbeos] Re: Javascript-capable Browser



>
> >I've been thinking for a while.  I've heard it said several times here
> >that a Java-script capable browser is KEY to an OS being used as a
> >person's primary desktop OS.  I know this is true in my case.
>
>Agreed.

Ditto. Without a Java-script capable browser you're back in Windows every 
half hour ... ewwww ...

>
> >I think it is in OpenBeOS's best interests to do whatever it takes to
> >get a GOOD javascript browser released with R1 that is rock solid.

Agree. Particularly with the "with R1" part. New users get their openBeOS 
CD, install it, fire it up, get on the internet ... everything good so far 
... then their favourite site uses javascript, so it doesn't work properly. 
Baaaad. You never get a second chance to make a first impression, and I fear 
that without a Java-script capable browser you run the risk of getting seen 
as a nice, fun OS that you can't actually use to do the stuff you need to 
do. Remember that?

> >I don't know which one that should be, it seems to me that whichever
> >browser is chosen, that we in OpenBeOS should make our highest priority
> >to either support the browser development, directly lend a hand, or
> >create a development team to assume the development on a browser to make
> >sure it makes release and is excellent quality.
> >
> >Thoughts?

Would it be possible to write something that different developers could 
modify for their browsers, so you avoid favouring one developer over the 
other? Need to be even-handed.


>I disagree here. I would very much support a browser effort. If it be Opera 
>(which I bought),
>a continuation of Net+, if it were licensed, or something else all 
>together, I think that it is a
>great idea.
>
>But. There is a limit to what we can wrap our heads around.
>Realistically, there would be nearly 0 benefit to having a web browser team 
>as part of OBOS,
>AS COMPARED TO having the same people on a different, unconnected team.

However you structure it, just so long as it comes out with R1, methinks.

More importantly, what we are talking about here is merely one instance of a 
more general issue (and IMHO an absolutely critical one), i.e.:

What is the goal of this project - is it to rewrite an OS, or is it to 
rewrite an OS _and_ try to ensure that people use it? IMHO, only the latter 
will ensure the long-term survival of openBeOS. If it _was_ just the 
technical excellence of the OS that ensured success, why did Be fall over in 
the first place?

The stated goals of the OpenBeOS project are:

1. "the re-creation, followed by the extension, of the BeOS."

and

2. "Why was OpenBeOS started? Simple: to keep the BeOS alive."

1. is a purely technical goal, whereas 2. includes 1. as its first priority 
but also implies the other things needed for a user/developer  community - 
certain apps, infrastructure, an effort to acquire enough users to make the 
whole thing viable, etc.

Some of these things will be somewhat removed from the OS per se, but will 
make a huge difference to user uptake. A javascript-capable browser is one. 
But to push the point, let me talk about pure "eye candy" - having something 
like BeTheme in the distro, with a whole bunch of really good-looking 
themes, will make a _big_ difference to user uptake. To most people on this 
list BeTheme is probably not a huge deal, but to your grandmother it is 
really, really cool. Another e.g. of this is the QING plugin in SoundPlay - 
whenever I put that on when we have people over I get a "that's cool!" 
reaction.

And yes - I did spend time working in marketing (6 years), though marketing 
is only _part_ of the "other stuff" needed. I've been thinking about the 
"other stuff" issue for a while. While the thoughts I've put down here are 
nowhere near as systematic as I would like, if people here can see some 
sense in what I'm saying, I am quite willing to contribute in this area.

Anton.

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

Other related posts: