I've found enshittification to go in cycles, with mixed results for recovery.
Google successfully embraced extended and extinguished XMPP, but now it seems like most folks use Discord, Skype, Zoom, Signal, and whatver Meta calls their spyware today. Our chat experiences certainly aren't living the FOSS dream, but at least Google Talk doesn't feel mandatory anymore like it briefly did after it "extinguished" XMPP. (Did Google kill Talk? I can't keep track of what Google hasn't killed yet.)
Mobile operating systems have been a bumpy ride with highs and lows, but Android, the current most common mobile OS, is a lot more open than anything we had before. The vendor builds of Android that most people accept are, indeed, enshitifying now, so I guess the verdict is still out.
The web itself tried hard to go fully proprietary several times: with Microsoft COM, Microsoft ActiveX, Adobe Flash, and Microsoft Silverlight, among others. These are all completely gone now. Today, almost every scrap of technology serving and browsing the web is open source. Of course, most of search is still closed and enshitifying, and the open options for social media are very new, so there's still plenty of room to improve or lose ground.
The Commodore 64, a (delightful, but closed) proprietary platform, was once the single best selling single computer model of all time. Today that title goes to the Raspberry Pi, a mostly open hardware specification that is rapidly improving.
Anyway. There's cause for hope, along with plenty of reasons to be concerned.
Maybe because I tried to follow MS's "use your own distro" instructions instead of using something prepackaged?
Not op, and I don't care about systemd, but...
When I've used anything I wanted to substantially modify, I've followed the "use your own distro" instructions. In the past I've done this because WSL had a strong assumption of exactly one copy of each distro, and I like to abuse it for more.
Overall, I've had a better time with the the "bring your own distro" instructions. But some of my experiences with WSL were before they even got the Windows Store installer working correctly.
More recently, I recall Windows Store being fine for stock Ubuntu and for stock Debian. But I didn't find the "bring your own distro" instructions to be much trouble, either. My perhaps faulty memory is that it took maybe ten minutes, last time I used them.
So why are you advising to change the default install of Debian to include it?
I didn't advice any such thing. My edit is just to acknowledge someone else who makes it part of their process.
Citation needed.
I shared my personal experience and you turned it into a distro war. Go look up your own damn sources.
Pretty sure this is either personal opinion or anti-canonical, anti-snap ideology.
Fuck yes. It's both! Snap is a slap in the face to the contributors who brought Canonical this far. I appreciate their partnership so far, and now, speaking as a package maintainer, Canonical can fuck right off.
Targeting WSL users with this rhetoric is ridiculous.
Helping people make an informed decision about their tool chain is rhetoric? Give me a fucking break.
I don't like Ubuntu. That's not a secret. Ubuntu is a fine option for total newbies. People using WSL tend not to be total newbies and may well run into real issues (such as the ones that prompted me to switch), thanks to snap.
In contrast, I find the benefits of Debian over Ubuntu to be most noticeable on the command line, which is all we get in WSL anyway.
To me this is some solid advice that I already knew.
I think there's also a fair assumption by the author that anyone running WSL isn't a total Linux newbie. I personally, think of WSL as an intermediate skill level way to run Linux, because WSL is still - frankly - a huge pain in the ass, when contrasted with trying out a bootable USB drive, and then only gives the command line, which is also a very limited way to experience Linux. (I think it will get better, but today WSL is not a way that I recommend to newbies to try out Linux.)
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 newer Linux users.
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 (optional) 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.
(Edit: In case anyone was wondering, I really, personally, don't like Ubuntu, because it has Snaps. I'm aware that makes me a meme.
Snaps are bad for the community, and bad for the user.
Some of us understand why, and do our best to mention it politely, every so often, to save our peers a headache or two.
That said, folks who need hand-held through the specifics of why Snap sucks would do better asking elsewhere. I am famously old and irritable.)
But it's also useful - the preparations given for zombie apocalypse are actually pragmatic preparations that can help during severe weather, supply chain disruption, pandemic, etc.
I like to share the zombie article, in particular, because, while it's silly, the advice in it is reasonable and useful to almost anyone.
Basically yes. The article source is able to confirm attacks by Orcas on moose have happened.
The only "maybe" part is whether any moose has been fully eaten by any Orca. Occam's razor says yes, but the whole encounter is a rare enough (or just rarely documented!) occurrence not to be widely documented yet.
Yeah. Any party that gets desperate enough to court actual progressives will get a big boost.
That said, courting racists also seems to be pretty effective.
I choose to believe in a world where the second option is getting less viable while the first is becoming more viable, with time. But that's just a matter of faith (with at least a little bit of evidence from history).
I've found enshittification to go in cycles, with mixed results for recovery.
Anyway. There's cause for hope, along with plenty of reasons to be concerned.