« Return to Thread: Netbeans SLOWDOWN - PLEEEEEEZZZZZ HEEEELLLLPPPPP
Re: Netbeans SLOWDOWN - PLEEEEEEZZZZZ HEEEELLLLPPPPP
by Peter Ford-4
::
Rate this Message:
Jess Holle wrote:
> Peter Ford wrote:
>> Windows XP ? For developing code? With ONLY 2GB of RAM? You're having a laugh!
>> And a source file that's 7000 lines long suggests you need to think about your
>> code design.
>>
>> 1. Get linux
>> 2. Get more RAM
>> 3. Refactor your code.
>> 4. Stop cussing and get on with it...
>>
> The post that started this thread was abrasive, etc. [It was also not
> mine.]
>
> That said, when it comes to class file length, etc, shtuff happens.
>
> * 7000 lines is by no means the upper limit of what I've seen in a
> Java source file. You can't refactor a decade's worth of code
> overnight. Nor should you have to.
> * Windows XP is a commonly /required/ platform in business -- and
> where it is not required it is the only thing IT will provide any
> assistance whatsoever with. Not everyone wants to be the system
> administrator for their machine at work. Some people just want to
> do their work.
> * RAM is often at the discretion of your employer. While going to
> 4GB is cheap and clearly worth it, this may not be clear to
> accountants.
>
> Despite the original abrasive post, there is no reason a Java IDE
> /written in Java /shouldn't be able to handle 10-15k source files well
> (and do so without using SWT).
>
> I have 4GB of RAM and a Core 2 Duo, so perhaps that does the trick, but
> NetBeans hasn't struck me as /awful/ in dealing with such files lately.
> Or perhaps it is just that I've been able to avoid such files as of late.
>
> In any case, no one should be under any illusion that NetBeans shouldn't
> work /well/ with such files as this situation is a fact of life for many.
>
> --
> Jess Holle
>
You're absolutely right - I think the OP should have no problems with the set up
he's using, even in the code is 7000 lines or more. I didn't put the smileys in,
so I guess it turned into a flame rather than a light-hearted response. ooops... :(
I've certainly had no real problems on a much less highly-specced system than
the OP described, except that I don't use MS Windows. I have seen other people's
systems where Windows XP happily slurps most of 2GB on irrelevant nonsense and
leave me with a few KB to actually do anything productive, so more memory is
worth a look for serious development work, as is an alternative OS.
At the moment I'm using NetBeans for PHP coding, not Java, so I'm not seeing the
compile-on-edit problems, and even the scanning performance issues that others
have highlighted don't seem to be a problem.
--
Peter Ford, Developer phone: 01580 893333 fax: 01580 893399
Justcroft International Ltd. www.justcroft.com
Justcroft House, High Street, Staplehurst, Kent TN12 0AH United Kingdom
Registered in England and Wales: 2297906
Registered office: Stag Gates House, 63/64 The Avenue, Southampton SO17 1XS
> Peter Ford wrote:
>> Windows XP ? For developing code? With ONLY 2GB of RAM? You're having a laugh!
>> And a source file that's 7000 lines long suggests you need to think about your
>> code design.
>>
>> 1. Get linux
>> 2. Get more RAM
>> 3. Refactor your code.
>> 4. Stop cussing and get on with it...
>>
> The post that started this thread was abrasive, etc. [It was also not
> mine.]
>
> That said, when it comes to class file length, etc, shtuff happens.
>
> * 7000 lines is by no means the upper limit of what I've seen in a
> Java source file. You can't refactor a decade's worth of code
> overnight. Nor should you have to.
> * Windows XP is a commonly /required/ platform in business -- and
> where it is not required it is the only thing IT will provide any
> assistance whatsoever with. Not everyone wants to be the system
> administrator for their machine at work. Some people just want to
> do their work.
> * RAM is often at the discretion of your employer. While going to
> 4GB is cheap and clearly worth it, this may not be clear to
> accountants.
>
> Despite the original abrasive post, there is no reason a Java IDE
> /written in Java /shouldn't be able to handle 10-15k source files well
> (and do so without using SWT).
>
> I have 4GB of RAM and a Core 2 Duo, so perhaps that does the trick, but
> NetBeans hasn't struck me as /awful/ in dealing with such files lately.
> Or perhaps it is just that I've been able to avoid such files as of late.
>
> In any case, no one should be under any illusion that NetBeans shouldn't
> work /well/ with such files as this situation is a fact of life for many.
>
> --
> Jess Holle
>
You're absolutely right - I think the OP should have no problems with the set up
he's using, even in the code is 7000 lines or more. I didn't put the smileys in,
so I guess it turned into a flame rather than a light-hearted response. ooops... :(
I've certainly had no real problems on a much less highly-specced system than
the OP described, except that I don't use MS Windows. I have seen other people's
systems where Windows XP happily slurps most of 2GB on irrelevant nonsense and
leave me with a few KB to actually do anything productive, so more memory is
worth a look for serious development work, as is an alternative OS.
At the moment I'm using NetBeans for PHP coding, not Java, so I'm not seeing the
compile-on-edit problems, and even the scanning performance issues that others
have highlighted don't seem to be a problem.
--
Peter Ford, Developer phone: 01580 893333 fax: 01580 893399
Justcroft International Ltd. www.justcroft.com
Justcroft House, High Street, Staplehurst, Kent TN12 0AH United Kingdom
Registered in England and Wales: 2297906
Registered office: Stag Gates House, 63/64 The Avenue, Southampton SO17 1XS
« Return to Thread: Netbeans SLOWDOWN - PLEEEEEEZZZZZ HEEEELLLLPPPPP
| Free embeddable forum powered by Nabble | Forum Help |
