171–180 of 186 posts
Earlier quoted context omitted.
But how many of that input should have been from internal testing instead of users after the rollout?
Microsoft don't have internal testing. They get the devs, who already know the code, to see if it makes sense. And woe betide you if you disagree with the PM!
That's a no-go.
Earlier quoted context omitted.
Makes me glad I stuck with vim. I do pretty much the same thing as you, what made you use vscode in the first place? What are the coolest features in your context?
VS Code has a strong plugin ecosystem, and is built around plugins. You can find plugins for everything, so whatever linting, code formatting, back end integration, custom renderers, menus, etc you want you can build and plug in if they aren't available already. Beyond that access to a project tree view / definition list toggle on the side, debug code at cursor, context menu options to refactor/find usage/etc, and ea…
The disadvantage is of course that it's not integrated, but the advantage is that my editor never crawls to a halt.
Earlier quoted context omitted.
And same for Emacs, great LSP and DAP integration.
I heard someone say gdb works great with emacs but I never had a good experience with C++ in neovim. I asked friends and they all say they use a second editor to debug which is part of why I bothered to do this
VSCode is still on the top of accessibility, so when you can claim that you work perfectly with a screen reader, you will convince me to switch.
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.
VSCode is still on the top of accessibility, so when you can claim that you work perfectly with a screen reader, you will convince me to switch.
and yet, wacom pens are not supported. I need it to help with RSI
Do you have a preferred com channel?
Earlier quoted context omitted.
VS Code has a strong plugin ecosystem, and is built around plugins. You can find plugins for everything, so whatever linting, code formatting, back end integration, custom renderers, menus, etc you want you can build and plug in if they aren't available already. Beyond that access to a project tree view / definition list toggle on the side, debug code at cursor, context menu options to refactor/find usage/etc, and ea…
Seems like a lot of training wheels to me. I mean linting, formatting can be done by piping buffer into external programs. Not sure what back end integration means but you can accomplish a lot with just bash+vim+tmux (or zellij which I recently switched to). The disadvantage is of course that it's not integrated, but the advantage is that my editor never crawls to a halt.
The 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…
Sometimes it's easier to start from scratch than figure out how some storied monolith works
Tldr: avoid rewriting software. Most likely the gigantic monolith got big because because of all the business logic encoded in there.
Or just use Vim. Not sure I understand the obsession with VSCode.