Skip to main content

Aptana - Please Don't Suck Any Harder

I wrote this post after hours of frustration, trying to fix my broken environment, and losing valuable time on a project that was falling behind.

I now realize that the post was overly emotional, and probably not entirely fair to the Aptana team. I'll post updates here as I work through the issues to get my RadRails working again.

Comments

Adam Bard said…
I can't speak for the Mac version, but I haven't had stability problems on either my Linux or Windows machine. The Linux one was using ridiculous CPU for a while, but I switched to Sun-Java and that seemed to sort it out.

That said, it's certainly not the best for anything but Javascript. But doesn't Mac have better Rails options anyhow?
Adam, there are certainly options. IntelliJ IDEA now has support for ruby, but IDEA is not free. TextMate is the tool of choice for the majority of Rails developers, but I personally always preferred the integrated multi-window environment. That said, I am pretty much switching to TextMate now, but unfortunately not because of free will but because I have to get some work done :)
Hi Konstantin,

I'm sorry to hear that you're having issues and I'd like to help. As part of our RadRails release, we spent a significant amount of time adding many new features and fixing existing bugs with the goal of giving people a great Rails development environment.

It sounds as if Aptana Studio may have had an issue with some old configuration information when you re-installed. You might try the steps here to see if it solves your issue:

http://www.aptana.com/node/251

We're mostly Mac users here. I'm trying out the latest version of the standalone version on OS X 10.5.2 and I'm unable to reproduce the Apple-Shift-R issue, so any help in reproducing the problem so we can fix the issue would be greatly appreciated.

Popular posts from this blog

Car or Auto Make-Model-Year Database : For Breakfast

Make Model What?If you like me were tasked with loading a database of recent car makes/models/years, you would start by looking on the web and seeing if someone else just has it out there, readily available, hopefully for free, but perhaps for a tiny nominal fee.?If only it was that simple... I looked and looked, and couldn't find anything that would fit the above requirements. So I thought, who would know about US car models better than Kelly Blue Book? So I went on their site, and sure enough they have a javascript file that lists all known to them makes and models of used cars. Since the file is public, I figured it's not really "evil" if I scrape and parse it for my own benefit. Disagree? Have a better source? Then leave a comment.Anyway, to cut the long story short, I'm hoping to save a day or so to someone else who may, like me, be looking for this information. The ruby module shown below retrieves and parses the javascript from KBB site into a Ruby da…

Why I Like PostgreSQL

Today I gave a short presentation at work about PostgreSQL, and why I much prefer it to MySQL.

PostgreSQL vs MySQL: Eternal Battle
I may be misreading this, but it seems that there is a recent trend within startups to move away from MySQL, probably thanks to folks like Heroku on one side (who use PostgreSQL to the extreme, and help and contribute to it's development), vs folks like Oracle on the other side, tainting the "open source pureness" of MySQL :)

At my work we currently use a mid-sized MySQL 5.1 Percona instance, which is holding up quite well I must admit. Both PostgreSQL and MySQL have definitely converged to cover most features that people want, but my leaning is still towards PostgreSQL. I just agree with it's focus on data integrity, recovery, constraints, extensibility, while some of the early decisions in MySQL's design do not agree with me at all (like truncating long strings, 1/0 instead of booleans, ambiguous group by, etc). I think that data …

On Ruby on Rails with PostgreSQL, and Acts as Paranoid

Back a few years ago I was researching differences between PostgreSQL and MySQL databases, and chose PostgreSQL because at the time it supported foreign key constraints and many other fantastic SQL extensions that make developer's life a lot easier. Today I am sure MySQL is just as functional as PostgreSQL, and it does appear to be a more popular choice as the Rails DB than MySQL. I still prefer PostgreSQL, it just feels more natural to me coming out of Oracle background, so I am probably biased (who isn't?) Anyway, in the last year and a half or so, I've been writing Rails apps that use PG-based databases and found a few random tricks I'd love to share here. Opinions differ here, but just like accountants like the ancient double entry accounting system, I personally prefer a double validation system - where Rails validates my objects before/after updates, but the database double checks this using proper constraints. Rail's validation system is very robust and ext…