« Return to Thread: [Tapestry Central] Caught between Two IDEs

Re: [Tapestry Central] Caught between Two IDEs

by Ulrich Stärk :: Rate this Message:

Reply to Author | View in Thread

I'd already be happy with a Tapestry DTD file for use with Eclipse's XML Editor

On 03.07.2009 09:47 schrieb Ivano Luberti:

> The 3.3 version was clearly bugged with a memory leak they have never
> solved.
> This is objective.
> Now I use 3.4 and I'm an happy man: I don't know what I could ask more
> from an IDE except for a useful Tapestry plugin ;-)
>
>
> Angelo Chen ha scritto:
>> I got two reasons not using Eclipse:
>>
>> 1) crashes, it just simply crashed even sitting there, probably it's getting
>> better now.
>> 2) don't know what to download, so many versions out there, and never find
>> out which one is correct for me, in front of Eclipse I'm really a newbie:)
>>
>> angelo
>>
>>
>> Christian Edward Gruber-2 wrote:
>>  
>>> I agree - I bounce back and forth as well, quite commonly.  I'm  
>>> encouraged by Eclipse 3.5 for reasons you cite, but it's  
>>> frustrating.   Every-so-often I seriously consider just a text editor  
>>> and command-line, but things like re-factoring tools, etc, usually  
>>> bring me back.
>>>
>>> I'll tell you though, the one that gives me a NeXT-style  
>>> InterfaceBuilder work-alike for Swing or SWT will probably win for  
>>> me.  (And if someone let me build tapestry code that way... drag and  
>>> drop GUIs... I'd definitely pay for that privilege)
>>>
>>> Christian
>>>
>>> On Jul 2, 2009, at 4:30 PM, Howard wrote:
>>>
>>>    
>>>> I seem to be caught between two IDEs: Eclipse and IntelliJ. I  
>>>> abandoned
>>>> Eclipse a couple of years back, partly based on wide spread
>>>> recommendations from many different people, and partly because Eclipse
>>>> just stopped working for me (it crashed out).
>>>> After I got started with IntelliJ I started to appreciate its merits,
>>>> despite a generally clunky interface (with lots of modal windows),
>>>> truly awful documentation. Many things are streamlined and only a
>>>> ctrl-alt-shift-coke-bottle-touch-your-nose away.
>>>> However, over time, using IntelliJ got slower and slower and slower.  
>>>> It
>>>> also started running the Tapestry test suite horrifically slowly: 40
>>>> minutes and up (it should be about five). It would often go away, even
>>>> when memory wasn't tight. Indexing? Checking Repositories? Computing
>>>> primes? No way to tell.
>>>> Meanwhile, Eclipse has been moving forward, with Eclipse Galileo being
>>>> a Cocoa (not a Carbon) application. Critical plugins such as M2Eclipse
>>>> have gotten nice, and the Clojure plugin is mostly better than the
>>>> IntelliJ one (though both are very early).
>>>> For a while I was using IntelliJ when teaching Tapestry (as part of  
>>>> the
>>>> VMWare image I use when training) ... and I got a lot of resistance.
>>>> People were much happier with Eclipse on the last couple of go-rounds,
>>>> and I'm sticking with it.
>>>> Overall, I'm feeling that most of what I've grown used to in IntelliJ
>>>> is present in Eclipse, just handled a bit differently. The Clojure
>>>> plugins are a wash; IntelliJ has the edge on the Git plugin. I think
>>>> Subversion inside Eclipse is actually better.
>>>> I've even cranked up NetBeans but didn't find anything there  
>>>> compelling
>>>> enough to switch.
>>>> It seems like all my major tools (Firefox, Firebug, Eclipse, IntelliJ)
>>>> are in the habit of growing too complex, and doing too much stuff in
>>>> the background that I don't care about. All those intentions in
>>>> IntelliJ that you have to turn off (for performance reasons), and all
>>>> those extra plugins for Eclipse that you need to not download in the
>>>> first place ... they're all getting in my way.
>>>> I think a lot of this falls into the general category of accidental
>>>> complexity ... to address the limitations of the Java programming
>>>> language, all this extra stuff is coming into play: tools and wizards
>>>> and plugins and indexes and whatnot. I find it pretty pleasant to work
>>>> with Clojure instead, where the accidental complexity of Java is
>>>> managed and isolated and the IDE doesn't feel the need to be overly
>>>> ambitious. That's the Clojure concept right there ... grow the  
>>>> language
>>>> to your needs, rather than building up tools. I think that's the
>>>> Tapestry ethic as well.
>>>>
>>>> --
>>>> Posted By Howard to Tapestry Central at 7/02/2009 01:10:00 PM
>>>>      
>>> Christian Edward Gruber
>>> christianedwardgruber@...
>>> http://www.geekinasuit.com/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@...
>>> For additional commands, e-mail: users-help@...
>>>
>>>
>>>
>>>    
>>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

 « Return to Thread: [Tapestry Central] Caught between Two IDEs