On 1 Oct 2002 at 17:51, Mike Aizatsky wrote:
> > 1 - Auto entering of quotes: This can't be disabled, and makes life
> > hell. Typing a quote by mistake (' is right next to ; on a US/UK
> > keyboard) makes one want to hurl the keyboard at the nearest monitor
> > and be done with. I don't understand the timesaving aspects of this
> > at all.
>
> 651 build removes two quotes on backspace (as IDEA does with "()" ).
> There was a bug in tracker and I don't understand why didn't you vote
> for it if it was so annoying? Or do should we use our telepathic
> abilities to deduce which feature is most annoying? I haven't also
> find even a post from you in this group about this issue.
I'm glad you did that. It was anoying (although not as annoying as the tone in the
note
indicates).
> > 2 - Editing large files gets slower in every build. I have an EJB
> > session bean that is rather large, and with build 650, I sometimes
> > have to wait a second for every keypress. Not a lot of fun. Used to
> > be a lot faster in 629.
>
> We are constantly working on performance improvement in latest builds.
> We've also weren't able to get _any_ feedback from everyone who claims
> that IDEA has bad performance. No sample files, no projects, no
> keysequences. Almost nothing.
Other than requiring large gobs of memory, I think intellij's performance is just
dandy (1gb,
1600+ athalon). The more I look into it, the more I am convinced that the performance
problems break into three categories.
1) JDK garbage collection / Insufficient RAM. - When garbage collecting and the VM is
swapped out, be prepared to wait a while.
2) Network issues when the files are stored on a network drive. (don't do that. Use
snapshot
views -- or their equivalent in other SCM systems).
3) Pathelogical code issues, where a specific construct in a large class causes
reparsing
delays. These are one-offs, and are usually 100% repeatable. If I open file
XYZ.java, it
takes forever... If you have that kind of case, then send XYZ.java to our intellij
friends and it
will be fixed.
> > I apologise for my tone, but it's very frustrating seeing a great
> > IDE become so bogged down and annoying to use.
>
> Looks like I should apologise for my tone too. But most EAP members
> have really great influence of our feature/bug fixing plans and I
> don't understand why don't you use this ability and only post a
> message which is almost backing by facts/SCRs. You can't blame us for
> not fixing problems we haven't heard of.
We are customers. We don't have to be rational :-)
> > That isn't the point, I'm unhappy because
> > I've seen what the IDEA guys can do, and frankly, the current builds
> > don't do them justice, and seem dissapointing compared to the great
> > things we've been spoilt with and (sadly) gotten used to.
>
> None of the development team member can really understand why come to
> acid?
I can't understand it either. I think the current builds are great. My suggestion
for those out
there who feel similarly, is try to put yourselves in the shoes of a test group.
Don't complain
that the development team is producing product you don't like. Proove it with
reproduceable
test cases, and clear direction to the development team on what should be done next.
We
are, afterall, basically the system test organization for IDEA.
Can you imagine if the test group at wherever you work decided to go to senior
management
and complain that the product was "insufficient", and that the development team was
"unresponsive" without taking the time to write defects and work with the development
team
to set priorities. I don't know about you, but I would rip them to shreds.
If you think it really shouldn't be your job to do this level of testing, then I
suggest going back
to an older version (perhaps all the way back to 2.6), and waiting.
Mike
---
[EMAIL PROTECTED]
To obtain my PGP public key, mail "SEND PUB KEY" in the
subject to "[EMAIL PROTECTED]"
_______________________________________________
Eap-bugs mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-bugs
