I made myself a little HDMI dongle (about half the size of a classic Fire Stick) with a WiFi modem that I use to remote control my TV from Home Assistant. My remote is the HA app.
Why? Because Google Home's TV remote stuff can do a lot, but not turn on the TV. CEC can.
Historically neither of them made any microcontrollers. Arduino shipped Atmel and Raspberry Pi chips. Adafruit has boards with a variety of microcontrollers from various brands on them.
This is different now that Arduino is Qualcomm-owned and ships Qualcomm silicon, of course.
As an open source dev, in principle I like the idea that my code is used to train models that help produce other code. The problem is license enforcement.
Do Arch and NixOS count? We're in the core package repositories for them, and have packages available for a list of others.
We're not aiming to be in GUI installers yet, that'll be sometime after taking the experimental label off. We're still going slow and steady; I don't think about doing things that will bring in more users until incoming bug reports are dead quiet (or as close to it as they ever get), and the userbase has been going up plenty fast all on its own by the activity I see.
So, sometime next year we'll be working on distro stuff again. Dunno when, I expect another spike in new users and bug reports when I take the experimental label off.
now that 6.18 is the new LTS kernel, will I have a good experience with bcachefs if I stay on that LTS kernel instead of tracking newer stable kernel versions?
I currently run NixOS with ZFS-on-root, and because ZFS is also out-of-tree, the "stable" ZFS version in nixpkgs isn't always compatible with the most recent stable kernel. to keep things simple I tend to just stick with the LTS kernels.
previously when I've tried to experiment with bcachefs on NixOS I ran into a catch-22 where I needed to upgrade to a newer kernel to get bcachefs support but doing so wouldn't be compatible with ZFS.
FWIW, this just isn't true for KDE. We hit a rough patch with the KDE 4.x series - 17 years ago - that has been difficult to live down, but have done much in the way of making amends since, including learning from and avoiding the mistakes we made back then.
For example, we intentionally optimized Plasma 5 for low-powered devices (we used to have stacks of the Pinebook at dev sprints, essentially a RaspPi-class board in a laptop shell), shedding more than half the menory and compute requirements in just that generational advance.
We also have a good half-decade of QA focus behind us, including community-elected goals like a consistency campaign, much like what you asked for.
I'm confident Plasma 5 and 6 have iteratively gotten better on all four points.
It's certainly not perfect yet, and we have many areas to still improve about the product, some of them greatly. But we're certainly not enshittifying, and the momentum remains very high. Nearly all modern, popular new distros default to KDE (e.g. Bazzite, CachyOS, Asahi, Valve SteamOS) and our donation totals from low-paying individual donors - a decent proxy for user satisfaction - have multiplied. I've been around the commnunity for about 20 to 25 years and it's never been a more vibrant project than today.
Re the fantastic talk, thanks for the little KDE shout-out in the first two minutes!
I'm obviously biased when it comes to FOSS foundations, but Simon is also a member of the board of the Python Software Foundation, which is not nothing in terms of looking after our craft.
The LLM stuff feels minor in comparison, even if it may be what HN knows him for. It's certainly not the same level of achievement as your average bargain bin AI rambler in your LinkedIn feed.
If anything, Python programmers should be mortified that PSF leadership includes someone who seemingly spends all his free time and social capital trying to normalize slop and downplay the negative externalities of a bunch of companies that openly wish to undermine software authorship, depress programmer wages, and obliterate career opportunities for novice programmers.
The Industrial Revolution is coming again. Look at data center spend for massive companies like Microsoft. Love it or hate it, the AI you see today isn’t going away. It will only become more capable.
Maybe the next generation can / will need to start the Butlerian Jihad but we’re stuck for now.
Clearly you've had some interaction that upset you and I apologize for that, but I've never come across any Plasma dev who felt we nailed that one (and I wrote large parts of the panels, the menu, the icon desktop, etc.) I was genuinely surprised by your comment.
To be honest, this is like.. 5 years back? Maybe more. But I don't switch DEs that often.
It's funny to see the two things that prompted the discussion (naming desktops and per-desktop wallpapers) come up heavily under that issue you linked.
Like I mentioned in another comment, I like that KDE devs are much more constructive than Gnome devs. In that issue you can clearly see you're asking users to rephrase their feedback so it is more useful.
With Gnome, I've for example opened an issue for something that isn't according to visual HIG practices. Implementing this would lead to more visual clarity and it would look better to boot. I got told that no, actually they know better. It was pretty clear that they thought that if code or design originated from their shop, there could be no (better) alternative.
When I linked and gave mockup examples I got snarked, and when I snarked back I immediately got dressed down for rule violation by some mod figure that completely ignored their dev's initial snark. Just very, very unpleasant people.
Apologies for the rant haha. Anyway, thanks for linking that and for responding!
Why? Because Google Home's TV remote stuff can do a lot, but not turn on the TV. CEC can.
reply