So let's see... Syllable was great. I was worthless. All the devs left because worthless me was somehow able to chase them away. The devs were united in their disgust of me, so they forked Syllable into Pyro. Seeing that only worthless me was subtracted from the Syllable project, Pyro went on to become a great success and conquer the world.

Now, you're getting ahead of your self. OS development is hard work. You'd already know this had you actually done any. We'll worry about being a great success & taking over the world AFTER we hammer this code into shape. When that's done, maybe we'll become a huge success, but there's a lot of hard work between then & now. You & I (plus a lot of other people) intimately know that you were a huge part in the neglect of the codebase having features. It's hard to understand why someone who wasn't doing any of the coding had so much 'NO' power concerning certain things. You can only use that word so many times before people stop doing work. It's clear from your attitude & behavior that you have absolutely ZERO leadership skills. However, all of that is besides the point. Instead of trying to push the focus of failure towards us, maybe you should work on your OS.

Dee, you're in a worse state than I thought. You still don't get it. You're not getting Pyro to work because you tried to delete all my hard work from it. The fact that you simply deny my work tells a story in itself.

All these years you have been claiming that our decisions to use Linux and REBOL lead to no being said to native Syllable work, but despite my repeated asking you have failed to come up with even one actual example. Maybe you can give one now?

Dee, you're in a worse state than I thought. You still don't get it. You're not getting Pyro to work because you tried to delete all my hard work from it. The fact that you simply deny my work tells a story in itself.

All these years you have been claiming that our decisions to use Linux and REBOL lead to no being said to native Syllable work, but despite my repeated asking you have failed to come up with even one actual example. Maybe you can give one now?

Let's get something straight, we've already replaced your cheap build system. Our build system works. We already have Pyro images. What's a work in progress is a native GUI based installer. This is something that's been on the Syllable roadmap, but has never had work started on it. Also, we're replacing the chaos of sIDE, Catalog Editor, Sourcery, & any other stray tool that you guys have to string together with an actual full-fledged IDE. In addition, there's the matter of improving the driver framework & writing new drivers. The issues we're having have nothing to do with middleware scripting bullshit, we're having issues because we're addressing the parts that you seem to be ignoring --THE ACTUAL OPERATING SYSTEM. I suppose that you don't have these issues, since you don't do any operating system development or any native application development. Had you done any, you would've also come across missing or partially implemented functionality in libsyllable (which we've been addressing in libpyro). Also, you'd be a fool to think that the codebase at our website is an accurate representation of our state of affairs. We're OS developers, not web developers. We're also actively working on a port of git, so that we can to repo management natively from within Pyro, rather than from another host OS. So, if I'm so incompetent, why am I talking about actual OS development while you're still gluing middleware into your OS & hoping for sympathetic developers to aid your cause? Perhaps you should mirror our approach - sit down, stfu, write some f'n OS code; it just might work out for you. Oh, wait, you don't know how to do that...sucks for you!