Hacker News new | ask | show | jobs
by yjftsjthsd-h 266 days ago
That feels like a contradiction; either WSL is a good solution and you can just run radicle there, or it isn't.
1 comments

Good enough in a pinch to prevent a switch but not good enough to do all your work in the wsl filesystem.
WSL... filesystem? Either way, I firmly disagree, there are not many cases where I've been unable to do dev work on WSL. Only when I need particularly weird / specific networking or hardware (ie. GPU, which might work now) have I had significant problems.
File IO from windows into the wsl disk and vice-versa is significantly slower so it's not great to, for example, use wsl git on a project living under your windows user directory or visual studio on a directory under your wsl home.

I think they're just using FUSE to make it work but don't quote me on that part.

Last I heard, using native git on Windows was slow anyways? Something about how NT handles files. So even with git it was already best to keep things inside WSL and just use ex. VS Code with a remote in WSL, and at that point it doesn't matter if you use radicle in WSL instead of git.
Oh that use case isn't great yeah. They probably aren't using FUSE, they notably use 9P a networked filesystem protocol from Plan9.

If you operate fully inside of WSL (either via X11 or in a terminal) it's a pretty good experience.