You must log in or register to comment.
I use Arch in WSL BTW. This is not a joke its actually quite nice
How do you get systemd to work properly? Maybe because I tried to follow MS’s “use your own distro” instructions instead of using something prepackaged?
ChatGPT - give me an example of what an insufferable Linux elitist would say about wsl.
“This article is not for Linux experts. If you are one and have a Windows machine (main reason is gaming), I hope you are using Debian for WSL and not Ubuntu.”
if you encounter problems just search online or ask AI, it’s fairly simple
Good luck with that. All the answers are going to assume WSL is using Ubuntu.
Why do Linux advocates try so desperately to overcomplicate things?
Can’t you you just be satisfied a Windows using is experimenting with Linux. Why does it have to be your ideological strain of Linux they use.
All the answers are going to assume WSL is using Ubuntu.
Every recipe that I have ever encountered for Ubuntu worked on Debian, except the recipes involving Snaps, which were inevitably much simpler on Debian. And I haven’t seen anything useful under WSL (cli tools) packaged better as a snap anyway.
Why do Linux advocates try so desperately to overcomplicate things?
Computers are complicated. Linux advocates just aren’t being paid to lie about it.
In this case, this is a simple 7 character (edit: plus a one line command to enable systemd) change that can save a newbie a lot of trouble, and comes with
no downside.the downside that systemd isn’t enabled by default. (Edit: a good point made below.)There’s very few cases where Debian and Ubuntu are different at on the command line (which WSL is). In those very few cases, anyone using WSL is going to have a much better time on Debian, because they’re more likely to find a working recipe.
The exact reasons for this are nuanced, but come down - folks liked me publishing recipes don’t target Ubuntu anymore, because I wasn’t (as a package maintainer) invited to the Snap party. Which is fine. Flatpak does the same job, in an open way.
So for the 98% of recipes that predate Snap, there’s no difference to be had as a user. For the cutting edge 2% of new stuff, newbies are increasingly better off on Debian.
I’m pretty sure a year ago there was a set of users claiming systemd was the worst thing to happen to Linux since snap.
So why are you advising to change the default install of Debian to include it?
Every recipe that works for Ubuntu works for Debian,
May as well just install Ubuntu then.
For the cutting edge 2% of new stuff, newbies are increasingly better off on Debian.
Citation needed. Pretty sure this is either personal opinion or anti-canonical, anti-snap ideology.
Targeting WSL users with this rhetoric is ridiculous. If you want to tailor your own systems outside the norm then sure go ahead but claiming things will be easier for a newbie by running specific commands they don’t have the context or expertise to comprehend is absurd.
@adam431@lemmy.world @Adam431@lemm.ee
Why the new account? Did your last account get banned from spamming posts from your own blog?
Ubuntu in WSL comes with systemd enabled. Debian doesn’t, and you have to enable it yourself.
That’s why I chose to have people use Ubuntu in WSL, despite the other downsides. One less step to setup a Linux environment on Windows makes the process smoother.
That’s a fair enough reason. I personally never noticed because the “this isn’t running” message is pretty clear to me. But I can see how that’s a potential blocker for new Linux users.
Well that was a whole load of nothing.
How about just using Debian and not WSL?
Work computer. I’d wipe it with Linux if I could.
“if you’re a Linux expert, this article isn’t for you. You’re probably already using Debian if you use WSL”
As a Linux expert - yep! My distro choice under WSL is Debian, for the same reasons shared in the article.
What reasons? They gave reasons? They just said that windows fixes the flaws Debian has which is quite the “compliment”.
Hurr durr Canonical bad