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 437707
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"
Member since:

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).

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