I'm thinking about possibly abandonning kde development (would still use KDE while in linux/X) and starting to concentrate mostly on the development of Syllable instead. Syllable is ayoung project, and I think I'll be able to learn more (and contribute more) in this project than I'm able to in KDE. The entire codebase for the Syllable OS is less than that of KDE, which is just the GUI in linux.
To that end, I think my KDE-OS project will be completely and entirely shelved. On the flip side, developing on syllable will give me an opportunity to develop REX as an alternative front end to a system that already fits all the requirements for the backend. Also, I think by abandonning KDE development, I will spend less time idling on irc -- since there's only 7 people in the #syllable channel *grins*
I've been following syllable for a while -- since it was known as AtheOS -- and am subscribed and contributing (a little) to the mailing list. My first project once I get it installed will be to port Python over to the OS. This will allow me to become familiar with the workings of the OS, as well as providing a
sizable contribution to the still small community.
Python's core should be fairly easy to move over, since it's quite portable (runs on win, mac, unix already). Then I just need to get the individual modules ported over to work with the OS... like sys and os, etc.
Anyway, I'll install syllable tomorrow -- found a working floppy drive to boot from. Will take the next week (on and off) to get familiar with the system. Once Python is ported over, I'll try porting mod_python (since apache was already ported) and then try this blog on that system for developement purposes.
I won't dump my slackware install that I'm on right now for quite a while. It's rock solid, and I can actually get work done in it. I'll see if I can use vmware to get the best of both worlds for a while. If necessary, I'll purchase vmware.
Anyway, until next time, be safe
- Log in to post comments