[TYPO3-ect] Eclipse Plugin Development Status

[ries van Twisk]

On Sep 21, 2007, at 12:13 PM, Elmar Hinz wrote:

>>> Speed is the point. I can't develop faster with current Eclipse,
>>> but it can
>>> be big help for beginners.
>>
>> But some people can developer faster with an IDE, that's why they are
>> so popular,
>> and that why GUI's are so popular ...
>>
>
> Yes it depends on situations and for people:
>
> 1.) if you have real autocompletion of methods and arguments like  
> in java.
> 2.) if you people don't invest some time to learn useful key  
> combinations
> 3.) for beginners
> 4.) for huge projects with many levels of directories (not T3  
> extensions)
> 5.) for people with badly organized code that need assistants to  
> orientate
>      in the own code
>
> 1 and 4 would be situations, that would lead me to switch. For T3  
> extension
> vim is still the fast solution for me.
>
> Regards
>
> Elmar
>
>

Correct,

4) applies to me... I do run a couple of bigger projects here at any  
given time for which I
need to have many tools at my finger tips at any given time.


5) I don't agree... i think vim cannot solve badly organized code  
better then any other tool.
I think vim can provoke badly organized code bases as well...

1) I don't need it that badly... does vim do it so well?

3) I think that any tool, both IDE's and vims can be for beginners  
and professionals.
there are to many real world examples of that. Most professional  
tools I know of
are some form of a IDE anyways... (vim is more for nerds???)

2) Why? Most of my time goes into projects design, rather then coding  
anyways..

However we do agree both on one thing.

  - People should use the tool set that can do the job the fastest  
for them.. There are some exceptions,

for example (non programming)
We had to decide what 3D design software to use and had to pick  
between Pro-Engineer Wildfire (WF)
and Solid Works (SW) (I was biased towards WF)

For the work we where doing one particular user could swear he could  
do it faster with SW, rather then
WF. we did setup a couple of test cases and projects to really proof  
one tool over the other.
In these tests it showed clearly that SW was good for small simple  
projects, while WF won hands on down on
large projects, but no so much on the smaller. The estimated savings  
where huge when using WF over SW.

What I am trying to say is that it all depends what the user is  
doing.....

I think we should stop this discussion now and we should start

a thread about windows vs Linux vs OSX which can be fun aswell. :D  
Just kidding...

again... it depends what you are doing, what teh company is using  
etc... all tools have there place.


Ries