Back in the day I switched from Kawa to IntelliJ I think if I remember properly the first version I used was version 2.5, after months of torterous VisualAge usage, a worthy successor to Kawa existed. For many years I stayed with the same platform, namely W2k and had no real problems. VSS support was a mess, but by and large the application was a pleasure to use.
That all changed when I started a new job in September. The operating environment was different and so was the IDE. The switch from Win2K to Linux was mandatory and so too was the rather pathetic Eclipse. IntelliJ and "Develop with pleasure" was replaced with "Disgruntled crashing" and Eclipse wreaked of VisualAge which was no great surprise given the Eclipse project heraldry.
Eventually the team saw the light and we bought IntelliJ 3.5. It had been a few months since I used my beloved IDE, unfortunately during those months IDEA had developed an illness, an illness seemingly that plagued only Linux users. It frequently became lethargic almost dosile if it was minimsed, it behaved like a small kid refusing to startup again if I toggled to a different application. Still despite these less than pleasurable experiences, I devoted most of my time to IDEA and it was better than using Eclipse, though I felt its slogan was more akin "Develop through pain". It seemed that all was not well in the house of Jetbrains, a coup d'etat had been staged, it seemed that users who should have used JBuilder had infested what was an IDE of pure beauty and unquestionable intelligence. Release 4, was delayed month after month. Rumours of a ghastly gui development suite persisted, oh no pray tell, what was becoming of my beloved IDE.
Initially my impression was positive, IDEA no longer became lethargic, she seemed fresh and I had managed to avoid the bloated beast that was the GUI development features. It seemed a symbiotic relationship existed once more. Unfortunately that was short lived, it has come to pass that IDEA no longer is as nimble as she used to be and instead now characterises a bloated obese beast of Gigantour proportions. It sucks all CPU resources, and requires contant killall -9 shock treatment.
Worse still the very users that have made this tool so popular have become ambivalent to the current woes. I want the tool I paid for, namely something that does not kill my machine...
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
10076 jcooper 25 0 488M 175M 176M S 89.4 34.7 27:42 0 java