Linked by Thom Holwerda on Fri 20th Aug 2010 21:40 UTC, submitted by koki
BeOS & Derivatives This summer, too, the Haikuproject is part of the Google Summer of Code event. One of the more interesting projects is the Services Kit (draft document!) by Christophe "Shusui" Huriaux, which is an API to facilitate the creation of native web-enabled programs using standard web protocols and data exchange mechanisms.
Permalink for comment 437704
To read all comments associated with this story, please click here.
RE[2]: Strain
by StephenBeDoper on Sat 21st Aug 2010 23:09 UTC in reply to "RE: Strain"
Member since:

I have to agree here: I only tried some trial version of BeOS years and years back and never used it for more than a few minutes so I lack the feelings of nostalgia. With the rose-colored shades of nostalgia missing I can only say that Haiku looks plain hideous to my eyes.

Yes, technology-wise it's got enormous amounts of potential and I can bet my ass that it's going to be a strong contender for certain things in the future, but if they wish to make it attractive for people without the rose-colored shades they really need to work on the looks.

I don't think that nostalgia is the sole (or even primary) driving force behind retaining the BeOS visual appearance in Haiku. Minimalism was always one of the main design (and philosophical) goals behind the OS - a minimalist, understated interface is consistent with that.

Of course, aesthetic preferences are just about the most subjective & widely-varying opinions that people can have. Even leaving aside nostalgia, I find that the mix of subtle/understated UI & clean but slightly-cartoony graphics is easier on my eyes than just about any other UI I've used.

To me, that says that the visual designers paid close attention to detail - but they also had the restraint to avoid going completely overboard with gratuitous visual effects (as opposed to effects that serve a useful purposes, E.g. to enhance usability by giving better visual feedback).

And I fear that's not going happen; given how many of the core developers are die-hard BeOS-fans they will not want to 'tarnish' it with some fancy effects or more modern looks.

Actually, there's been significant discussion among Haiku developers about visual changes to the OS - just not for R1. E.g. there's a "Glass Elevator" sub-project that's been around almost since Haiku's inception, with the goal of more long term, "forward looking" changes after the immediate goals of R1 are met:

And there already have been a number of visual changes to Haiku that, while subtle, are immediately-obvious to any long-time BeOS users. And unlike much of what I saw of ZETA, the changes have all been for the better (at least to my eyes).

There is a general perception that, because they're recreating an "old" OS, they must be die-hards who are clinging to the past, etc. But I don't think that the age of the OS is very useful indicator on its own - for one, in many ways BeOS was quite advanced for its time and had features that have only recently become common in mainstream OSes (IIRC, "future-proofing" the OS was one of Be's goals). And every indication I've seen is that that the Haiku devs are entirely realistic about changes that the OS will need if it's going to have any viable future.

Reply Parent Score: 8