[Openmcl-devel] A plug for nx1-combination-hook
dlw at itasoftware.com
Thu Sep 10 11:52:08 EDT 2009
Tim Bradshaw wrote:
> On 7 Sep 2009, at 17:52, Terje Norderhaug wrote:
>> I am in the camp preferring a more spartan, focused IDE for myself,
>> with just the functionality I need. But I can see the attraction of
>> toolbars etc. It could be useful to have a variety of IDEs on top of
>> a lisp environment, supporting the taste/needs of different
> I agree with this, but I feel perhaps more strongly. I use Eclipse
> relatively frequently, and it basically makes me feel fairly ill every
> time I do so. I'm not a very fluent Java programmer but I still do
> not want something that overwhelming (and I can't see anyone who can
> type wanting that). It may be that younger programmers today *do*
> want that - I guess the fact that Eclipse exists at all must indicate
It does not merely exist at all. It is very widely used.
I would like to see the "curl" package, which is a Lisp
module for Eclipse, improved.
One technological thing I'd like to see if to make
the Slime/Swank protocol be documented and
stabilized, so that other IDE's than Slime can use
Swank in a non-brittle way.
I agree that it makes sense for there to be more
than one IDE, because there is more than one
"target market". There are the Emacs people,
the Eclipse people, the MCL people, and so on.
> So I'd (obviously, since I'm not contributing anything other than
> whining!) be fine with some more fashionable IDE but I'd like not to
> sacrifice the more spartan one if possible. I'd also rather have the
> bugs worked out of the spartan one first, as Hemlock falls about
> annoyingly often (but again, don't listen to me, I'm not the customer!).
> FWIW I quite liked LispWork's IDE which was a good compromise and had
> a number of powerful tools (mainly the grapher). I would still be
> using that if I could justify the cost given how much CL I write now.
> So looking at that might be interesting.
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
More information about the Openmcl-devel