131–140 of 178 posts
Give me one good reason why anyone would bother with any of this at all?
WSL saves me to install them.
Additionally, I only care about running Linux containers, everything else I run on native Windows, so the filesystem performance isn't an issue.
Earlier quoted context omitted.
You can access them from the rest of the system. For normal usage the performance is completely acceptable but for development tasks it matters.
> Just copy it into the WSL file system Yea bro totally. Totally. I'm gonna copy 2TB of media into the WSL virtual disk just so ffmpeg can run a little faster but still way slower than simply running linux. (I beta tested the shit out of WSL1 and 2) before I wised up and just installed Gentoo forever.
Earlier quoted context omitted.
> Just copy it into the WSL file system Yea bro totally. Totally. I'm gonna copy 2TB of media into the WSL virtual disk just so ffmpeg can run a little faster but still way slower than simply running linux. (I beta tested the shit out of WSL1 and 2) before I wised up and just installed Gentoo forever.
Why are you using ffmpeg under wsl?
The entire point of wsl is to be able to run code compiled for Linux on Windows.
ffmpeg underpins so many things these days. It could be used to extract frames in a PHP based website, convert something to a gif, or a demux an mkv. You may as well be asking me why I'm using a computer.
Earlier quoted context omitted.
> Just copy it into the WSL file system Yea bro totally. Totally. I'm gonna copy 2TB of media into the WSL virtual disk just so ffmpeg can run a little faster but still way slower than simply running linux. (I beta tested the shit out of WSL1 and 2) before I wised up and just installed Gentoo forever.
There is ffmpeg for Windows.
This ladies and gentleman is the problem with discussing Windows design patterns on the internets. They say "use this" and you say "well it's broken in X, Y, Z" ways and instead of fixing it they say "you're using it wrong". No. Maybe it's just an inferior architecture.
Earlier quoted context omitted.
Windows _is_ garbage for a lot of modern development (except thise targeting Win32). But that does not matter to the ICT department tasked with controlling and securing all endpoints, preferring a single, very well known and controllable OS over freedom and performance.
At least it isn't Wayland, or having to mix and match configurations until hardware video decoding on Chrome finally works.
The top compositors right now for desktop are KDE Plasma, Hyprland, Gnome/Mutter and all of them implement the Wayland protocol independently.
For game wrappers Valve makes Gamescope (https://github.com/ValveSoftware/gamescope) which is also a Wayland compositor.
When you run a game through a wrapper like GameScope it will draw to the Wayland Server that GameScope is running and then that subsequently writes to the parent display server (which can actually be X or Wayland).
Anyway it's a far superior and more secure protocol than whatever Windows is doing and you should for sure have ChatGPT explain it to you.
Earlier quoted context omitted.
On the other side, I am a lifelong Linux user, and even with advanced LLMs, trying to get Microsoft Windows to behave sanely takes hours every month for years on end (thanks, day job). Things Linux figured out in 2003 are still magic or completely undoable on Windows.
Not my experience. I installed the IoT version of Windows 11 and have changed exactly one setting (put the start menu back on the left where it rightfully belongs). Nothing else has required any changes at all to get sanity, which is more than you can say for Mac (which requires half a dozen extra apps to make it same - SteerMouse, Karabina, Spectacle, etc.), or Linux, where the UI is mostly sane - if you're using KD…
On Linux, KDE has the plasma System Monitor, and if you can't use it for some reason you can switch your entire session to a TTY with CTRL+ALT+F2 and kill any process you want.
Earlier quoted context omitted.
/mnt/c is a mounted C: drive in WSL2, that allows WSL2 guests to read/write files on the Windows host. The mount is fine and speedy enough, but the underlying reads/writes turn into native NTFS reads/writes through Windows. NTFS file API is incredibly slow - high fixed overhead for initial file access. So patterns like node_modules with many small individual files (or compiling code in general) are much much slower o…
It's the file system filters that are an issue on Windows. It trades performance for extensibility. NTFS itself is a fast file system.
File access is significantly slower on Windows compared to Linux on the same hardware. You can run Linux inside a VM and it will easily beat the host OS in filesystem performance.
If the problem is not NTFS, then it is in how the Windows OS uses it
The new container capability also looks magical, and being able to access that directly from windows apps seems pretty cool too. Not sure it would be worth the time investment vs. docker desktop, but interesting none the less.
Earlier quoted context omitted.
> Just copy it into the WSL file system Yea bro totally. Totally. I'm gonna copy 2TB of media into the WSL virtual disk just so ffmpeg can run a little faster but still way slower than simply running linux. (I beta tested the shit out of WSL1 and 2) before I wised up and just installed Gentoo forever.
You are very far from the average WSL user, especially with that Gentoo mention.