Tag Archives: beware

REALbasic: Cross-platform that really doesn’t work

It sounds too good to be true. Write once, run everywhere. (Where did we hear that promise before?) Alas, it is. I’ve been working with REALbasic for about a year, now, and my conclusion is that it’s not ready. Given that they have been working on it since 1996, I suspect it never will be. As a language, it’s amateurish. Threads are not native, and are actually cooperative as opposed to preemptive. Kind of like the Mac back in the 1980s. Worse, threads hand over control not at regular intervals, but at each iteration of a loop. Who came up with that horrendous kludge? It’s hard to believe they have the gall to actually release a version of their software dubbed “Professional.”

But being merely amateurish wouldn’t be enough to warrant a blog post. I’m warning people off of this piece because it’s so buggy as to be almost unusable. I’ve had problems with bugs in their semaphore class not actually protecting resources from all threads. (Apparently they really have a problem with this thread thing.) Most problematically, however, the IDE itself is highly unstable. Sometimes, under Linux, it gets confused and when you hit “delete” in an editor window, it actually think you want to delete the whole method, not just the current character. That’s obviously a problem, especially if you don’t catch what it just did, and accidentally hit save. Restarting fixes this. Right now, whenever I set a breakpoint, it crashes with a segfault upon reaching the breakpoint. Running without the breakpoint works fine. Clearly, they need more work.

Maybe in another ten years they’ll be ready, but for now I suggest anybody considering REALbasic learn a real language instead. BASIC can potentially be a great language, but in the hands of these guys, it’s open mike night.

For the love of all that is holy, stay the hell away from OpenOffice

Twice now I’ve had it hopelessly corrupt a file on me. (What is it they say about “fool me twice, shame on me?”) Saving isn’t enough with this ungodly piece of shit. You need to run ten minute backups of the file you’re working on so that OpenOffice can’t kill it. The latest accomplishment of this pig astounds me: I opened a document and had OO open up a second window, so I could edit one part while looking at another. At some point, I close the window in which I was editing. Poof, the changes I made in that window were erased. You probably think I accidentally deleted something, right? Nope. Going back through the undo history, my changes just weren’t there. Things I’d done before the changes that were lost were undoable, so something fishy clearly happened. You also probably think I stupidly opened two windows using two different instantiations of OO, so that one overwrote the other. I didn’t; I used the “New Window” function. I suspect there is some bug with how OpenOffice handles two windows on the same document.

If this stupid blog does one thing useful, it will be to save just one person from using the complete waste of space that is OpenOffice. I can’t tell you how much I’d be willing to pay for Microsoft Office if I could go back in time and use it instead of OO, but I can tell you it’s a lot more than Microsoft charges for Office. What’s really embarrassing is that using a “community developed” version of office software is exactly the kind of stupid, false economy for which I railed against desktop linux.