Watching Linux distros (and yes, it is usually Debian packagers who act the most sanctimonious) shoot themselves in the face and then insult upstream AND the users of a popular package under the delusion that only the distro's self-declared experts are capable of making decisions is always a good reminder as to why you will never be able to waterboard me into using Linux as my primary desktop. Very sorry this is happening Team KeePassXC. https://fosstodon.org/@keepassxc/112417353193348720
The KeePassXC GitHub repo where Debian users are filing bugs (b/c people by default blame upstream, in part b/c the distros love to blame upstream for everything, even when the changes are clearly the packagers fault) and the Debian packager responds by calling the software crap is my favorite part. https://github.com/keepassxreboot/keepassxc/issues/10725
@johnmark no. Me, a person who loves drama and mess is completely unaware that software development comes with drama. That’s why I haven’t spent fully half my life enmeshed in open source circles. /s
@drwhitt oh, I think it is very emblematic of a lot of the bad/toxic parts of open source culture. It isn’t unique to OSS, but OSS culture (and I’m a huge OSS fan, but we have to be able to call the baby ugly) empowers and promotes lots and lots of anti-social behavior and even worse, puts those people in power.
@keyboardg@keepassxc I mean, this is the natural evolution. And I don’t always love Flatpak or Snaps, but I fully understand why so many pieces of software want to avoid the distro packagers at all costs. It’s a role that made a ton of sense 25 years ago. I think it is a role that still makes sense for non-GUI tools. But when packagers make decisions that negatively impact users without even communicating with upstream, that’s just not cool.
@kgMadee2 I agree with this but again, a change of this magnitude without any rational reason (I’m worried about future xz-like backdoors is not rational), especially when the features are turned off by default, and with Debian’s complete lack of willingness to alert users who now can’t access their password database b/c YubiKey support was removed, goes far beyond the RTFM expectations of using testing.
@kgMadee2 More disturbingly, these problems were found in testing and when users bring up the very real issues with this approach, the asshole packager has the nerve to insult upstream, insult users who use a password manager differently than him, and then has the temerity to call them “his” users. No. They use KeePassXC. They don’t belong to him just because they happen to use Debian.
@matdevdug in general, I agree with you. But thankless task or not, this maintainer decided to make decisions without even trying to coordinate for upstream — problems that will primarily affect upstream, and not this person or Debian — and did it in a way that will be most disruptive. And then when faced with the edge cases and problems of his own making, this asshole decides to insult the project and its users. Users he then claims belong to him.
@glassresistor ok, but how are users expected to know about this when this hits stable or Ubuntu or Mint and their various derivatives? All the user sees is that features they used to have enabled don’t work. Or that they now can’t access their password manager with their YubiKey. And Debian is historically very against any sort of user-alert. If there was actual user awareness, fine. But the response is “read the Debian.NEWS file” as if that is sufficient. And there should be complaints here!
@matdevdug I don’t like criticizing maintainers either but decisions like this are why so many developers are trying to cut the middleman of the packagers all together for the much clunkier world of flatpaks and snaps and appimages. And it’s frustrating to see.
@davidbcohen@craiggrannell@KingShawn there are paper-based vinyl that are probably “greener” but the quality sucks. I honestly just don’t think this move saves that much; even at Apple’s scale, to be a worthwhile trade off. Other things they could do to make more of an impact that wouldn’t take away the whimsy.
The problem with the iPad as as many have pointed out is that the software hampers what it can do unless you’re willing to contort yourself into a very specific workflow. For most casual users those limitations aren’t an issue and the advantages of the form factor outweigh the deficits. But when you charge MBPro money for a device the trade-offs sting. As @jsnell says, the best solution would be to just let us virtualize macOS on an iPad Pro when using it in certain modes https://sixcolors.com/post/2024/05/the-ipad-pro-is-no-longer-the-future-so-whats-next/
@john@jsnell I mean, virtualization allows pass-through access to network and storage components. So you’d just approve permissions to access stuff stored locally to your iPad. But in the case of Procreate, the default for both Mac and iOS of those is iCloud anyway. And the VM wouldn’t be using a separate storage device. Again, there might be some edge cases and limitations but that’s why this would be an option, not the only solution.
@markv@a40yostudent I would pay for that so hard. Fuck, give me cloud-based macOS I can use on my iPad seamlessly (so not just via a VNC) and I’ll pay for that!
Love this from @ismh - I haven’t written much about the new iPads yet because if I buy one, it will probably be so I can hand my 2022 M2 Pro to my mom (since trade-in is less than a 10th gen iPad with 256GB and cellular costs…which is insane. Not for the trade-in but the iPad 10th gen price) and not b/c I need to upgrade. B/c the software means I still use my iPad primarily as a media consumption device. No matter how great the hardware, the software is the rub. https://512pixels.net/2024/05/the-problems-never-the-hardware/
@luis_in_brief@jsnell now, Apple might lose a future MacBook Air sale for you if they did what Jason and I want. But they’d also potentially get you to spend more on an iPad Pro, which might negate that lost income. And I said this in a reply to someone else but if they did this, I think they could absolutely charge another $100 or $200 for the iPad Pro just for that feature. B/c as Jason pointed out, the beauty of the iPad is the flexibility. But the software limitations hinder that beauty.