Linked by Kaj de Vos on Tue 5th Jul 2011 17:54 UTC
Syllable, AtheOS Red is a new programming language inspired by REBOL, but compiled and open source. The language is currently being bootstrapped by first implementing a lower level dialect, in which the high level, dynamic language will be written. This C class dialect for systems programming, Red/System, has reached beta status after only half a year of development. It now supports using dynamic libraries on Syllable. Also, a new version of Syllable Desktop's FTP client, Transferrer, was released (screenshot accessing Syllable Server).
Thread beginning with comment 480007
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by cipri
by FreeGamer on Thu 7th Jul 2011 17:52 UTC in reply to "Comment by cipri"
FreeGamer
Member since:
2007-04-13

Syllable is open source, under the GPL. If you are so unhappy with its current direction, fork it.

The Syllable developers [active or not], as people who contribute their spare time, blood, sweat, and tears and do so voluntarily, owe you nothing. Not support, not any answers about anything, not explanations. Nothing. You have not paid them, exchanged contracts, or done anything other than continuously spread hate on this website (and wherever else you stalk Syllable news posts).

Stop being a childish little troll. Help out (contribute), help yourself (fork), or help the world (by shutting up).

Reply Parent Score: 2

RE[2]: Comment by cipri
by cipri on Thu 7th Jul 2011 19:01 in reply to "RE: Comment by cipri"
cipri Member since:
2007-02-15

Syllable is open source, under the GPL. If you are so unhappy with its current direction, fork it.

You have not paid them, exchanged contracts, or done anything other than continuously spread hate on this website


1)
I dont want to become personally, but do you have problems with understand the meaning of a question?
I never said that somebody owes me something. If you are not able to understand, you should consult an mathematician, who will logically analize my sentences and tell you the content.

2) Do you have as many years, as many thousands of c++ code i wrote related to syllable? Just two programs that I published have been altogether about 10.000 lines of c++ code. My other applications (sever + client (gui) imitating AltMe, PDF-Viewer based on poppler, a software for translating text imitating the software Lingoes) which I didnt publish, but who have been seen by some syllable devs, are also about more than 20.000 lines of code. The code that I wrote for testing the syllable API is also considerable.
I guess I'm one of the few, how knows the syllable api in detail, all this didn't come over night, it was a lot of time that i spent with syllable. Especially since the syllable api is poorly documented and it has a lot of bugs, and you need to try a lot of hacks to make it work like it should.
Write yourself at least 30.000 lines of code related to syllable like I did, and then come again and tell me that this is nothing.

Help out (contribute), help yourself (fork), or help the world (by shutting up).

As I said before, nobody with a clear mind would spend too much time with syllable. I guess that's also Vanders reason, why he even hasnt written a comment in the last year on the syllable forum, not to talk about writing code.
I guess, you should contribute to syllable if you think it's worth. If you are not able to write c++ code, you can learn it very easy and fast, I encourage you. I still have a clear overview of the current syllable development (and it's internal situation), when you will be contributing I will notice it, and I will be the first to congratulate you. So hurry up contributing.

If you are so unhappy with its current direction, fork it.

Did i say that I'm unhappy with the current direction? No, I didnt say that. I just said that it's pathetic to write write in an osnews article that you fixed some bugs of a very basic application in the last 2-3 years. You must be very desperated if you need to notice that kind of progress in an osnews article.

If you will read again my comments, you will see that somebody owes me something (answered, etc.). Just try again, and read carefully. If you still have problems, consult an mathematician, for example Anthony, he can help you for sure.

Reply Parent Score: 1

RE[2]: almost a fork (2)
by anonymkous8756 on Sat 9th Jul 2011 12:24 in reply to "RE: Comment by cipri"
anonymkous8756 Member since:
2011-06-19

As i said in other thread,
No new code, no fork, just more documentation and a clean sh build script without ruby, rebol crap (nothing personal about rebol, just want a cleaner compile way)

I'm trying to solve some problems, there exist more than 240 makefiles, the API is poorly documented, the kernel, also has a poor documentation. If someone wants to clean a little all that mess, i've created a google code project with my effort in to make a better documentation (really, i have no hope, but a lot of energy)

http://code.google.com/p/wave-os/

The very first i want to do is to update the building script, create.sh, because i not just want to build the whole system in a straightforward way, but also to assemble the whole iso and then burn first a copy of the new iso and then an installation cd.

Reply Parent Score: 1

RE[3]: almost a fork (2)
by cipri on Sat 9th Jul 2011 13:22 in reply to "RE[2]: almost a fork (2)"
cipri Member since:
2007-02-15

As i said in other thread,
No new code, no fork, just more documentation and a clean sh build script without ruby, rebol crap (nothing personal about rebol, just want a cleaner compile way)


I dont want to say something bad, but you really waste your time and effort. Syllable is as good as dead. On top of that, it has a lot of bugs and very deep problems. Haiku is beating syllable in all domains (posix, hardware, software,..). Now recently Haiku got a payed full time developer, and also just recently somebody donated 10.000 dollar.
I know kaj told you a lot of lies related to haiku, but I can really can give you the advice not so spend your time with syllable.
Syllable was already declared by Thom (osnews owner) to be dead. And he had a good appreciation, even he didnt know the "internals".

There are now more than 2 years, since the last release, and a new release is even not in sight. Most developers are gone, even the leader disappeared. The last development build is nearly 2 years old too. Taking all that facts together, your "alarm bells" don't ring? What can you expect?
Syllable will remain "quasi-dead", and I dont expect much more than some osnews articles which say: "script xy is working on syllable correctly", "a new boot-option was added to the menu", "keyboard navigation was enabled", "some sdl games have been build by a user", "some bugs in transferrer were fixed".
That's what I expect from syllable.

Edited 2011-07-09 13:34 UTC

Reply Parent Score: 1

RE[3]: almost a fork (2)
by Vanders on Sat 9th Jul 2011 17:44 in reply to "RE[2]: almost a fork (2)"
Vanders Member since:
2005-07-06

No new code, no fork, just more documentation and a clean sh build script without ruby, rebol crap (nothing personal about rebol, just want a cleaner compile way)


The build system for Syllable (Builder) is actually pretty damn good.

I'm trying to solve some problems, there exist more than 240 makefiles


Well, yes, there will be. Building an entire OS requires building a lot of components. Note that the ancient recursive-Makefile based build system was replaced long, long ago with Builder.

The very first i want to do is to update the building script, create.sh, because i not just want to build the whole system in a straightforward way, but also to assemble the whole iso and then burn first a copy of the new iso and then an installation cd.


I'm not sure if you're aware of the existing build scripts: http://syllable.cvs.sourceforge.net/viewvc/syllable/syllable/system... ? You install Syllable, run start.sh to install the additional build components and then build everything by running start.sh. Once the build is complete you can use build-cd.sh, build-vm.sh or build-upgrade.sh scripts to create installable media. It's really pretty simple.

Reply Parent Score: 2