vscode

Hi, I'm part of the VS Code team. We have a page on our wiki that describes in a fair amount of detail how we structure iterations: https://github.com/Microsoft/vscode/wiki/Development-Process

I like VSCode a lot. The only reason why I sometimes switch to other alternative is the multi-file search results. When the fix this, I will be a happy camper: https://github.com/Microsoft/vscode/issues/63465

expect for a feature that keeps a lot of people on other editors (recordable macros) https://github.com/Microsoft/vscode/issues/4490

There are some warts, but it seems nice from afar. The biggest wart is/was the "FUCK FUCK FUCK" git clean vs git reset UX error: https://github.com/microsoft/vscode/issues/32405 . This is a fantastic demonstration of why i exclusively use git from a command prompt -- i know what will happen and nobody's going to reinvent terms to put on buttons that just confuse me. In my life: - I'm committed to emacs for org-mode and LaTeX editing and daily use. - I paid for sublime so i will use it -- and multiple cursors everywhere is a boon for quick and dirty data munging. - I write serious python code in pycharm. - I write serious c# in full blown Visual Studio

sublime is still much faster and more stable than anything else... the only time i switch to a jetbrains editor is when i need something heavy like java or android or flutter... for example: https://github.com/Microsoft/vscode/issues/63542 just look at the difference between sublime and vs code. the new ui in vs code also made things slower: https://github.com/Microsoft/vscode/issues/60419

Ah, I checked there seems to be an extension that lets you write macros in a JSON file: https://marketplace.visualstudio.com/items?itemName=geddski.... But there seems to have been no movement on this request for a functional macro feature: https://github.com/Microsoft/vscode/issues/4490

> "we have an extension for this file type!" There's a setting for disabling that, arguably these sort of annoyances should be easier to eliminate though. IMHO the plugins per-se are one of VSCode's strengths, you can find plenty of high-quality ones, and the APIs are good enough that making your own is overall a pleasant experience. What sucks is the Marketplace [1]: 1. searching is basically broken 2. the downloads count, and therefor the ranking system, is skewed towards extensions publishing lots of updates. [1] https://github.com/Microsoft/vscode/issues/42890

> that's not maddeningly complex I'm not sure what's complex. Adding one more option "Triaging" here[0] doesn't seem complex. I'm working at VS Code and now we are trying to make a bot that would add a label if someone (from a whitelist) types `/label bug` (same for marking duplicates). The fact that we have to go this far for letting community contributors assign labels to issues is more maddening to me. See an example here: https://github.com/Microsoft/vscode/issues/62016#issuecommen.... [0]: https://user-images.githubusercontent.com/4033249/47674432-8...

Any examples of well-structured jest/mocha/<insert test framework> projects? Any typescript code base you would read to enhance your testing skills? For instance, vscode: https://github.com/microsoft/vscode

Hi It's Kenneth from VS Code. We have looked into this, and haven't found an intentional change that should change your opt-out settings. This shouldn't happen. We have two theories: 1) Your settings file was deleted, which means that you would have lost all of your settings, and not just the telemetry setting. This can happen if the AppData or ~/Library/Application Support was cleaned up. 2) One of your installed extensions updated the settings either accidentally or on purpose. This would require further debugging, and a list of your installed extensions. To help debug this further, it would be great help if you could open an issue on Github, https://github.com/Microsoft/vscode/, with more details about your OS, VS Code version and installed extensions, so we can figure out what happened. Thanks! /k

> Stop using sha256(MAC address) for telemetry machine ID #8688 https://github.com/Microsoft/vscode/issues/8688

Oh, I appear to have misread your comment as "why developers move to Electron for their apps". The reason why developers, myself included, migrate to VSCode is really simple: because it's the best all-around cross-platform IDE right now for many scenarios, and because it has a thriving extension ecosystem to tailor it further. But it is that in spite of being written in Electron, not because of it. If Microsoft announced that it is being rewritten in Qt tomorrow, I'd be ecstatic. Just to give you an example of what kinds of issues using web tech for desktop-like experience can cause: https://github.com/Microsoft/vscode/issues/22900 (Yes, I'm well aware that they fixed it. The point is that the offending code needed to be written in the first place. A native desktop app using 13% of the CPU to render a blinking cursor would be considered a

"MIT allows this" is a red herring. Even if the source was GPL, if Microsoft own[1] it, they can do whatever the hell they like with it. [1] own or own enough rights. Before any PRs are accepted, you need to sign the CLA https://github.com/Microsoft/vscode/wiki/Contributor-License...