From: Mushfeq Khan <mushfeq.khan@...>
Date: 2006-12-18T02:26:37+09:00
Subject: Re: Ruby IDE

------=_Part_4318_30330559.1166376393815
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Twice a month??! I'm not going to name any names, but here goes...

Ideally you would keep your IDE open all the time. But in practice things
are often less than ideal. As intellijent as these things are, they are also
often very memory and disk intensive and eclipse your computer's resources.
I have the good fortune of using two rather heavyweight IDEs during the
course of my daily work and I find that on average I have to restart at
least once a day due to bugs, corrupted local histories and other general
wonkiness.

That's not so bad, but sometimes there are legitimate usage patterns that
become a real pain. For example, if you're working on several different
projects each day, all of them large-ish codebases, then you probably don't
want to keep them all open at the same time. Closing and reloading projects
in the IDEs that I use is no quicker than a full restart.

I hope I've been vague enough that no one has a clue which IDEs I am talking
about. Apart from the above issues, they are quite quite excellent. So I
don't really have any preferences on the text-editor vs IDE issue.

Mushfeq.



On 12/17/06, David Vallner <david@vallner.net> wrote:
>
> Sam Smoot wrote:
> > There seems to be some confusion though: You don't compile Ruby. The
> > Ruby interpreter executes your source code directly. So other than
> > syntax checking, integrated help, and syntax highlighting, an IDE
> > doesn't buy you much.
>
> Like integrated unit test support.
> Project management.
> Debugging with source code navigation.
> Semantics-aware code templates.
>
> No, not much, unless you actually learn to use one effectively.
>
> > But I don't use class-browsers,
> > integrated unit-testing suites, etc. There's a command-line equivilent
> > for each of those with Ruby, and they're a lot more convenient than
> > learning 5 different ways for 5 different IDEs.
>
> Erm. The thing is you pick an IDE, stay with it, and use one way to
> consume those things only instead of keeping idiosyncracies of
> command-line interfaces in your head.
>
> Also, this is too strongly an issue of personal work patterns to be
> preached, and I find it irresponsible to mention that without a big YMMV
> disclaimer.
>
> > I can go through that whole cycle in a
> > fraction of the time it takes Visual Studio 2005 + Resharper to load on
> > my work computer...
> >
>
> How often a month do you need to load an IDE again? Twice?
>
> David Vallner
>
>
>
>
>

------=_Part_4318_30330559.1166376393815--