9
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Mar 2026
9 points (100.0% liked)
JetBrains
477 readers
2 users here now
A community for discussion and news relating to JetBrains and its products! https://www.jetbrains.com/
Related Communities
- !aqua@programming.dev
- !clion@programming.dev
- !datagrip@programming.dev
- !dataspell@programming.dev
- !fleet@programming.dev
- !goland@programming.dev
- !intellij@programming.dev
- !phpstorm@programming.dev
- !pycharm@programming.dev
- !rider@programming.dev
- !rubymine@programming.dev
- !rustrover@programming.dev
- !webstorm@programming.dev
Copyright © 2000-2024 JetBrains s.r.o. JetBrains and the JetBrains logo are registered trademarks of JetBrains s.r.o.
founded 2 years ago
MODERATORS
Honestly, that was a good move. JetBrains used to have many actions as popups that prevent reviewing the source code and the project in general while e.g. figuring out a commit message.
Wat? The popup has code right in the window. If I wanted VSCode, I'd use VSCode and their shitty design.
Yes, but only the diff.
What if my change is one parameter in a function call ? The most meaningful aspect of the change lies in the definition of said function, that may not be part of the diff.
What if my change is related to another commit that I want to reference in my message ? I'd have to close the dialog, copy the commit ID, and reopen the dialog.
For an infinite amount of reasons we rarely foresee, blocking states are never good.
Same.
But this one thing isn't part of said shitty design.