REALbasic Linux IDE Public Beta Available
An anonymous reader writes "A brand-new visual development environment for Linux is in public beta now. REALbasic 2005 for Linux Standard Edition will be available for free when it ships in August. The company has also done away with their email registration requirement. Download the public beta now from REAL Software."
While a slick desktop would help the quick adoption of Linux, being able to EASILY and quickly write ad hoc business applications from within linux will help more. The fact that you can write your apps using the Windows, Mac, or Linux IDE and then target all of the same will allow a company to make a gradual shift as well instead of balking at an all-or-nothing choice. Put this product right alongside Firefox and OpenOffice as tools that could seriously undermine the future hegemony of Microsoft on the business desktop.
Thanks. I can't believe the editors would be lazy enough to not only post a direct-download link, but also not add an information link. I hate when sites do that because it feels like they're cramming some new software down my throat when I'd rather read up on it first.
Arguing about vi versus Emacs is like arguing whether it's better to make fire by rubbing sticks or banging rocks.
True story: I used to work for a major internet retailer as a UNIX systems engineer/administrator. This major internet retailer, named after a large river, had a warehouse in Seattle. The warehouse operations manager was a very smart cookie, not a programmer or developer, but still very smart. One day this manager needed a tool to check shipment status, he requested this from the software developers, but they were too busy wanking over "good programming practices" (whatever those are, from a plurality of the developers I've worked with it seems that their good practices are "overpromise and underdeliver", "blame the hardware" and avoid being oncall if at all possible) to develop this for him. So this warehouse operations manager went and got himself a PERL book and sat down and wrote a tool that did what he wanted it to do.
When the software developers found out about this they were aghast. Aaaaacccckkkk! Someone other them then writing a tool, a member of the unwashed actually coding, God forbid! Of course the developers found a lot to bitch about in his tool, it wasn't very good PERL they said, it ran out of his home directory, it beat the shit out of the database and our NetApp filers, etc, etc, etc, yadda, yadda, yadda. But all of them missed one point, if they had gotten off of their asses and used all of the good programming practices that developers keep nattering on about to develop the tool he requested he wouldn't have had to sit down and write this thing (which really wasn't that bad, he had followed the style that most PERL books use in their example code). If they had done their jobs he wouldn't have had to do theirs (as well as his).
Of course I worked with lots and lots of people who called themselves software developers who wrote code that pounded our systems to their knees by running full table scans against databases, writing vital log files to a directory that was NFS mounted from a personal Linux workstation, leaking memory, running out of control and pegging the CPU, etc, etc, etc, etc, and they were writing most of their code in C and C++, those darling languages of those who call themselves professional software developers.
I guess what I'm trying to say is "go fuck yourself you arrogant prick!" You're not as smart as you think you are. You're not as good of a programmer as you think you are and you obviously know nothing about REALBasic (it ain't GWbasic or even Vbasic) and if it helps users get their job done then it's a good thing in my book, even if it isn't in yours.
cheap labor conservatives - they want to keep you hungry enough to be thankful for minimum wage.
Linux applications are not usually known for good programming.
The ones that are good examples were generally created first by a commercial software house.
ie.) PostgresSQL was done well enough that I was able to figure out the architecture without documentation fairly quickly.
Though, I do agree with your main point, about java, mono, and python being better alternatives.
Also, I do agree that better applications programming skills are needed, and things like source forge and the oss model help young programmers to learn how to more effectively become experienced programmers.
Really not hard to see why you got kicked out of their beta program - you've missed the entire point. There is no such thing as a bug that is "too obvious to report on". Did it never occur to you that, perhaps, those bugs that seemed "obvious" to you might have been anything but to someone else? Different people use different pieces of software in different ways. I'm a developer, and I can't tell you how many times I've gotten bug reports where people described ways of using the software that seemed completely bizarre to me, but that seemed totally normal and obvious to the people who reported them. They couldn't imagine why we let such an obvious bug slip; I couldn't imagine how they ever thought of doing that in the first place. This happens. It's normal. That's what beta testers are for. You didn't do your job; no wonder they kicked you out.
And what kind of bullshit is "the code first has to reach a certain level of maturity before it can properly enter a beta status"? What the hell are you talking about? Software is beta when its developer says it is beta, and they usually say it is beta when they are done adding features to it.