I disagree. It was a good read.
386 karma · joined May 24, 2011
You can run the following to check if you have the malware in your dependency tree:
`rg -u --max-columns=80 _0x112fa8`
Requires ripgrep:
`brew install rg`
https://github.com/chalk/chalk/issues/656#issuecomment-32668...
- Using the iPhone to scan documents from Finder has recently stopped working on the second scan. I need to restart my phone to get it to work again.
- iPhone mirroring is terrible: laggy, UI glitches, drops click events, scrolling is a nightmare. This is when it actually even manages to connect.
- Often, with Airpods on, lowering the volume, shutting down the iPhone display and putting it in my pocket quickly enough will entirely turn off volume. If you happen to increase the volume instead, you'll get blasted with maximum volume in your ears.
- Use vertical tabs on Safari for one day. You'll see it actually crash a few times. Not to mention the UI glitches. - Open the App Store on macOS. It first opens empty, then the UI controls show up, then it flickers the entire UI. I am convinced it's a Web app.
- In System Settings, most of the sections you click have a delay in rendering. Nothing feels snappy in that app. I can actually click 3 sections quick enough for the second to never even be rendered.
- Sometimes dragging an application from the Dock popup menu into the Trash does nothing, even though it appears to have worked. I often find that it wasn't deleted at all, that I have to open Applications folder in Finder and hit Cmd-Backspace to delete it.
[0] https://github.com/microsoft/vscode/tree/main/cli
[1] https://github.com/microsoft/vscode/tree/main/src/vs/server
VS Code dev here. Would you like to share that list of severe bugs? Also, can you clarify what exactly isn't open-source in the entire VS Code with SSH and devcontainers flow? It's disheartening to read this, knowing that this simply isn't true.
[0] https://www.seriouseats.com/quick-caramelized-onions-recipe
We'd love to hear more about the lack of documentation you're referring to. It's definitely a solvable problem. Could you create an issue so we address the problem? https://github.com/microsoft/vscode/issues
Also on
> But petty gripe: please kill the git username/password fields when I git clone a private repo over HTTPS in the console. I don't like being aggro towards what other devs find cool, but I think hijacking a CLI with an extension incredibly annoying. And I can't find a way to disable that specific "feature" without disabling all of the git integration, which I use all the time.
This can be disabled with the `git.terminalAuthentication` setting.
It uses a fork of gifsicle compiled in WASM to produce highly optimized GIFs really fast. It supports trimming and cropping the end result.
Let me know what you think!
We use deemon in VS Code to improve development and minimize downtime. As developers we like to run our build from within VS Code in order to get tasks support and get semantic errors in the Problems view. But since we often need to reload VS Code, this would kill the build task and we would need to start the build all over again which takes roughly 2-3 minutes to warm up. With deemon we are able to run the build from inside VS Code as a build task and later reattach to the same `yarn watch` process, even if we quit VS Code or reload it.
Deemon works similarly to running your build tasks inside tmux, detaching from it and later reattaching, but with a simpler interface. Instead of `yarn watch`, one runs instead `deemon yarn watch`.
Adopting it to the VS Code repo was as simple as adding a dev dependency to `deemon` and adding a new `watchd` script: https://github.com/microsoft/vscode/blob/4e8408d4c4dafae88f7....
You can try it out right now using `npx`: simply run `npx deemon BUILD COMMAND` (eg. `npx deemon yarn watch`). `Ctrl-C` will detach from the background process. Run the exact same command to reattach. `Ctrl-D` will terminate the background process.
Glad to answer any questions!