701–710 of 719 posts
Earlier quoted context omitted.
Obviously Mac is terrible, as a Linux user I would clearly not use it as a baseline of how it should work.
The point is it's a difficult problem which nobody has solved perfectly. ALSA was certainly not better.
Earlier quoted context omitted.
> You know what software doesn't fill me with dread to update? FOSS. speak for your clearly non-pulseaudio-using self (:
And also clearly not a GNOME user...
For some reason they just can't help themselves from "improving" the themes that people are already using instead of creating new ones that people can choose if they want extra white space or whatever is hip now.
Earlier quoted context omitted.
Anything with the Red Hat stink, these days. Which, yeah, a lot of that’s Poettering. If they haven’t been executing a plan to make it extremely painful to maintain a distro that differs significantly from whatever Red Hat’s preferences and ways of operating are (so, making it harder to justify anything but “screw it, we’ll just use red hat, everyone else is just the same thing but with less ability to steer the dire…
Latest venture of the ilk behind all that : device attestation for Linux (Amutable). Yes, they clearly have an agenda and are being quite successful at pushing it.
Earlier quoted context omitted.
Uncle Bob has fully embraced AI and is risking becoming part of the problem these days.
Uncle Bob already became part of the problem by some of the stuff he wrote in Clean Code (like using mutable instance fields instead of method parameters). Luckily he isn’t perceived as very relevant anymore.
It's not that I disagree without you about mutable fields vs params, but the industry so disproportionately on the other side of that issue that I'm surprised this objection is raised as often as it is.
Bring it on! Let's have more persistent data structures in standard libraries. Construct a Map by folding new key-vals onto another (possibly) empty Map.
(Rather than creating an empty map and then mutating its instance fields until it's full)
Earlier quoted context omitted.
It's not what I would call invisible, but yeah that's the behaviour I would expect. That's also similar, to what already happens when I type in one window, while I scroll in another.
That's only possible when they are partially.side by side otherwise you wouldn't be able to hover over the background window
Earlier quoted context omitted.
We can't change the fact that commercial OS vendors are all feudal overlords now, but the lawmakers are letting them get away with it and that is something we might still be able to change.
We can also choose a different OS, at least for real (non-phone) personal computers.
Earlier quoted context omitted.
I'd buy that if lots of high quality PRs were sitting around waiting to be merged, but they don't exist. There's barely any evidence that AI is even real in the open source world, other than the slop of course
for small to medium sized bugs I managed to get a bit more than half of my PRs to get merged. ~90 PRs since May https://june.kim/speedrunning-open-source Verify yourself: { merged: search(query: "is:pr is:merged author:kimjune01 created:>2026-05-09T00:34:00Z", type: ISSUE) { issueCount } closed: search(query: "is:pr is:closed is:unmerged author:kimjune01 created:>2026-05-09T00:34:00Z", type: ISSUE) { issueCount } all…
>It cost me 53 merges, 63 closures, a billion Opus tokens, and eight account blocks
I can't believe people think this is acceptable. You didn't fix any problems, you just managed to deliberately sneak slop past maintainers without their knowledge. There's no review by you here that any of the PRs actually fixed anything (presumably because software engineering is a learned skill), you just assume that the AI fixed the bugs without checking any of it apparently because.. you feel you're important?
Earlier quoted context omitted.
I am doing my best to implement a rule with apps where the third time in a single session you bother me about something that has absolutely nothing to do with the workflow I opened to app for, I uninstall the app. I don't want to update my spreadsheet app, I want to work on this spreadsheet. I don't want to tour the new features from the last update, I want to work on this spreadsheet. I don't want to sign in in orde…
I’d have no software installed after a week!
1. Our incentive structure in software has always been to a large extent driven by more features [1]. Agent driven development has poured gasoline on that fire.
2. Despite all the effort we put into quality assurance by engineering teams, it's still hard to full de-risk releases across a broad set of configurations use cases, etc. Especially as most agents and even the test hierarchy itself tends to favor unit or module tests and these issues tend to pop up at integration points or hard to test non functional requirements.
So I think what we're seeing is people are rapidly adopting agent lead development due to #1 but the risk reduction pipelines haven't caught up with #2. I think they eventually will but we're definitely in for a rough road for a bit.