You’re already doing great if you just don’t disable IPv6. Bonus points if your ISP and your router supports proper dual stack IPv4 + v6, then you can actually connect to the internet using v6! Also, fun fact: the original Nintendo Switch does not support IPv6 at all. Pretty much all other non-ancient consumer stuff should be fine. Check your clients IP address assignments, maybe you’re already using IPv6.

Yes, the issue is the wording. The american version shrinks a bottle of certain volume, the metric version shrinks the unit of measurement.

No, though parts of systemd have a scope creep issue, that’s not what I’m describing. I’m talking about Poettering deciding to create a service layer for Linux after stealing some ideas from MacOS. Reducing that to “scope creep” is misleading at best and feeds into the “systemd is a monolithic application” concern trolling at worst.

Don’t like systemd-resolve? Fine. I get that plenty of implementation details are incomplete, suck or have caused friction with other software. On the other hand it’s a really useful tool for dynamic split dns handling, which is why I like using it. You can disable it, I’ve done so on some workstations and servers, because of poor choices in internal domain names leading to mDNS issues, knock yourself out.

Don’t think it should be part of an init system? It really isn’t. I wouldn’t call systemd just an init system to begin with, though that was the initial project goal. Most of its parts are reasonably well separated or at least highly configurable for a service layer. I genuinely think it’s completely insane to have DNS resolution in libc, but people have gotten used to that. Systemd-resolved is completely inoffensive in comparison imho.

Don’t like systemd as a whole? Use a distro without it. It really is that simple. Everything has been discussed - at length. Wars have been fought. At this point, change will only come if the complainers actually sit down, shut up and do some work towards their goals.

Sorry this turned into such a rant, most of this isn’t even directed at you, this situation just annoys me. Especially this poor guy getting death threats on GitHub because someone riled up all the asshats in the community who have no idea how any of this works. Maybe they should focus their energy on the political forces pushing the California legislation that started this whole mess? I’ve been tired of this stupid debate for years now. I feel like it’s mostly carried by people who have no idea what they are talking about these days.

Could be surrealist humor if we ignore the alternative american version

Yes.

Watch people unironically celebrate FOSS developers running into financial issues from bot traffic, because they don’t like Gnome shell.

Wait a second. Is this just Lunduke gaslighting people again, like the last time all the idiots were saying that Gnome was going to go bankrupt within a year?

The “political stuff” about the birthdate field is completely overblown, as per usual with systemd. Binary logs aren’t that big a deal either. Like Torvalds said, those are details you can disagree with but it doesn’t mean you should dismiss the entire project because of it. Your comment is probably the first one I’ve read in this community that doesn’t boil down to: “I read somewhere that systemd doesn’t follow unix philosophy, yuck!”. That was kind of my entire point.

I wouldn’t even complain about it, if people here just stuck to shitposting instead of this thinly wrapped “I like/dislike X, please fight about it in the comments :)” bait.

There are legitimate reasons to criticise systemd and I’m completely certain that they will never be posted in this community. I swear if I have to read some stupid comment about the unix philosphy from someone who has no idea what systemd is, which parts are optional or what init looked like before this stupid twenty year long debate…

Let’s pool together and buy shares for a hundred bucks.

You don’t really need to care about that from a consumer perspective. Unfortunately however, this is a common weakness of FOSS projects. If the maintainer is an asshole, the project suffers and eventually dies most of the time. Being an asshole is not conducive towards attracting contributors. Who knew?

Pokémon Go already has multiple revenue streams, including direct in-app purchases.

Time to hit the mysterious S↔D button.

I’m glad I don’t work where you do. Unfortunately though, I’ve heard plenty of stories from industry colleagues who have been forced to use AI coding assistants, regardless of any actual impact on productivity or reliability. The consequences of this approach are already manifesting in the form of an embarassing new era of security vulnerabilities. Preaching about the widespread usage of AI is misleading at best if the adoption is mostly based on external marketing pressure. We’ve had this before with other technologies that get pushed hard by sales people.

You might want to consider Bottles as an alternative for managing Wine prefixes and launching applications.

I wasn’t sure if it was a joke and I read another comment here that seemed to indicate that it was not. Thanks for clearing that up, unfortunately sarcasm is easily lost across the internet.

No clue what your issue is, but if your standard for OSS is not being associated with furries, I’ve got bad news for you.

Depends on your use case. Manjaro is in the unique position of having such a poor management track record, that almost any other Arch derivative (or, you know… Arch) is preferable. They’ve let their SSL certificate expire for the 7th time just last week I think? I honestly haven’t kept count, but it happened at least a few times. If it works for you, that’s fine. I imagine most reasonable people don’t really care. I personally dislike Manjaro for their poor track record managing their repositories or SSL certificates, their historically stupid approach to the AUR and the generally negative effect it had on Arch linux (tech support). Honestly I think Manjaro benefits most from its popularity in the tech influencer spheres and the fact that most of its userbase doesn’t seem to question if a rolling release model actually makes sense for their use case.

If the graphical fidelity and the animations in the trailer are actually in-game, then I suspect we’ve already seen at least half of the Pokémon that will be available, in this trailer.

I mean, yeah that would be my solution. I get that the AUR is attractive, precisely because it has a low barrier for anyone to submit their PKGBUILD. The level of oversight and verification is just a bit too low to recommend it to an average user, without a lot of caution. You’ve mentioned some alternatives that fall on different points along the spectrum of delivering software. Something like flatpak is a much more reliable tool in the hands of someone who just wants a GUI app and not think about how it gets to their desktop. For everything else that isn’t part of your distros repositories, there’s really not a good noob-friendly solution that doesn’t carry a big potential risk. Most distros have third-party repositories that use the same underlying tools to deliver software, but are less strict about QA and stuff. This is kind of a bad fit for rolling release distros in my opinion and is probably one of the reasons the AUR is so hands-off and DIY oriented.

There’s probably a better way to handle this, but I don’t think it’s an easy thing to solve (especially for the rolling release model) and the AUR isn’t really appropriate for mass-consumption by average users. Also, there will always be a certain point beyond which you’re on your own, it’s just not feasible to have reliable, safe, distro-agnostic packaging for every piece of software out there.