Apple Watch and AirPods were certainly category-defining products, some people would also argue that the iPad was. So 2010 or before is certainly not fair.
Besides starting at $599 (the Air has mostly been a $999 product; occasionally selling at $799 at Costco), coming in 4 bright colors with matching keyboards, using an A series chip for the first time in a Mac, containing 90% recycled aluminum (the most of any Apple product) and breaking all Mac laptop sales records, there's nothing new about it. /s
Last time I was in London for a day, I simply reserved a table at one of the restaurants at Sky Garden and got in without any queues. Maybe I booked it on the previous evening, but not much earlier than that.
Where none of the desktop environments offer the same feature set. And the more compositors there are the harder it is for apps to use those new protocols, and guaranteeing a ton of bug reports from users using an unsupported compositor. That just hinders Linux desktop app development.
I doubt that. But they clearly thought that people should have a choice. And it is great. But fractured community using different tools for the same task makes slower progress. Each approach has its positives and negatives.
I think it is great that we have wayland and systemd. It will eventually lead to something greater in the future.
I think it came from the necessity for rapid integrations between different parts of the OS. And if it is handled as a single project it takes less time to improve it, since you don't have to align with 10 different projects and their release cycles.
With unified kernel images there is no need for grub or any other bootloader anymore. And UKI simplifies boot configuration and helps improving security in some aspects.
Yes, but people learned from issues that pulseaudio had and then came pipewire. Everyone is happy now.
I don't know about the philosophical aspects, but from pure technical point of view systemd brought some order into the mess. Before systemd it seemed like most distros were barely holding together with duct tape. Systemd standardized a lot of things.
I am fine with a little bit of controversy if the result is a much better desktop OS experience for the user. And as a relatively long time Linux user, I can certainly say it is much better now than it was 20 years ago.
> Yes, but people learned from issues that pulseaudio had and then came pipewire. Everyone is happy now.
Yes, I'm very happy that it mutes my audio when I accidentally unplug my headphones (something which I never asked for) and then often fails to unmute them when plugging them back in, something which requires digging up alsamixer to fix because pulse/pipeware-based GUI tools are being lied to about the output not being muted.
I'm also especially fond of having to open the audio settings app to change audio from one display output to another because some very smart person decided to group all display audio (which are separate ALSA sinks) into one output with different profiles.
But lets not forget that it at least simplified configuration. So much that GUI tools basically don't let you configure shit at all and you need to use one of two (yes, one was not enough) turing-complete configuration languages to accomplish anything slightly non-standard like giving outputs are better name than what your display manufactures cat produced while walking over his keyboard or hiding some of the bazillion useless audio devices that you might end up with somewhere in your PC.
And then of course it still has the PA-innovations like audio randomly stopping for no reason at all until you restart the daemon.
Meanwhile ALSA with an up to date default dmix configuration worked just fine.
When it comes to incorrect profiles, I suggest making a pull request to alsa-project/alsa-ucm-conf with correct configuration. I had similar issue with my audio interface a couple years ago but it was quickly merged and now it works better than on Windows or macOS.
Before that I did have custom config, it was not that hard to set up, there are great examples and explanations on Arch wiki: https://wiki.archlinux.org/title/PipeWire
It depends on how you set it up, but main doesn't have to be the stable release branch. From what I have seen, in most public projects it is the staging area for the next release.
If you have to go back to previous releases you have tags.
When will EU/EEZ introduce right to repair? So much talk about freedom in EU but you can't even fix your own EU made car. All we get are stupid cookie prompts.
Still unable to get any repair manuals for cars, firmware locked down by PIN. For US VINs for the same car model you can purchase access to that easily. Meanwhile in EU you need to be an authorized service to get that.
Factory service manuals? Most of those are free. You don't need to be an authorised service to get hold of those.
The right to repair directive also authorises you to bypass any software restriction without violating hacking laws, as long as you're not hurting other people. The same is not true of the USA.
I made a custom Payload CMS block that allows to create and update excalidraw diagrams within the CMS. It supports dark and light mode switching and rendering inline or as external SVG.
And last weekend I added MCP server with Oauth so I could generate and update those diagrams and add them to post drafts from Claude. I think it is more convenient since I don't have to use API billing model and don't need to build a custom UI.
Originally I wanted to sync posts from Obsidian but it doesn't have good enough image handling which I sometimes need and I needed extra metadata to unlist or password protect or noindex some posts.
reply