A rapid development environment, similar to Visual Basic, published by REALSoftware. It is available at realbasic.com.
*My comments from experienced C++ cross-platform developer, pertinent to the current shipping (5.5) RB version towards end of this page - AndyDent *
Not as rapid as Cocoa. (Actually, it’s more rapid than Cocoa for simple projects, but it becomes unwieldy with large scale projects. I learned how to program the Mac with REALBasic and then recently swithed to Cocoa (which I like much more). However, RB is easier for some simple things, and it’s nice to have built in support for things like regular expressions).
Perhaps because of its ease of use, notorious for facilitating the production of horrible apps by inexperienced and/or clueless developers, many of them reviewed at http://www.perversiontracker.com/
Anyone want to compete with me to attempt to get an app listed on peversion first?
I thought their last nominee iPong was actually pretty cool (only the paddle and ball graphics could have been done better). Who can account for taste (mine included)?
Programming with RealBasic is like bowling with the bumpers up.
No, I don’t think it’s like that at all. It’s more like buying a kiddie bowling set at home, and playing with it. Things in realbasic just don’t work… if it had some interface builder cooperation, I think it’d be worth using.
I second that, i used to program using Visual Basic on the PC, interface builder is really good, that with the coding language of REALBasic would be REALLY good! Each language has it’s positive’s and it’s negatives, REALBasic just has more negatives, REALBasic has a stupid UI editor, and is too “classicish” needs to learn from OSX and is too “carbonised” needs to be written in xCode!
I don’t think there’s anything particularly wrong with REALBasic per se. It’s a good language. I think it has suffered from two major problems, however: feature bloat and over simplicity. The REALSoftware team has tried to add too much too fast to a language that is still a BASIC at heart, creating a horrible mish-mash that produces executables 12x larger than they need to be. Also, because they oversimplified REALBasic so much, many people who don’t really know anything about proper development produce quick apps with it that come out shoddily. It is perfectly possible to write a good and useful program in REALBasic. It has earned its reputation, however, because most people don’t. –OwenAnderson
I second that.
So what it comes down to, perhaps, is that they made programming simple where they should have been making total design simple? That was my experience with RB, more or less. – RobRix
The main problem with REALbasic is that it is incredibly buggy, and I have issues with the people at REAL Software and their attitude. – FinlayDobbie (Yes, I agree, it is definitely full of bugs. When new versions come out, they tend to add new features rather than fixing the already existing bugs! Doh!)
Actually, REALbasic has a few things over cocoa. You can build windows executables, for example. While we all love our macs, some of us may want to distribute to other platforms. Unfortunately, REALbasic’s apps are barely true-carbon. If you make a metal window with it, it won’t be dragable properly. You can do a lot with RB, and it’s a good language, which I’ll use for some things, but unfortunately, it’s not good enough.
REALbasic is good for simple, small projects, but nothing commerial or shareware at all. Once you start to get complicated in your app, it just fails left and right. I had been using REALbasic for a while and got to know the language very well, wrote many many apps (most just fun things) but I switched to Cocoa a while back since it is so much more stable and expandable and freakin’ awesome. – KevinWojniak
Once they work out the kinks, RB will be really good. I like some things about RB, and hate others. –CharlieMiller
“Once they work out the kinks” has unfortunately been repeated for years now. I cannot now think of any situation I would use RealBasic over Cocoa in at the moment, although that’s biased by the familiarity with Cocoa I’ve been developing since before the PB came out. – RobRix
I said once they work out the kinks, but it’s true, it’s likely they will never work them out. You should give it a try though… it’s better than most cocoa developers think. I’d rather use RB than do standard carbon and/or windows programming… that just frightens me. –CharlieMiller
I think there’s no disagreement over this fact: REALbasic is a hell of a lot easier for a beginner to learn and use than Cocoa. I agree with RobRix - RB is 5 years old now and it’s still awfully buggy. I learned to program on REALbasic, and just recently I’ve started moving over to Cocoa. I believe that my RB ability helped me a lot here - I had only to learn ObjC syntax (took an hour) and I was already past the beginner stage. Going back to what I said at the beginning - RB is easier for beginners to pick up - that’s both good and bad at the same time, as many people have remarked. Some people can do great things with RB, others just churn out electronic turds. But there’s no denying it’s a good learning experience. –OwenYamauchi
Good programmer + REALbasic = good program. Good programmer + Cocoa = good program. Bad programmer + anything = bad program.
One problem I had with REALbasic (besides some annoying bugs) was, that it’s basically a closed environment. It’s somewhat difficult to include foreign code. And whenever Apple changes the APIs you have to wait for the folks at RealSoftware to update REALbasic. With Cocoa this is so much better … Always up to date, no problems including C, C++, Java, …
Well, REALbasic does have plugins. (One thing I would like to do now that I know C is write plugins, but you need CodeWarrior - which I won’t buy.) Also, the built-in system for Declare statements is very convenient. I’ve programmed a lot of the custom RB code I release using Declares. I will concede that Cocoa is better integrated with the OS. The only major RB feature I’m going to miss is the ability to compile for 3 platforms (soon to be 4) from the same source code. –OwenYamauchi
(Insert standard rant about OPENSTEP/YellowBox’s lost multiplatform support, to the point of being able to ship one .app package that ran on all of them.)
That’s what’s happening to me, I believe. Except right now my computer’s in the shop. As for the huge compiled apps, that was something that repelled me, too. I think it’s a consequence of the cross-platform compilation thing. I’m on the RB Network User Group mailing list, and recently there was a big, heated discussion: should the RS folks concentrate on introducing glitzy new features (like compiling for Linux) or fixing bugs? The RS folks were adamant: new features were more important, unlike the all-bug-fixes release that someone requested. That’s their problem: not enough importance is placed on bug fixes. It’s losing them customers. Well, one, at least… me. –OwenYamauchi
Oh. So the discussion about bug fixing is still going on? That’s funny, because we had that same discussion a few years ago. That was when I decided that I didn’t want to work around RB’s bugs any more and … you know the story. :) –AndreasMayer
Whenever REALSoftware announces a new release of REALbasic, the bug fixing discussion occurs, as do other recurring discussions (text encodings, :)). The problem is that the company has to introduce new features in order to attract new customers, and keep old ones upgrading. At the same time, they need to fix bugs, in order to not have much worse software. So, they must strike a balance between the two, and everytime they announce new features, everyone vents their opinions to everyone on the lists, including most of the people that have no interest in listening to them. Apple, on the other hand is in a very different situation, because they don’t charge for Cocoa and the developer tools, allowing them to focus more on bugs. They also have many more resources. They have access to the APIs before they are released to the public (before developer seeds), and simply have huge programming resources, much more than REALSoftware will ever be able to afford.
And the ‘REAL has to choose between adding features and fixing bugs’ apology always follows hard on the heels of the bug fixing discussion. So when do the bugs get fixed? I used RB from F4 (pre 1.0) until about 4.5 and just got so fed up with the constant bugs on top of bugs on top of forced upgrades for fixes of last year’s bugs and broken promises that I jumped to Cocoa as soon as the beta dev tools were relased and haven’t looked back. RB version 1.0 was advertised as compiling for Mac, Windows and Java - it looks like they’ve finally gotten Windows targets working acceptably ~5 years later. Read RobRix’s comment about making design simpler - probably the majority of bugs I’ve encountered with the few RB apps I’ve tryed has been due to uninitialized preference items. Adding an API to the defaults database would fix that, but no, REAL would rather compile for Linux instead. Whatever.
Lets not forget… REALBasic PRO costs $399.95… REALBasic Standard costs $99.95, XCode is FREE!!! Also, REALBasic Upgrades cost $169.95 and $79.95 respectively… XCode updates are FREE!!! –FreedomDumlao
XCode also doesn’t compile for four platforms simultaneously.
I’d rather compile software that people will use. I’d rather compile for one platform that I care about than 3 I don’t. I’d rather compile software that people on the platform I care about won’t trash instantly (because they’re using the one platform where they haven’t been forced to acclimate to software that sucks.) I’d rather not get laughed off the face of the earth by Linux users for thinking they’d use something written in BASIC. I’d rather not get bug reports from Windoze users.
RealBasic is good for what BASIC has always been good for: enabling non-programmers to solve simple programming problems on their own without having to become a programmer. Unfortunately, too many feel the need to inflict their ‘solutions’ on the world at large and, in some cases, expect to profit from it.
Free as in beer. Someone pays for them.
‘Someone’ == Apple. Because Apple uses those tools to develop the very OS they run on, the applications that ship with the OS, the iApps… essentially everything they do. That’s a big guarantee of continued support & improvement. And even if Apple goes away, my code is in plain text files, compiled with a (mostly) standard compiler, in a standard language. It wouldn’t be difficult to port it to GNUStep or whatever arises to replace Cocoa. RB is a closed environment by a small company that could vanish at any time.
It would be 100x easier to port an RB app to VB then a Cocoa app to GNUstep or any other language/API. RB came from VB. Cocoa came from…. NeXTSTEP? Microsoft’s not going away anytime soon, but REAL… who knows what’ll happen to them.
The discussion on RB vs. Cocoa all boils down to one thing: your coding perspective. From the perspective of RB programmers, and their needs, REALbasic is the better environment and framework, and Cocoa does not meet their needs. From the perspective of Cocoa programmers, and their needs, XCode/Cocoa is the better environment and framework, and RB does not meet their needs. A member of each group will be convinced that their perspective is correct and that the other group is composed of idiots.
That’s it. Let’s end the argument now. ;-)
(BTW, I’m both a Cocoa and RB programmer. They are both excellent tools for their own purposes. So there!)
I’m sorry, but such equivocation is what a hanging curve is to Barry Bonds. Apologies if you are overseas and would rather talk about Thierry Henry or something. Don’t know the matching metaphor. Henry does not, however, need the goalkeeper to be flat on his face in order to score, or shall I say, trying to play on both ends of the field at the same time.