bpasero

6 ms·

1. 1.▲
   by bpasero 9mo ago

   We maintain a single VS Code setting that allows you to opt out of the AI features provided in VS Code: "chat.disableAIFeatures" (see also: https://code.visualstudio.com/updates/v1_104#_hide-and-disab... ). If
2. 2.▲
   The Lab of the Future(news.microsoft.com)

   5 points by bpasero 3y ago|0 comments
3. 3.▲
   Is the Big Bang Cycling Through Hidden Time? (2015)(space.com)

   2 points by bpasero 4y ago|0 comments
4. 4.▲
   An almost perfect rsync over SSH backup script(blog.zazu.berlin)

   199 points by bpasero 5y ago|126 comments
5. 5.▲
   GitHub adds ability to search issues by label using logical OR(twitter.com)

   2 points by bpasero 5y ago|0 comments
6. 6.▲
   The State of the Octoverse(octoverse.github.com)

   6 points by bpasero 7y ago|1 comments
7. 7.▲
   JIT-Less V8(v8.dev)

   337 points by bpasero 8y ago|116 comments
8. 8.▲
   Modernizing Node.js with idiomatic JavaScript(medium.com)

   1 points by bpasero 9y ago|0 comments
9. 9.▲
   Performance Impact of Spectre and Meltdown Mitigations on Windows Systems(cloudblogs.microsoft.com)

   75 points by bpasero 9y ago|37 comments
10. 10.▲
    by bpasero 9y ago

    VS Code will never close a buffer that has changes (e.g. is dirty). In this case, the buffer was closed because the editor was not dirty. You can change this by configuring "workbench.editor.closeOnFileDelete": false
11. 11.▲
    Code: Introducing Insider Builds(blogs.msdn.microsoft.com)

    2 points by bpasero 11y ago|0 comments
12. 12.▲
    Visual Studio Code 0.3.0(code.visualstudio.com)

    8 points by bpasero 11y ago|0 comments