I don't know how their IDEs were advertised to you or how large the codebases you work on are.
I get fast enough autocomplete (sub second), and full line completion just fine, and I never use/buy top of the line systems. (using a midrange ~2020 thinkpad).
But I'm in a similar place as the comment you replied to. Unless they start focusing again on improving they existing product line, next year I might not renew my licenses anymore.
Before AI took over, I was following closely their release notes and announcements because there where on the right path on improving experience.
What makes their IDE look bad is their indexing process, during which it is slow and completions will not show up. If you know about this quirk you know where to look for it (it's visible in the status bar), and know what triggers it (dependencies installation and such). After so many years, I really feel the solution for that is pretty "simple", "just" run the indexing on a snapshot that is not shared with the running instance and swap out indexes when done.
I know about the indexing, marking directories correctly so as not to trigger reindexing etc etc.
Since i work on a couple dozen services in a monorepo in a few languages, no amount of heap memory or CPU will be enough.
One days its the grapqhl plugin, the next day its typescript type inferrence, then something with rust, it just never stops. Sometimes even the golang operations are slow.
Its all just monorepo issues, but i expect my IDE to be able to handle a monorepo, all other IDEs work without issue (and are inferior in functionality sadly)
I get fast enough autocomplete (sub second), and full line completion just fine, and I never use/buy top of the line systems. (using a midrange ~2020 thinkpad).
But I'm in a similar place as the comment you replied to. Unless they start focusing again on improving they existing product line, next year I might not renew my licenses anymore.
Before AI took over, I was following closely their release notes and announcements because there where on the right path on improving experience.
What makes their IDE look bad is their indexing process, during which it is slow and completions will not show up. If you know about this quirk you know where to look for it (it's visible in the status bar), and know what triggers it (dependencies installation and such). After so many years, I really feel the solution for that is pretty "simple", "just" run the indexing on a snapshot that is not shared with the running instance and swap out indexes when done.