Post a Comment
Really good to see Syllable progressing nicely!
I was particularly interested to see them include Orca as the main scripting language. Good on them for daring to be a bit different!
Orca (for those who haven't heard of it) is an open-source "work-alike" of the Rebol programming language. Orca and Rebol look (to me) like an interesting blend of Forth and Python. Take the concise nature of Forth and add the user-friendliness of Python and you might end up with something like Orca / Rebol.
Orca is still in its early days, but shows good potential. Rebol itself packs a *massive* amount of power into a very small size, and hopefully Orca can do the same.
Edited 2007-12-14 23:18
The screenshot shows Syllable Server running in Bochs on a Syllable Desktop system. In the installation and usage instructions it says "- Most notably, Syllable Server doesn't have the graphical environment from Syllable Desktop yet." IIRC, they intend to implement their GUI system without using X.org, but I don't think it's ready yet.
So, anyone has any idea of what parts of Syllable are in fact running over the Linux kernel? The post at syllable.org only talks about Linux packages.
And yes, IIRC, the GUI won't use X but the frame buffer.
From what I can tell it's still pretty close to a basic Linux system. The tree under usr/ has been changed significantly (each package gets its own directory, with its own subdirectories for bin/ lib/ documentation/ and so on).
I haven't spent much time with the 0.2 release yet, but I will tomorrow. If I find anything that's definitely from Syllable Desktop, I'll report back.
Sorry I keep asking questions, I don't really have time to give it myself a try:
Maybe I got it wrong, but that means that, for example, two binaries that need the same libX.so will have each one a copy of the lib? If that's the case well... ugh
Maybe I got it wrong, but that means that, for example, two binaries that need the same libX.so will have each one a copy of the lib? If that's the case well... ugh
As long as the basic system libraries cover all typically required functionality, only a few apps should need custom libraries. It seems to work well enough on OSX.
I'm all for it if it prevents problems like the libexpat fiasco a few months ago on Gentoo.
We can do both. The next release of Desktop should be ready soon (I'm testing and fixing the last development build right now, in fact).
Server will start to become really interesting once we get the appserver running on it and start to integrate Server & Desktop together.




