Linked by Thom Holwerda on Sun 23rd Dec 2007 21:11 UTC, submitted by Kaj de Vos
Syllable, AtheOS The Syllable project has published the source code for Syllable Server. The code to build Syllable is maintained in Builder, the build system. There is a main repository of build specifications and overlays for Syllable Desktop and Syllable Server. The code for Server is now completely published in the source repository. A package of Builder (11 MB) for Syllable Server has been released that corresponds to Syllable Server 0.2 with a few fixes. The procedure to build Syllable Server will be the subject of an article in a future Syllable Newsletter.
Thread beginning with comment 293020
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: syllable desktop
by SomeGuy on Mon 24th Dec 2007 19:17 UTC in reply to "syllable desktop"
SomeGuy
Member since:
2006-03-20

The xcb library is also not a soulution and is not actively developed.

Wrong on both counts.
1) XCB is transparently threadsafe. Now that it exists, there's nothing from making toolkits that are
completely thread-safe and async.
2) XCB is actively developed, and is actually now the base for Xlib.

for example posix message queues instead of dbus

Have you ever looked at d-bus? It doesn't even vaguely resemble posix message queues.

1) DBus is strongly typed. I can look at a dbus message, and see what "object" in the process it's
directed at. I can look at the types of arguments and the methdods. Etc.
Posix message queues are closer to raw sockets than to dbus.

or implement fam as a library and not as a daemon which just wastes resident memory

Because having a daemon to handle the kernel's job AND a library to interact with the daemon is so much better. Right.

Sorry, but even though inotify isn't all that great, I'd rather have a thin wrapper library around it than a daemon, and a thin wrapper library around the daemon.

Edited 2007-12-24 19:17

Reply Parent Score: 4