I use Jetbrains IDEs now for 5 years, I’ve used VSCode, Sublime, Atom, Vim, Neovim but I feel like Jetbrains IDEs are just better if you have the RAM to run it.
It’s a setting.
Doesn’t happen
Doesn’t happen
Searchable actions, just search for “encoding” in this case.
That’s an LSP/project mismatch usually just a setting. Most things are supported but worst case you can remove the error.
Happens if you run out of RAM or open a very large file.
So it’s not all bad, but comes with a lot of good such as “invert if statement”, “use template strings” and “extract method” thingies along with a load of plugins.
Agree. I used a ton of different IDEs too and I can say Rider was the least terrible one I’ve used professionally (mostly on Unreal Engine projects, so having the thing not kill itself when trying to compute large, complex codebases for syntax highlighting/autocomplete was a requirement).
Number 3 happens all the time to me when using VSCode with Copilot as autocomplete. Copilot sometimes works, sometimes doesn’t. Also happens a lot when using Pycharm with Python. Sometimes it’s great at autocompleting, sometimes it completely gets lost and has no idea what my Python script is doing.
Number 5 also happens a lot on VSCode + Platformio. It also frequently happens on Intellij IDEA for me, but mostly when I am concurrently running build or test while writing. My crappy work laptop suffers from Windows 11 related performance issues, and when there’s not enough performance available, underlines do get wonky quite frequently.
I also had issue when I was working on a pycharm project back when I was on windows. During setup it asked me “What’s your name?” and my name has a cheeky accent which Windows was decided should be the name of my Home folder. Home folder also has appdata and whatnon so which the build system didn’t expect to have a an accent in the folder path.
I ended up having to create a different folder and link to it then move all the path configurations to that folder link just so I could get imports working.
can also sometimes happen when your workplaces corporate antivirus you can’t uninstall, pause, or change any settings on decides to scan your project files while a build is in progress 🤦🤦🤦
We get the beauty of every file that’s modified
being scanned before the write “completes”. It’s an absolute joy starting a build and watching ~80% of the available compute be consumed by antivirus software.
Or, you know, normal filesystem caching as part of your tool’s workflow.
I use Jetbrains IDEs now for 5 years, I’ve used VSCode, Sublime, Atom, Vim, Neovim but I feel like Jetbrains IDEs are just better if you have the RAM to run it.
So it’s not all bad, but comes with a lot of good such as “invert if statement”, “use template strings” and “extract method” thingies along with a load of plugins.
Agree. I used a ton of different IDEs too and I can say Rider was the least terrible one I’ve used professionally (mostly on Unreal Engine projects, so having the thing not kill itself when trying to compute large, complex codebases for syntax highlighting/autocomplete was a requirement).
I’m so spoiled by searchable settings that it feels like I’m back in the 50s if I actually have to manually click around menus looking for a setting.
Number 3 happens all the time to me when using VSCode with Copilot as autocomplete. Copilot sometimes works, sometimes doesn’t. Also happens a lot when using Pycharm with Python. Sometimes it’s great at autocompleting, sometimes it completely gets lost and has no idea what my Python script is doing.
Number 5 also happens a lot on VSCode + Platformio. It also frequently happens on Intellij IDEA for me, but mostly when I am concurrently running build or test while writing. My crappy work laptop suffers from Windows 11 related performance issues, and when there’s not enough performance available, underlines do get wonky quite frequently.
I also had issue when I was working on a pycharm project back when I was on windows. During setup it asked me “What’s your name?” and my name has a cheeky accent which Windows was decided should be the name of my Home folder. Home folder also has appdata and whatnon so which the build system didn’t expect to have a an accent in the folder path.
I ended up having to create a different folder and link to it then move all the path configurations to that folder link just so I could get imports working.
Oh, you get the benefit of explicit scanning?
We get the beauty of every file that’s modified being scanned before the write “completes”. It’s an absolute joy starting a build and watching ~80% of the available compute be consumed by antivirus software.
Or, you know, normal filesystem caching as part of your tool’s workflow.
Or dependency installing and unpacking…
Or anything actually that touches a lot of files.
Yeah was experiencing that for awhile, a couple of workarounds: