Please, slow down with versions of Ariadna! Follow
I think that i must alert the team to the danger, but maybe i just have a panic.
I look at intellij way since build 527. I this time IntelliJ progress was slow and most stable (closely one new version per week or two). Now i see that it go like a shot, too much fast.
Now we can get new build closely everyday, but not one of this is not stable.
The picture is like that team management reappraise power of programmer's team, as we can see to look at line of last bulds (since 640). 20 builds and no one significat feature, just look and feel and, maybe, GLUE. Even a old high priority defects not fixed.
For example, the JSP analyser still not stable, still have more limitation comparing to Java coding.
I not want to lash your work, just i want to help IntelliJ management to make a decision. It's just a point of view, it's only my point of view, just a look from out side on progress action.
I guess that now IntelliJ must take a break, reorder your power, reingineer the code, throw out not needed features and fix ALL not fixed bugs in current build or in previos builds. Maybe i come to panic, maybe this. But i realy have a fear about IntelliJ bogged down in "tar pit", in bugs, new technologies and project times etc.
Thanks for your attension,
i just hope that i fall in panic...
Please sign in to leave a comment.
As a software developer, I admire the project team's ability to develop new features at this kind of pace without making the software unusable. I think IntelliJ management has been too ambitious on adding new features.
Compared with ver 2.6, IDEA (bld 661) has huge number of new features that I couldn't resist. However, it has become much more resource hungry and less stable.
I hope IntelliJ management can give the development team some time to cool down and sort things out. Personally, I don't mind to wait a few more weeks for the final version, but I understand that IntelliJ management might have different concerns.
I look forward to a stable efficient ver 3. (For IntelliJ management, you can look forward to our order forms too. :))
I can't use the build 660 anymore... It destroy my project again file, and it not stable with JSP. I moved back to 650, but i think that in little time, i'll moved to 648. I choose 650 only for pmy plugins still worked in IntelliJ.
Please, fix these bugs! Thanks
I also think that this point is extremly true. IntelliJ IDEA 3.0 is becoming
really feature packed and it will definetly outstand all the other java ide
in the market. No doubt that any person who puts their hands on IntelliJ
IDEA 3.0 will hate to put their hands on any other ide. At this moment I am
also just excited with this product too. But as Chen Nan just mentioned, hey
man, cool down a bit and give those programmers a break. Take them out for
some yummy lunch. Just slown down a bit and concentrate on stabalizing the
IDE, as currently there are lots of performance issues that many have
I haven't found a version useful since 642. However, I have been reluctant to install anything until I see bugfixes (perhaps regarding perf) that warrant a look. Short of that, it looks like I may be done testing this product until it provides some value to me (v3 release?).
I'll take the counterpoint then...
I download and install every released build and have found 95% of them completely usable.
I am currently using #661 in a high volume team production environment and have been mostly pleased with features and performance.
Again to balance out this thread, I agree. I have no recent complaints whatsoever with the eap builds. But even if I did, everyone please remember these are EAP builds, the point is less to give us all super-stable development environments and more to fully test the code. Of course, we've gotten used to super-stable code so when that falters we get in trouble because we're depending on it.
So, keep perspective. As for me, I've honestly had zero problems since one build over a month ago where my favorite feature (ctrl-shift-n to open files) broke. But a few days later the next build fixed it.
One caveat: I do very little if any jsp work. Perhaps that is where the instability lies. cheers...
I understand that this is a pre-beta project and that instability is to be expected, however, in order to have the general public supply QA for your company (which works very well for this type of product!) then you probably need to supply something that is compelling enough for them to run.
Good to see that it has worked for you -- and probably others. But until the performance picks up a bit I'm done running off the tip. If the quality of the releases were similar to the way they were, then Ariadna would be 'tested' by more of the general public.
I would consider it a panic. Here's why:
1) if you had participated in our previous EAP releases, you would realize
it's a normal speed for the team
2) if the builds come out very often (e.g. every day, which rarely happens
btw) it means they contain important bug fixes that make the previous build
unusable for some people
3) latest builds contain almost no new features becauses there is a thing
called a feature-freeze which ought to be done some time before releasing
4) there are no open bugs in the Tracker about some problems with the JSP
5) if the IntelliJ management would be wrong, they would not have managed it
to get such a great product
"Alexey Efimov" <email@example.com> wrote in message
slow and most stable (closely one new version per week or two). Now i see
that it go like a shot, too much fast.
team, as we can see to look at line of last bulds (since 640). 20 builds and
no one significat feature, just look and feel and, maybe, GLUE. Even a old
high priority defects not fixed.
comparing to Java coding.
make a decision. It's just a point of view, it's only my point of view, just
a look from out side on progress action.
reingineer the code, throw out not needed features and fix ALL not fixed
bugs in current build or in previos builds. Maybe i come to panic, maybe
this. But i realy have a fear about IntelliJ bogged down in "tar pit", in
bugs, new technologies and project times etc.
1. I disagree - spead of development spinup faster now, what 3-5 monts ago.
2. Yes is difficult problem. IntelliJ now have a critical bugs, and you must fix it quickly (this is OK). But also, you add new features (and they give new bugs), etc...
3. In EAP no builds named "latest", i wrong? Every new build have new features, and bug fixes.
4. Ok i will post again bugs :)) All my bugs was closed with unintelligible description (as not repeaded, mustined project root and path, etc). But now i can say about:
JSP after check out (clear read only attribute) the JSP file is ALL in red :). Type a space that backspace - all OK.
Taglibs TEI not working
Refactoring not complite (ALT+Insert, for example)
Some times on some files Internal Error on open (no matter read only it or not)
Base page extends?
Jars from WEB-INF/lib and classes from WEB-INF/classes?
5. Yes, you absolutely right! :)
PS. Don't take it very much to heart. I guess, that IntelliJ now is best IDE product of all other on market. Then - management work right. I just say may impression on so fast development speed. Maybe it's a normal process, i don't know. Thank you otherwise for good work!