This ‘intelligent’ code completion completes wrong in 99% of all cases and I have to delete/change half of the completed. What is this good for?
// @jetbrains
This ‘intelligent’ code completion completes wrong in 99% of all cases and I have to delete/change half of the completed. What is this good for?
// @jetbrains
I turned it off in the options. It was too much energy for me to keep dismissing, parsing, or correcting.
Even with it off, the autocomplete has been made less useful from previous years.
Even worse, many other features, like highlighting and syntax parsing do not work as well with the AI turned all the way off. I finally found, with trial and error, a balance I could live with (allow it to run in background but limit what it displays to me)
The only reason I have not permanently rolled back to the best version before last year is because of language and docker changes.
But, I am ready to jump ship
and that fact really destroyed my year-long appreciation of the engineering at JetBrains.
also you can no more auto-complete to symbols defined elsewhere in your project. what a joke.
I have used them for php, ruby , database and c the last decade; spent thousands of hours using their editor.
While I had several issues and reported bugs during that time, I had no breaking changes.
Then last year I simply did not update at all. I rolled back to the last version in 2023 because the bugs from the new ai were so bad, I could not even copy paste without pasting as text only. Dozens of other new issues. Many of them, I think, only happened with large code bases.
I lost confidence in them, I am still using the last version of last year, have not looked at the bs of latest version.
Their code base was fragile, they always had issues after a major upgrade. But the new AI layer probably caused issues that will not be resolved, never mind the nonsense of whatever marketing is dictating this year