Earlier quoted context omitted.
Not having an exclusion for a development directory is like using a 10yo machine or using a laptop without the power brick connected: it’s basically leaving half the perf on the table. Still, a second seems a bit much for a real-time scan.
Clearly you do not work for corporate America. Any amount of performance loss is acceptable to check a security compliance checkbox somewhere.
I can't stand using VSCode so I wrote my own
131–140 of 186 posts
Re: I can't stand using VSCode so I wrote my own
#132I use vscode for doing devops-y things (Terraform, OpenTofu, JSON, python, yaml, txt, dockerfiles, etc.) and sometimes the way it bogs down my system drives me bananas. I'll punt to Sublime Text on occasion and use it for a few days, but then start running into papercuts in various places and have to go back to vscode. I so, so wish there was a better way to do this without fucking electron.
Talk about something as simple as code folding. VsCode does the best job of it I know, and yet the other day it simply stopped working properly for pure JS code, not sure if that's because Microsoft prefers we use Typescript instead of JS. Nothing I did fixed it, and something as simple as that messes us with your workflow. And then I remember that VSCode has introduced a recent bug where after you collapse a piece of code, the file jumps to a weird location. And other paper cuts too numerous to mention, which seems to appear and go randomly
So I tried Sublime text again, only to find that "Collaspe All" does not work properly by design, whatever the reason for that. And it still insists on making many things un-ergonomic.
So I try Webstorm again, and after a few tweaks, it seems to do pretty much what I want. But, it is dog slow, and the display of collapsed comments is a bit weird. I start thinking of writing my own code editor...
My point is pretty much this: The various advanced code editors spend so much effort on advanced features, but they forget that the basic must work flawlessly for most devs to have a good experience. I wish they focused on the basics again to make common sue cases frictionless.
Re: I can't stand using VSCode so I wrote my own
#133The author could try forking and patching VSCode to fix the annoyances manually. Years ago I had an issue with VSCode: it was missing a small feature that was very important to me, with the GitHub issue stuck in limbo. I ended up going into the source and implementing the feature myself. It took a few hours after bugfixing, I think the fix was ~100 LOC. Then I used the locally-built version. I recall building took a…
Re: I can't stand using VSCode so I wrote my own
#134The author could try forking and patching VSCode to fix the annoyances manually. Years ago I had an issue with VSCode: it was missing a small feature that was very important to me, with the GitHub issue stuck in limbo. I ended up going into the source and implementing the feature myself. It took a few hours after bugfixing, I think the fix was ~100 LOC. Then I used the locally-built version. I recall building took a…
Re: I can't stand using VSCode so I wrote my own
#135Earlier quoted context omitted.
Not having an exclusion for a development directory is like using a 10yo machine or using a laptop without the power brick connected: it’s basically leaving half the perf on the table. Still, a second seems a bit much for a real-time scan.
Under Windows 11, a "dev drive" can also make a big difference. https://learn.microsoft.com/en-us/windows/dev-drive/
Re: I can't stand using VSCode so I wrote my own
#136The author could try forking and patching VSCode to fix the annoyances manually. Years ago I had an issue with VSCode: it was missing a small feature that was very important to me, with the GitHub issue stuck in limbo. I ended up going into the source and implementing the feature myself. It took a few hours after bugfixing, I think the fix was ~100 LOC. Then I used the locally-built version. I recall building took a…
Re: I can't stand using VSCode so I wrote my own
#137The author could try forking and patching VSCode to fix the annoyances manually. Years ago I had an issue with VSCode: it was missing a small feature that was very important to me, with the GitHub issue stuck in limbo. I ended up going into the source and implementing the feature myself. It took a few hours after bugfixing, I think the fix was ~100 LOC. Then I used the locally-built version. I recall building took a…
This is the way. Anytime I have had issues with an open source project, creating a PR even if it's not great will often have it taken over, improved and merged.
Re: I can't stand using VSCode so I wrote my own
#138Re: I can't stand using VSCode so I wrote my own
#139The only thing that annoys me about VS code is that Microsoft decided to call it visual studio, which means if I search for help for a problem with actual visual studio I end up with vscode suggestions. Id like to know why ms thought this was a good idea.
Microsoft has been flopping with their naming recently... Case in point, Copilot. GitHub Copilot, Microsoft Copilot, Office 365 Copilot... all different products for different uses. Still can't figure out why they didn't follow through with Cortana being the OS copilot name and retired it. It was such a perfect fit. My only guess is that they are worried about anthropomorphizing the AI.
I can't figure out why they didn't use it as an opportunity to bring back Clippy.
Re: I can't stand using VSCode so I wrote my own
#140When I had a 2 GB laptop lying around, I always wanted a simple text editor with auto-completion etc. (Though only for Python, Linux) After trying KDevelop, Kate, Eric, Sypder etc. I thought I could write my own. I had a simple plugin system in mind, with similar to LSP style features (VSCode was not released that time). The UI was inspired by Blender. Blender has such a fluent UI where you can customize everything.…