IDE dilemma: New features (e.g. AI) vs. basic usability - Keep the balance!
Hi there
I am using PyCharmPro for a long time and it's a valuable tool in my chain. (V 2026.2 on W11). However I am a bit concerned about the future direction:
I understand that the AI race is on and Jetbrains is in it - willingly or not. Adding AI features should not compromise the basic look and feel such as.:
- sluggish response to editing changes, sometimes little hangs, cursor focus barely responsive
- code completion - in the past - was a great help. Right now it is more of a nuisance. The effects of tab (review/complete/revert) are confusing. I know there is this hint displayed. Overall it delays me in my work. For me smooth editing is paramount.
- “This view is read-only” / “Nothing there” drives me crazy. How to get out??
Now about AI:In the past (V 2025.x) I have used the assistant for refactoring, creating smaller code segments. And that worked well. Now I tried this
“Suggest fixes for the major warnings in module xx.py. Let me accept/reject for each suggestion” Codex and Junie never delivered an answer. I cancelled after several hours of waiting. This is not a big deal for me. I just let you know.
So hopefully keep the balance between a premium look-and-feel of basic features and the add-on of new things. I am aware of the dilemma.
Please sign in to leave a comment.
Thanks for the feedback. Let's address them separately
"This view is read-only" means the editor is refusing input, and the way out depends on where you see it:
- In a diff or a proposed-change view, the hint is itself a link. Click Enable editing or Switch to editing in the hint text.
- In a file with the read-only attribute set, use File | File Properties | Toggle Read-Only Attribute.
- In a library file under site-packages, it is read-only by design. Open your own copy of the code instead.
Which of the three is it? Post a screenshot. If both messages show up in a panel that Junie or Codex was filling, let me know
The Tab behavior you describe comes from AI inline completion and Next Edit Suggestions. Both live at Settings | Editor | General | Code Completion | Inline. Turn them off there. Tab returns to its previous meaning, and classic completion is unaffected.
That same switch is the cheapest test for the editing lag. Cloud completion runs on the typing path. Turn Inline off and work for an hour. Tell me whether typing feels normal again. That either implicates it or rules it out before anyone reads a thread dump.
Codex and Junie failed the same way, which points at the shared agent layer rather than at either agent. Run Help | Collect Logs and Diagnostic Data and open a new YouTrack case with the logs for further investigation
Miguel, thanks for your quick reply.
read-only view: I put the cursor on the def set_pano_md and selected “write documentation” from the context menu.
So I guess this a proposed-change view. Except for the Revert arrow I see no hint, link or else. Please advise.
I updated the settings and will keep you posted about the effects.