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.
Thread beginning with comment 437707
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Forward thinking
by kaiwai on Sun 22nd Aug 2010 01:45 UTC in reply to "RE[4]: Forward thinking"
kaiwai
Member since:
2005-07-06

I believe they started off with the BSD libc, but switched to glibc for compatibility reasons (since BeOS had used glibc for its "libroot" support).

http://dev.haiku-os.org/browser/haiku/trunk/src/system/libroot/posi...

Recent discussion suggests that glibc may still be retained only for the BeOS compatibility (i.e. a gcc2-compiled set of libs will still remain optionally-installed for BeOS compatibility) while a non-GPL libc replacement will be grafted in moving forward.


Sounds awesome; I have to admit though, it is rather disappointing that they've removed the progress chart which used to track the 'completeness' of each API call or feature; is there some way to track how far along they are in terms of implementation? do they have a goal for the final R1 release or is it more a situation of plodding along and focusing on the quality rather than an arbitrary time table?

Reply Parent Score: 2

RE[6]: Forward thinking
by umccullough on Sun 22nd Aug 2010 05:49 in reply to "RE[5]: Forward thinking"
umccullough Member since:
2006-01-26

is there some way to track how far along they are in terms of implementation? do they have a goal for the final R1 release or is it more a situation of plodding along and focusing on the quality rather than an arbitrary time table?


I'd say it simply became too hard to track.

At this point, it's not so much "what's done, and what isn't", but rather: "What apps run, and for those that don't, do we really care?"

I'm not sure anyone really has a clear idea of what is incomplete these days. I know the media kit is still missing encoding support, but beyond that, the parts that are lacking BeOS R5 support are either few, or unimportant I guess.

These days, people are more interested in when Haiku will support their specific hardware, or support WiFi, etc.

As for when R1 might emerge... I couldn't answer that ;) There seems to be a desire for rock-solid quality before the core devs will sign off on that.

Edited 2010-08-22 05:52 UTC

Reply Parent Score: 2

RE[7]: Forward thinking
by koki on Sun 22nd Aug 2010 13:26 in reply to "RE[6]: Forward thinking"
koki Member since:
2005-10-17

The Haiku media kit already has encoding support. It was implemented last year by Stephan "Stippi" Assmus.

The development progress charts were cool and but pretty useless. The idea was nice, but the team leaders did not have the discipline to keep the charts up to date, so in the end they became nothing but make believe business, as in most cases they did not reflect reality at all. Good riddance.

Reply Parent Score: 1