lsp-ui VS for-win

Emacs has code peek.

With lsp-mode it has that little window: https://emacs-lsp.github.io/lsp-ui/#lsp-ui-peek

Personally I use eglot with consult which temporarily switches the entire buffer to do the "peek" functionality rather than popping up a tiny window: https://github.com/minad/consult

I couldn't reproduce it with my setup. Just for the reference, I use Doom ba35f12be with Emacs 29.0.50 76b7a5936 on Debian 10. Specifically, lsp-mode 68bdac0f8, lsp-ui d8cce7dc1. I use monospace Iosevka TTF font for both italics and regular faces.

rustic + lsp-mode + lsp-ui leads to a pretty slick IDE-like experience for Rust. All of these should work pretty okay out of the box!

I think you should be customizing LSP-UI specifically for the grey text issue, but I haven't used it recently enough to remember: https://github.com/emacs-lsp/lsp-ui

Fifth thing: Bricker of Windows

https://github.com/docker/for-win/issues/1549

Still pissed my HP Windows laptop was bricked from it a few months ago. I’ll never use it for anything.

I use containers on Mac and Windows for development (and we deploy on linux). Docker for Mac is _unusably_ slow in my experience. The VM that it runs is a giant resource hog and a battery hog, and doesn't support ipv6 [0] Docker Desktop itself is (another) resource hog, wildly buggy, and painfully slow. It's the epitome of "shitty electron app".

On windows, docker desktop has all of the same issues as it does on mac. Docker's concept of volumes and file permissions on windows are nonsense. Windows updates and Docker Desktop regularly decide to disagree, [1] It's networking support interferes with other applications (like OpenVPN and the Xbox Game Center) [2].

[0] https://github.com/docker/for-mac/issues/1432

[1] https://github.com/docker/for-win/issues/599

[2] https://github.com/docker/for-win/issues/1976

I have a GitHub post here I made that goes into more detail: https://github.com/docker/for-win/issues/13320

possibly related to https://github.com/docker/for-win/issues/13324 ?

> FWIW, when denying the request to wootric, the docker daemon crashes.

A yes, this about fits the standard of engineering I've come to expect from Docker.

Anyway, I couldn't find any references too "woocentric" anywhere in the code; looks like this part isn't open source? I did find this other issue: https://github.com/docker/for-win/issues/12718 with a comment from May 2022:

"At some point we found out that bugsnag was actually sending a «session creation» request of some sort when initialized, even if no crash was actually being reported. We believed we had fixed that, but I just checked with a MITM proxy and it appears to have regressed… There may be some other services doing something similar without us realizing (wootric, …).

We have created a ticket in our internal backlog to review all this."

Docker Github issue

I ran into this error ( no matching manifest for linux/amd64 in the manifest list entries ), so I tried again on my Windows machine. But then I realized that Docker on Windows actually just runs on WSL2, and it's technically Linux as well! Supposedly, I can switch to Windows containers by clicking on "Switch to Linux container...", but I guess apparently not on Windows 10 Home?? https://github.com/docker/for-win/issues/9701