Commercial Mac IDE

[Ryan Rawson]

Eclipse is not really a great environment to develop plug-ins for.
Lots of verbose structure (well it _IS_ Java after all), and lack of
documentation for many core/fast changing features.  For example I
wrote an Eclipse plugin to handle classpath derived from a custom
build dependency system.  Well it turns out Eclipse doesn't handle
dynamic classpaths well, and there certainly isn't any documentation
on how to do anything more advanced than add static strings to a class
path (useless) or handle dynamicism.  The eclipse plugin development
classpath dependency has the same problems and it handles them just as
poorly.

Also Eclipse is teh slow.  Emacs feels like a speed demon.

I would never use any IDE based on Eclipse again for non-Java languages.

On 8/11/06, Vlad Dumitrescu <vladdu55@REDACTED> wrote:
> Hi,
>
> My point was that it may be worth considering the options first.
> Having done some work on an IDE framework before, I know there are a
> lot of tricky details. So riding on the Eclipse wave would cut a lot
> of corners.
>
> If the project is seen as a "learn by doing" thing, then the above
> doesn't apply. But for a commercial project, time to market is very
> important. There are a lot of commercial Eclipse-based environments,
> so it's possible to build upon erlide with extra plugins (comercially
> licensed).
>
> And of course, I wouldn't mind if this would help along Erlide too :-)
>
> regards,
> Vlad
>
> On 8/11/06, Simon Chappell <simonpeterchappell@REDACTED> wrote:
> > > This is a large project, and if only for Macs, usefult for not so many...
> >
> > On the other hand, the Mac community have a strong track record of
> > supporting shareware authors by actually paying for the software.
> > While normally, an outsider might view the Mac community as too small,
> > they generally are capable of supporting quite an amount of shareware
> > authors.
> >
> > Oh and they tend to be fairly fanatically loyal as well. :-)
>