[kaba0]

I honestly don’t see it at all. It is RAM-hungry, but that is quite inherent with any sort of tool that has to do various fast lookups in large repositories — that has to be stored in-memory, regardless of programming language.

But if you do give it like 2GB of RAM at the least, it is very smooth (unfortunately it used to have a very low max memory setting for a long time). Java is good at handling dynamic loading, you don’t really pay for any feature you don’t use, they don’t even get class loaded.