3 ms·

IS this new UI going to solve slow indexing problem? I mean, real problems, the ones that really block our work?

kmlx 4y ago
is the new UI somehow blocking solving the problems that you mentioned? no. companies can work on multiple things at once.
- dmitriid 4y ago
  People working on the new UI are not working on other products. These are not the same people who work with indexing, but these could be people who work on decoupling UI code etc. while indexing is improved.
throwaway2037 4y ago
Zero trolling. Can you give a real world example of slow indexing? If you work in a /more/ dynamic language like Python, Perl, Ruby, JavaScript, it is very difficult to write a fast, accurate indexer. However, for /more/ strictly-typed languages like C, C#, Java, Scala, it is much easier to write a very fast, accurate index. (Leave aside C++ as it is so insanely context dependent, but LLVM has made amazing work of it.) Some anecdata, three times in my career, I have worked on massive 1M+ line of code Java projects -- single repo. The initial Apache Maven download of dependent JARs plus indexing might take one hour or so. After that: Lightspeed. Yes, I do agree: When you are forced to invalidate your indexes, the next restart is painful. More anecdata: One of my current projects is Python 3+. The indexing is much slower and less accurate. Plus, we use lots of binary libraries (compiled native code), which seems to trigger indexing on each restart. But whatever, get a 5GHz machine, give IntelliJ 16GB of RAM and let it run. In 2022, are there any serious alternatives besides a Titanic-sized IDE for enormous complex codebases? I don't see any that average developers (myself) will use. Last point to mix big IDEs with C++: Visual Studio (as much as a cringe writing anything positive about Microsoft) is a phenom platform. For years, it absolutely dominated C++ IDEs. IntelliSense was mind-blowing in C++ and force multiplier that was unmatched for many, many years. It is still very impressive to me. I am sure they feel JetBrains' CLion biting at their heels!
- albertopv 4y ago
  I work daily on a java 8 project with about 3k files, about 5k classes. Small in comparison. When I have to rebuild indexes it takes about 10 minutes on a intel 12th gen w/ 32GB RAM, I configured Idea jvm to use 8GB RAM. It happens quite often when I have to add a dependency, somehow Idea project file get out of sync and doesn't update anymore. When opening the project it takes about 1 minutes before being usable. Every time. I basically keep the project opened just in case. I use Idea every day for about 60 different projects on java, kotlin, python, typescript, groovy... Idea is great, its features are much better than Eclipse or vscode, but with the latter I wouldn't have to wait so long when opening projects. Jetbrains want to change UI? Fine, but as a paying customer I would like other things fixed, people working on UI is not working on other fixes to do.
michaelcampbell 4y ago
That's what a maybe once per day coffee break is for. Once indexed on the rare occasion I have to actually reboot or restart JetBrains products, I don't think I can recall ever having noticed indexing after that.

kmlx 4y ago

is the new UI somehow blocking solving the problems that you mentioned? no. companies can work on multiple things at once.

dmitriid 4y ago
People working on the new UI are not working on other products. These are not the same people who work with indexing, but these could be people who work on decoupling UI code etc. while indexing is improved.

throwaway2037 4y ago

Zero trolling. Can you give a real world example of slow indexing? If you work in a /more/ dynamic language like Python, Perl, Ruby, JavaScript, it is very difficult to write a fast, accurate indexer. However, for /more/ strictly-typed languages like C, C#, Java, Scala, it is much easier to write a very fast, accurate index. (Leave aside C++ as it is so insanely context dependent, but LLVM has made amazing work of it.) Some anecdata, three times in my career, I have worked on massive 1M+ line of code Java projects -- single repo. The initial Apache Maven download of dependent JARs plus indexing might take one hour or so. After that: Lightspeed. Yes, I do agree: When you are forced to invalidate your indexes, the next restart is painful. More anecdata: One of my current projects is Python 3+. The indexing is much slower and less accurate. Plus, we use lots of binary libraries (compiled native code), which seems to trigger indexing on each restart. But whatever, get a 5GHz machine, give IntelliJ 16GB of RAM and let it run. In 2022, are there any serious alternatives besides a Titanic-sized IDE for enormous complex codebases? I don't see any that average developers (myself) will use. Last point to mix big IDEs with C++: Visual Studio (as much as a cringe writing anything positive about Microsoft) is a phenom platform. For years, it absolutely dominated C++ IDEs. IntelliSense was mind-blowing in C++ and force multiplier that was unmatched for many, many years. It is still very impressive to me. I am sure they feel JetBrains' CLion biting at their heels!

albertopv 4y ago
I work daily on a java 8 project with about 3k files, about 5k classes. Small in comparison. When I have to rebuild indexes it takes about 10 minutes on a intel 12th gen w/ 32GB RAM, I configured Idea jvm to use 8GB RAM. It happens quite often when I have to add a dependency, somehow Idea project file get out of sync and doesn't update anymore. When opening the project it takes about 1 minutes before being usable. Every time. I basically keep the project opened just in case. I use Idea every day for about 60 different projects on java, kotlin, python, typescript, groovy... Idea is great, its features are much better than Eclipse or vscode, but with the latter I wouldn't have to wait so long when opening projects. Jetbrains want to change UI? Fine, but as a paying customer I would like other things fixed, people working on UI is not working on other fixes to do.

michaelcampbell 4y ago

That's what a maybe once per day coffee break is for. Once indexed on the rare occasion I have to actually reboot or restart JetBrains products, I don't think I can recall ever having noticed indexing after that.