Syllable's Kristian Van Der Vliet Interview 123
Andreas Louca writes "OSNews.com has a nice interview with Syllable's Project Leader, Kristian Van Der Vliet. Syllable is one of the teams that raised off the ashes of AtheOS. They talk about the future of Syllable and the current status. "
It... (Score:2, Funny)
It only has one... somehow I don't think that's going to cut it. ;) THppppppppt.
Re:It... (Score:2)
Re:It... (Score:1)
Re:It... (Score:2)
Re:It... (Score:3, Funny)
2. Play Ogg files
I'm right, aren't I?
Re:It... (Score:2)
Re:It... (Score:2, Interesting)
Re:It... (Score:2)
Kristian Van Der Vliet (Score:5, Funny)
Re:huh? (Score:1, Informative)
The expression is a reference to the mythical Phoenix, which would periodically die and burst into flames, and a new Phoenix would be born among the ashes.
In this case, the implication is that AtheOS died in flames, but Syllable was born among the metaphorical "ashe
Re:They used khtml before apple. (Score:3, Interesting)
Re:They used khtml before apple. (Score:2)
Re:They used khtml before apple. (Score:2)
Re:They used khtml before apple. (Score:2)
However I do remember the big deal about "oh they're using KHTML and not gecko", etc.
I think that was just because folks expected them to use Gecko: Gecko seemed more mature, and they had hired one of the fellows working on Chimera, a Gecko browser for OS X. At first it seemed like an insult to Gecko, but that is in part because noone was really paying much attention to KHTML. So you still get points for using KHTML before Apple; but it doesn't seem so surprising that everyone made a big deal out of App
AtheOS is dead? (Score:3, Informative)
Wasn't AtheOS the OS that was all being done by that one guy and had the amiga-like GUI with the nice c++ API? If that's the one i'm thinking of, is this a big mark against the single-benevolent-dictator software development model that AtheOS was the shining example of, or a mark for because the project got so far before the guy wandered off for whatever reason?
Well, at the least, this explains why I suddenly stopped hearing about AtheOS after so much noise was made about it..
Does AtheOS's previous developer still use it on his home machine?
-super ugly ultraman
Re:AtheOS is dead? (Score:5, Informative)
Re:AtheOS is dead? (Score:3, Informative)
As the news [atheos.cx] says, his dev box broke down and hasn't been replaced (yet) 'cuz he bought an airplane. I think the site server is run at his employer's or something.
Phew (Score:5, Funny)
Re:Phew (Score:2)
In other news, world-class journalistChristiane Amanpour [cnn.com] has announced a new SourceForge project, AmanpourOS. It will include a realtime kernel, POSIX and Win32 compatability, a full suite of GNU tools, and of course a Journalling File System called CNNFS (CNNFS is Not aNother File System).
When asked how much code she had available on her project site presently, she replied "Code? Oh, I haven't written any code, really. All I did was get a sourceforge project up and secured an OSNews interview with Euge [osnews.com]
Why? (Score:4, Insightful)
This OS looks really cool, but I just want to know: years and years since LiteStep or AfterStep or Windowmaker or whatever the first attempt to make "a NextStep-like window manager", and the "open source community" still can't seem to produce a GUI that doesn't look exactly like a less-stylish version of NeXTStep.
I guess that isn't *bad*.. it's just funny.
Besides this, though.. I am firmly convinced that "open source" is going to go nowhere until the Community realizes that everyone except you absolutely HATES the way that Motif looks. No, saying "it has skins" is *never* an acceptable answer. If your product, out of the box, has that faux-3D, Motif/NextStep/Netscape 4 look to it *anywhere*, people will not want to use it.
Re:Why? (Score:1)
HOWEVER, let's remember that most NeXT boxes were black and white... maybe they couldn't afford the license fees for color?
Motif looks like a windows 3.0 knockoff, but designed by a committee.
Re:Why? (Score:3, Informative)
Plenty of newer NeXT boxes and white hardware running NeXTSTEP or OpenStep were color. Even for copies of NS/OS on b/w machines, NeXT still paid the Pantone color licenses. NeXT was a platform that did many things very well. And when your display is greyscale, you better have accurate colors when you're going to be printing. Heck, back then, a Pantone license was a good idea on a color monitor. Apple's ColorSync existed before
Re:Why? (Score:3, Informative)
Re:Why? (Score:1)
Re:Why? (Score:1)
NextStep has nothing to do with Motif has nothing to do with this. Off topic.
Re:Why? (Score:3, Informative)
That the looks aren't all that much is another thing, though. But to just discuss taste -- I guess the users must decide here.
Commodity Hardware (Score:5, Interesting)
Re:Commodity Hardware (Score:2, Interesting)
If the hardware becomes more com
Re:Commodity Hardware (Score:2)
And as for coding in VLIW assembly language complicated enough to code an OS: an OS usually is mostly coded in C, so it isn't really a problem.
And if the assembly language is too complicated, and C too rigid for some parts, nothing prevents the use of some kind of "in-between" language: a C extended with all the operation offered by the CPU for example.
Re:Commodity Hardware (Score:2, Interesting)
Yes, but as hardware becomes increasingly complex, drivers, libraries and toolkits will be equally more difficult to write. Even more so if you don't have reference material for the hardware you are writing drivers for, as most OS projects don't have today.
It is not like standardized drivers appear magically for an OS, except a few select ones with critical mass.
Re:Commodity Hardware (Score:3, Insightful)
That's the most ridiculous thing I've heard in a while. Do you think that hardware interfaces haven't been increasing in complexity until USB came out?
RTFA. He's talking about writing operating systems from scratch. Who do you think writes the abstraction layers?
The point is that as each new hardware interface is developed, it is significantly more complex than the preceding one, and it becomes harder and harder for a hobbyist programmer to comprehend it.
Re:Commodity Hardware (Score:4, Informative)
Why? At the very least, developers can use freely code from the BSDs with no strings attached. If the OS developers are planning on GPLing their code, they can pull code directly from Linux.
If using code from either of those OS's is unacceptable (say, the new OS is being written in a different language), the developers could actually read the BSD or Linux routines and use that as a starting point.
Re:Commodity Hardware (Score:1, Interesting)
I think there are many people who believe that if the OSS community wants to make something, nothing will really stop it.
Looking over
Look at
In a word: (Score:1)
In another word: POSIX.
Re:In a word: (Score:2)
So what the hell does that have to do with supporting supposedly more difficult to support devices like USB? (Okay, yes, it's harder to support by far, because you can't just do IN and OUT. But as others have said, you can "steal" code from BSD.)
Re:Commodity Hardware (Score:3, Interesting)
This is unlikely to be the case. Should it get to the point where the hardware is too many and too complicated for everybody to program for, you'll find generic interfaces to the hardware being implemented in generic assembly languages like table assembly [penguin.cz].
Or perhaps firmware will develop further to ease driver creation.
There are many areas in which layers can develop to keep developing drivers possible for mortals. The
Sounds cool, but... (Score:5, Insightful)
For Open Source and Free Software to succeed people need to stop making "yet another peice of software written from scratch". The strength of having the source is that you can modify it for your own use (like syllable is doing with the GNU tool chain) and not have to re-invent the wheel. The argument of "what's out there isn't good enough" doesn't fly either. You have the source to fix it and make it better!
While this seems like a cool project, it is taking away developers who could be adding the same great features and abilities to our current systems. Then again, maybe I don't understand what they are trying to do.
Re:Sounds cool, but... (Score:4, Insightful)
What's the fun in that?
Re:Sounds cool, but... (Score:5, Insightful)
For Open Source and Free Software to succeed people need to stop making "yet another peice of software written from scratch". The strength of having the source is that you can modify it for your own use (like syllable is doing with the GNU tool chain) and not have to re-invent the wheel.
So in other words, Linus working on his own operating system kernel was just taking good developers away from HURD, right?
If we follow your logic, we'll be stuck with Linux and BSD forever. Not that Linux and BSD aren't great, but they are not perfect, and at some point "making them better" won't be enough anymore. You need to have constant experimentation with OSes or you'll never know what's possible (and you'll never replace all those OS programmers with a new generation).
Re:Sounds cool, but... (Score:2)
Re:Sounds cool, but... (Score:1)
Just because they "could" be working on linux doesn't mean they "would" be, if not for Syllable.
Re:Sounds cool, but... (Score:2)
Re:Sounds cool, but... (Score:5, Insightful)
Well I am one of the developers from Syllable (Syllable-Net team leader to be exact) so maybe I can answer your question.
The argument of "what's out there isn't good enough" doesn't fly either. You have the source to fix it and make it better!
Have you ever played with the linux internals? Or hacked on X or KDE? If you have, you know its a mess. Syllable is a consistent system built on modern ideas. We don't have 20 years of cruft to fight with everytime we need to make a change or add a feature. This alone is worth the effort.
Now most importantly: Our main developers code on Syllable because its fun. I have a blast throwing ideas back and forth between Vanders, Rick, Kaj, and all the others. If someone has a problem with some specific widget (recently the tab issue in our terminal), we work together to fix it. I don't think any of us are working on this to get rich. For the most part its also the whole "scratch an itch" philosophy. Just because we work on this OS, doesn't mean we'd work on another one. Thats like saying that just because I pirated a copy of Windows that I cost MS $200 because I would of bought it anyway. The world doesn't work like that.
We have a great community, a great project manager in Vanders and great developers. All of us keep our eyes on the user's needs, not on what we as developers want. As time goes on and more infrastructure is laid down, you'll see Syllable become more mature. Simple things that can be a hassle on Linux (gui consistancy, simple application notification through a central Registra, etc) will be in place.
Anyway, don't give up on Syllable yet. In the future it will be much different from Linux, BSD, Windows or anything else. Remember we're not even a year old yet (although AtheOS has been around for a while).
Re:Sounds cool, but... (Score:2)
Wasn't that the whole point of BeOS? To make a unix-like system that was great for multimedia and not full of cruft from the last 30 years of unix development.
If you're starting your own project just because you reject l
Re:Sounds cool, but... (Score:1)
So its the other way around I'm afraid
Re:Sounds cool, but... (Score:3, Interesting)
Linux internals are very messy. BSD is a lot cleaner, clean enough that researchers chop it up for use in experimental OSes. Why not start from something that works and has solid hardware support? Was it just more fun to do it from scratch or was there a design reson why reworking an existing system or just using large chunks of code wasn't an option?
I'm no UI expert but the code for X, KDE,
Re:Sounds cool, but... (Score:4, Informative)
However, once Kurt abandoned AtheOS it seemed a shame to waste such a promising system.
From my own experience, I'm the manager of ABrowse our web browser. ABrowse is based off of KHTML which is a nightmare. I'm currently thinking of some drastic changes because I can't keep up with porting the new versions. I don't want to write a html render engine from scratch, but I am seriously thinking of stripping just about all the none render code out of it. So yeah, there is a point where sometimes it is better to start from scratch.
Well we don't have remote displays yet. However it is rather trivial to add that. As for right now, there are no great advantages over Linux or any of the BSDs. The the other hand, all of our developers listen to the users so any input is appreciated and noted.
We support just about everything that is posix compliant, so that pretty much covers the GNU tools.
As for building a system on top of already existant kernel, well thats what cosmoe is. Its the atheos api tuned to run beos apps, running on a linux kernel. Its kind of a kludge if you ask me. Our kernel while rather immature has some nice features. Its SMP friendly and is completely pre-emptive, the former not done by *BSD until recently and the latter being something Linux doesn't truly have.
Re:Sounds cool, but... (Score:2)
I'm currently thinking of some drastic changes because I can't keep up with porting the new versions.
I think this is exactly the thing which most of the people saying "why didn't you use the code from project Y?" don't understand. If you use someone elses code you have to maintain a fork of that code. That means syncing with new versions to fix bugs etc. Now this will not be trivial since it is someone elses code, and probably
Re:Sounds cool, but... (Score:2)
I hope these guys can to a better job, but I am not at all "sure" of it. The people who work on X, KDE and GNOME aren't newbies who just learned C yesterday. They are excellent developers. I've looked at the code for all three projects, and it is all of high quality.
There is of course, some cruft in all three of those projects. But that cruft
Re:Sounds cool, but... (Score:4, Insightful)
Yeah, I know Linux and BSD are great and all, but who the hell are you to judge what these guys should or shouldn't be spending their time on? Maybe you've read too many articles about the RIAA/MPAA, "For every CD copied, we lose a sale," -- "For every developer working on non-Linux systems, we lose a Linux developer." I'm afraid it doesn't work like that.
I'm not going to bother arguing whether your assertation that they could use a Linux kernel is valid or not, because it's completely irrelevant. If the developers wanted to use Linux, they would. They chose not to. Do you imagine the thought just never crossed their mind?
We may all be a team in the sense that most open source developers have similar goals, but not in the sense that you can refer to "our current systems" in any meaningful context.
Re:Sounds cool, but... (Score:2)
Re:Sounds cool, but... (Score:2, Interesting)
Re:Sounds cool, but... (Score:3, Informative)
While a large part of the kernel has been written from scratch, there is nothing wrong with that. For the effort Kurt put into writing it, we have a kernel with a kernel space ELF loader and runtime linker, written with SMP support from day one, with an efficient micro kernel IPC mechanism. At the same time, he used code from Linux were it was beneficial. The allocator is essentially from Linux for example.
The terminal emulator (ATerm)
Re:Sounds cool, but... (Score:1)
Re:Sounds cool, but... (Score:2, Informative)
Re:Sounds cool, but... (Score:3, Informative)
he used code from Linux were it was beneficial. The allocator is essentially from Linux for example.
and the design for Linux's slab allocator ripped off Solaris (see "UNIX Internals: The New Frontiers" by Uresh Vahalia).
Re:Sounds cool, but... (Score:2)
Quick show of hands please: How many people have tried to "fix" the X Window System? [x.org]
Many [catalog.com] people [cbbrowne.com] feel [slashdot.org] that X11 is a bloated, unmaintainable hack. It is absolutely full of cruft.
My hope is that this effort gains enough of a foothold that it attracts developers that can put a WINE-like layer on it to translate KDE or QT calls. Then, as people migrate from lower-level toolkit lib
"Losses" in the cornfield (Score:2)
Now, here's someone who is motivated to learn how to write a "better" OS. And it's his time (and the others corresponding on the project) so how does this "take away" anything?
Consider: the entertainment industry "loses" Billions of dollars each year to people who don't buy music and don't visit
Testing, testing, testing (Score:3, Funny)
Why, then, is Syllable an ugly looking, instable OS?
Oh, he explains that later on:
"We are very poor at testing before we release things, [...]"
So good luck with your OS, Mr. Van Der Vliet.
Re:Testing, testing, testing (Score:4, Informative)
Because Syllable is a development, alpha version. Ugly can and will be fixed in time. We inherited the GUI from AtheOS and thats how it looks. Why spend time and effort changing the look of the GUI when the GUI isn't complete?
Instability is inherent in the development process. Yes, we are very poor at testing before release, but that is because it is alpha quality. I don't have a release schedule, and there certainly are not enough users to form a FreeBSD style release team.
Release testing generally consists of me trying out common actions for about half an hour after a build. As we finalise and stablise API's we can build automated test harnesses and formalise a testing plan for new releases.
Re:Testing, testing, testing (Score:2)
Screenshots (Score:2)
50% troll,
50% insightful.
Honestly...if an OS looks THAT similar to the Linux, OSX, and Windows, can it really offer enough to justify its existence to anyone other than its developers?
Give me something really new...Plan9 new...for a desktop OS, and I'll pay attention.
Re:Screenshots (Score:2)
Umm, no, that's not how we review an os. Maybe if we're on crack.
The "look" is themeable (like everyone else). But if we use your conclusion, then Windows with litestep is THE SAME as linux.
Sheesh.
Re:Screenshots (Score:2)
If an OS behaves the same as e.g. Linux but is different internally, then yes, it IS "the same" as Linux. Look & feel is a big part of this. The internal differences only start to be interesting if you're a developer, or sometimes (when the API is the same) even only if you are into a specialized markted, like embedded or real-time software.
For some of us, an ideal OS is one with an ideal user interaction. And sometimes when I ha
Re:Screenshots (Score:2)
a) has buttons
b) has windows
c) can draw them on a screen.
Syllable offers a lot more than this, but the first poster's point was that nobody cares. That is very frustrating from a developer's standpoint, since you put a lot of effort into a kernel, display server, or filesystem, but cannot expect people to read the article and find out about this since there are pictures that look a lot like linux, or windows, or foo-os.
I maintain my sheesh.
Re:Screenshots (Score:1)
50% boring,
50% interesting.
Honestly... if you look THAT similar to lots of other people, can you really offer enough to justify your existence to anyone other than your parents?
Give me something really new... Ossie Osbourne new... for a maturing person, and I'll pay attention.
Hmm. (Score:3, Insightful)
I would love it if all the 'hobby' oses, combined forces and worked on one thing, like openBeos (soon to be renamed ;)
I am not biased, either.
OpenBeos High School Football RULEZ!!!
Re:Hmm. (Score:5, Insightful)
Syllable does not use X or the linux kernel - it uses it's own SMP and fully preemptable kernel, it's own 64 bit filesyste (with attributes). and it's own alpha-channal-aware display server. It uses a C++ API that is similar to beos. And it is completely free.
In the end, we expect syllable to be a os that is nice to work with - easy to use, easy to program. Since it does not use X as a display server, It provides its own toolkit. This will help applications maintain one look and feel. Although most posix apps can be ported (a la
There are other hobby OSes. Syllable just happens to be reasonably far along (thanks to Kurt Skauen) and seems to have a lot of momentum (thanks to Vanders.)
Re:Hmm. (Score:3, Informative)
So it is a lot like OpenBeOS in that respect, except that Syllable has much more development behind it and works now. We are also not trying to clone BeOS API by API; if it suits our purpose we can and will
How do you maintain order and good design? (Score:4, Insightful)
In the last few days, there has been an explosion of activity on the mailing list, and maybe it's just my pessimistic self, but I think the focus has shifted away from clean design to features. If this trend continues, and Syllable falls victim to featuritis and coding without the big picture in mind, it'll simply end up as yet another operating system.
Do you agree that this is a problem? If so, do you think it will be possible to keep this trend in check or even reverse it?
Re:How do you maintain order and good design? (Score:1)
The key point in my mind that it was under the control of a single developer. Since it was his creation he had ultimate control. Even though a fork could be created it would be unlikely as the fork would be competing against the official code.
With the official c
Re:How do you maintain order and good design? (Score:2, Interesting)
Re:Amazing that Eugenia's dual Celeron box ... (Score:1)
Do you want her?
Syllable overview (Score:2, Informative)
If you are interested in Syllable, here is an overview of Syllable 0.4.4 [beeblebrox.net].
Re:What does Syllable offer that Linux doesn't? (Score:2)
It's you. Because you're writing under AC and I hate it very much! It's kinda lifeless, too.
So please take care of the problem. OKAY??????
BYE!
Re:What does Syllable offer that Linux doesn't? (Score:1)