Re: [67cat] Results from NetBeans 6.7 Community Acceptance survey

by rohitbrai :: Rate this Message:

Yup!

I hope we fix the scanning and error badging issues before the release.

I saw the error badging bug marked as fixed, haven't got a chance to check it out yet. But that was definitely a show stopper and real productivity killer.

Netbeans lags, drastically in performance behind Eclipse and there is no comparison with IDEA. While I think being from Sun, Netbeans should be performance benchmark for all Java applications and not just IDEs. Does anyone use Open Type/Open file features with large projects?

Though I won't consider performance a show stopper, considering the loads of new features we are releasing, we'll soon certainly be put to shame on that.

Doesn't everyone in the community feel that?

Come on guys, stop lying to yourself and face the real thing. We need to improve, If the Netbeans team is too busy releasing features, may be we can pick some volunteers from the community, train them about the platform and the source and let them work on performance improvement. and these can in turn train others and actually build up netbeans as a community project than a pseudo open source project? Eclipse has become so strong owing to involving community in the entire development process and not only for testing.

I know it is Open Source and we have the source and all that stuff, but it is not everyone's cup of tea to on there own go through the huge code base such as netbeans and moreover, there isn't much ROI in it.

Simpler solution, will be switching to Eclipse, which I am inclined to more than ever, considering the Netbean's UML project going the scrap way, Visual Web being scrapped, we might soon loose the edge we have in tooling over the other IDEs.

Yes I say WE, cause Netbeans loosing won't only be Netbean's team loss, but also loss of the community and each and every user who have so much invested in it in terms of knowledge and experience.

I agree with Jiri, that we could have raised the issues earlier, even I am at fault for putting in this mail so late, probably I should have raised it in the survey itself, but if the user base at large has issues, I think it will be decent enough to respect opinion and release a throughly improved build rather than releasing a product for which the "Patch 1" is already defined. That really reminds me of MS Service Packs :D

The NetCAT and CA are not testers vs netbeans team game as we are making it to be here in this and few other mail chains, it is us uniting together with a common goal of "near perfect release". I hope everyone agrees to that.

Regards,

Rohit

The diamond cannot be polished without friction, nor man perfected without trials
http://mytechrantings.blogspot.com

On Thu, Jun 25, 2009 at 5:01 AM, nleck <nleck@...> wrote:

Come on guys. There a numerous people complaining about the project scanning issues.

Here is one movie (http://www.netbeans.org/nonav/issues/showattachment.cgi/83834/200906180201.ogg) showing the performance regression between 6.5 and 6.7

Just from today's nbusers emails

>

> I am trying disparately to be able to, once again, use a project which has had an unfixable "The project XXXXX has a broken platform reference. You have to fix the broken reference and invoke the action again." error. While trying to use 6.7rc3, starting from scratch, I encountered a lock up of the ide while exiting. I've created the issue at

>

> <http://www.netbeans.org/issues/show_bug.cgi?id=167623>

>

> which illustrates the fact that the IDE, seemingly all over the place, is calling into the scanning/indexing code with the AWT-EDT and being blocked by bugs and implementation details of the prolonged locking associated with the cache implementation.

>

> Please vote for this one too so that we can, hopefully get enough documented issues to help the dev team understand the impact of this issue.

>

> Gregg Wonderly

>

and another

>

> Has anyone else noticed this on the recent builds: I'm in the IDE and have a few source tabs in the editor with one active and the methods/fields showing in the Navigator. I do something in the IDE outside the editor window (e.g. do a search or something) and then subsequently double-click on a method in the navigator that is supposed to take me to that method in the currently active editor window. Only it doesn't. Instead, the editor tab seems to "wake up" and refresh the navigator window. If I double-click on the method again, things work again.

>

> I can't reproduce this on demand - either it's occasional or is a sequence I haven't pinned down yet. Because of that, I hesitate to open an issue.

>

> Thnx,

> tom

>

« Return to Thread: [67cat] Results from NetBeans 6.7 Community Acceptance survey