4 ms·

Really? I work across multiple vscode projects (locally), some use dev-containers and others don't. I have never noticed any difference in experience across the

Really? I work across multiple vscode projects (locally), some use dev-containers and others don't. I have never noticed any difference in experience across the two. I have also used them remotely (ssh and using tailscale) and noticed a little lag, but nothing really distracting.

amonith 9mo ago
Most likely a Windows or MacOS user, where docker runs in a linux VM. Optimized as much as possible and lightweight, but still a VM.
- okanat 9mo ago
  No, on Windows it is very quick too. On WSL2 compiling Rust programs are almost as fast as Linux on bare metal. However the files need to live inside the Linux filesystem. Sharing with Windows drives actually compiles slower than native Windows.
  - pjmlp 9mo ago
    You can use dev drives instead, I guess.
    - okanat 9mo ago
      If you are building natively, yes. However the original comment is about Dev Containers which runs under WSL2. If you open a native Windows folder in VSCode and activate the Dev Container, it will use the special drvfs mounts that communicate via Plan9 to host Windows OS to access native Windows files from the Docker distro. Since it is a network layer accross two kernels, it is slow as hell.
      - pjmlp 9mo ago
        That is the beauty of Plan 9's design. :) I haven't tried, but the idea was to map a such a drive into WSL, but I am not sure if it is possible and indeed how much it would help in the end.
        okanat 9mo ago
        You can mount raw VHDX files even raw normal bare metal drives in WSL2, that's true. However, Linux needs to understand the FS inside.
- pjmlp 9mo ago
  Windows is a bit "yes but" kind of situation. First of all it supports containers natively, Windows own ones, and Linux on WSL. Secondly, because Microsoft did not want to invent their own thing, the OS APIs are exposed the same way as Docker daemon would expect them. Finally, with the goal to improving Kubernetes support and the ongoing changes for container runtimes in the industry, nowadays it exposes several touch points. https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/containerd https://learn.microsoft.com/en-us/virtualization/windowscont...

amonith 9mo ago

Most likely a Windows or MacOS user, where docker runs in a linux VM. Optimized as much as possible and lightweight, but still a VM.

okanat 9mo ago
No, on Windows it is very quick too. On WSL2 compiling Rust programs are almost as fast as Linux on bare metal. However the files need to live inside the Linux filesystem. Sharing with Windows drives actually compiles slower than native Windows.
- pjmlp 9mo ago
  You can use dev drives instead, I guess.
  - okanat 9mo ago
    If you are building natively, yes. However the original comment is about Dev Containers which runs under WSL2. If you open a native Windows folder in VSCode and activate the Dev Container, it will use the special drvfs mounts that communicate via Plan9 to host Windows OS to access native Windows files from the Docker distro. Since it is a network layer accross two kernels, it is slow as hell.
    - pjmlp 9mo ago
      That is the beauty of Plan 9's design. :) I haven't tried, but the idea was to map a such a drive into WSL, but I am not sure if it is possible and indeed how much it would help in the end.
      - okanat 9mo ago
        You can mount raw VHDX files even raw normal bare metal drives in WSL2, that's true. However, Linux needs to understand the FS inside.
pjmlp 9mo ago
Windows is a bit "yes but" kind of situation. First of all it supports containers natively, Windows own ones, and Linux on WSL. Secondly, because Microsoft did not want to invent their own thing, the OS APIs are exposed the same way as Docker daemon would expect them. Finally, with the goal to improving Kubernetes support and the ongoing changes for container runtimes in the industry, nowadays it exposes several touch points. https://learn.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/containerd https://learn.microsoft.com/en-us/virtualization/windowscont...