Linked by Kaj-de-Vos on Thu 20th Dec 2012 00:22 UTC
Permalink for comment 546242
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2007-02-15
when i started the discussion by then it was with a good intention, because at that time stagnating and I didnt understand what was going on, and everybody was silent. Just later I understood, that already at this point it was already too late for syllable. In fact there would have been a little chance in that moment of the discussion. At that moment most devs except you, vanders and necroromancist.... where already not supporting you anymore.
You gave youself the title of "co-leader" (next to vanders), even nobody has elected you. Your work was mostly related to scripting and applying the patches of the others, and you stared to imagine that you are a great developer and need to decide the direction of syllable.
Kaj, i dont want to harm you feelings, but as a scripting guy, it's very unlikely that c++ devs, kernel devs, filesystem engineers,... will pop up to follow you and saying:"scripting guy, tell us what to do next."
Even if you can find "long term followers", they will be of about your own skill, or inferior. And with such a "team" of course you can't get anywhere.
The other strategy can be of course to borrow as much as possible from linux, but since syllable is quite buggy and misses a lot of "instrastructure".... the amount and quality of the ported software is (mathematically speaking) bounded.
related to pyro:
I must admit i tried to tell the people from pyro (syllable fork), that it has not much sense to fork a system like syllable that is not in clean compileable state, that is missing a lot of features, buggy, etc.... when they could have forked haiku, which has all goals of syllable (and from which syllable itself tries to copy, or to be compatible with), and which is in a much more advanced state beating syllable in every domain even at scripting (well, except perhaps at... wallpapers, syllable is better at this, since it seems they also put more effort in wallpapers than haiku).
But they insisted on syllable, and to me this behaviour seems like blind syllable-love.
Now kaj, finally, you are the king of syllable, the only problem is that the castle is broken and the servants are gone, and you need to live on credit and it's unsure for how long you can hide that the king is bankrupt.
I have no problem with syllable, but i would like to see real news about syllable and not this kind of fake news, because it reminds me that once, many years ago syllable the little os with a big future, and now it's clinically dead since years popping up with fake news.
If you dont have technical improvements to report, then instead of such fake news, i would really love to see honest interviews with vanders related to technical stuff related to syllable (e.g. he could explain how a native syllable driver differs from a linux one, etc.), related to his decission to step back from syllable. There is a lot of interesting information related to syllable/atheos/pyro that would make a nice read and from whoes history we all could learn something.