On the contrary, I've found Eclipse to be very responsive and pleasant to use, 
having now used it exclusively for the past 8 months or so and been 
particularly productive with it.

I'll absolutely grant that the plugin/RCP development lifecycle is painful, but 
if you're lucky enough to avoid being an Eclipse plugin author, you get to 
enjoy all of the benefits that go along with that ecosystem.  I particularly 
like the bleeding-edge attention Amazon gives to their AWS plugin[1] and the 
GUI builders that Google open-sourced sometime last year[2].

- Chas

[1] http://aws.amazon.com/eclipse/
[2] http://code.google.com/javadevtools/wbpro/index.html

On Apr 1, 2011, at 10:18 AM, Armando Blancas wrote:

> That's how it is with these bloated IDEs. My day job is mainly Eclipse
> plug-in/rcp dev, so I'm also guilty of putting an absurd burden on
> others (disk footprint, startup time, memory use, unresponsiveness),
> but that's what's passes for effective tooling these days.
> 
> On Apr 1, 4:10 am, Chas Emerick <cemer...@snowtide.com> wrote:
>> On Apr 1, 2011, at 5:29 AM, Meikel Brandmeyer wrote:
>> 
>>> Hi,
>> 
>>> On 1 Apr., 11:01, Laurent PETIT <laurent.pe...@gmail.com> wrote:
>> 
>>>> ;tldr means "too long, didn't read" (I discovered this recently) and it 
>>>> acts
>>>> as a sort of the start of a short section at the end of a long post where
>>>> people not having time to read it in its entirety can see a summary.
>> 
>>> For this case it could look like this:
>> 
>>> "tl;dr: I have severe responsiveness problems with Netbeans and
>>> Enclojure. There is no obvious CPU activity, so it seems to be
>>> something I/O related. The status message "Checking for external
>>> changes" also points into this direction. Does someone have a similar
>>> problem?"
>> 
>> Yes, I encountered such behaviour on a regular basis across many releases in 
>> my time using NetBeans (close to 2 years, which started when Enclojure was 
>> the only option for those of us that are allergic to emacs).  In my 
>> experience, NetBeans does get gummed up on a regular basis, almost always 
>> while engaging in various automatic IO-intensive scanning processes:
>> 
>> http://blogs.sun.com/netbeansphp/entry/enable_auto_scanning_of_sourceshttp://wiki.netbeans.org/FaqScanningAndIndexingIssues
>> 
>> The project actually has a FAQ highlighting various ways the IDE might 
>> become unresponsive:
>> 
>> http://wiki.netbeans.org/FaqSlowNetBeans
>> 
>> - Chas
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with your 
> first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to