From: "Daniel L. Taylor" <[EMAIL PROTECTED]>
Date: Fri, 5 Jan 2007 01:37:42 -0800
I'd like to know why everyone is using REALbasic. There are other
tools
out there. There are other languages out there. Why REALbasic?
I use a number of tools and choose the one I think is best for each
job.
RB's big advantages to me are:
* Cross platform with native binaries and widgets.
* Rapid development features, including a pretty broad class
framework that
runs as expected on all platforms.
* Rapid deployment features, i.e. you don't need an installer or
special
libraries on any platform.
* Good balance in the framework design. Some of .NET's classes are
more
formally designed but also too "deep", i.e. too many steps to get
from A to
B. Some other tools are too "shallow", i.e. you can get from A to B
but only
with one set of options. RB's framework and widgets seem about
right in
terms of complexity and flexibility. And when they're not there's a
decent
supply of 3rd party classes and widgets.
Not always :(
Folderitems are over complex. Why have binarystream and text streams?
They are the same thing. RB enforces some crazy model where you
"aren't supposed" to use absolute paths, despite that everyone else
in the world does it. Or at least they use relative paths instead.
Aliases (getsaveinfo) are on the way out, they are a totally outdated
concept, bloated, not portable. Relative paths are the simpler more
modern way that works everywhere. But RB has no concept of a current
directory or a relative path, at least not a proper one. I wish RB
would just do file paths the Unix way, but their getfolderitem
doesn't allow for relative paths!!! Ridiculous.
In Cocoa, I can do something like this:
dim s as string
s = "file data"
s.WriteTo "/path/to/file.txt"
That's it. You wanna tell me that RB's way with binarystreams,
folderitems, enforced using of .child and all the rest of it, is
simpler?
RB's editfield really is superlacking, also. Styling is a pain, and
slow.
RB's listbox is done the wrong way also. It should be using some kind
of datasource, like Apple do it. In fact it should be done entirely
like Apple do it ;) maybe a bit simpler here and there but the same
structuring, because Apple's approach really works.
On the other hand, stuff like sockets is quite easy to use. SImpler
use of the GUI is very easy...
--
http://elfdata.com/plugin/
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>