growing it like a garden is a perfect phrase imo

because on windows or Mac it may have just worked. …until it doesn’t, or leaves your windows scaled wrong or placed on monitors that don’t exist or some other failure condition. at which point you reboot and hope for the best.

when it doesn’t work on Linux I’d check logs, actual configuration, and even the source if I need to.and then I’d hopefully improve things and make it work the way I want it to.

there’s also the impact of having less consistency in hours. i.e if I work Friday and don’t work Monday but am blocked waiting for someone whondoesnt work friday…it’s waiting until Tuesday.

If adopt systems then the question is easy to answer: no, journald does everything you need.

without adopting systemd… well. Are you evaluating going without any log handling at all and maybe just dumping logs ephemerally to tty0? DIYing all log stuff like your init scripts DIY things?

Personally if I had to go without journald I’d probably go back to using syslog-ng. But I guess there’s an argument for shipping straight into something like opentelemetry-collector if you’re willing to put in a lot of work.

It depends on the package really. Sometimes you’re better off without the fixes that occurred in the last 2 years if it means avoiding the new bugs in the last 2 years.

IMO the more you try to stick to the latest releases, the more important it is to continue to stay updated. but every upgrade is a chance for new bugs or just breaking changes, so for new users starting with a stable distro is a good choice.

… except for browsers, where you both need the newest features but REALLY need the newest fixes.

There’s a lot of things that make the Bluetooth experience better… it’s just almost all focused on mobile phones, maybe apple laptops if you stay in their walled gardens, but definitely not stock windows.

I say stock because if you do use windows and want to use Bluetooth you can improve things with a third party driver https://www.bluetoothgoodies.com/a2dp/ it’s still not great but at least you can use better codecs than default

for earbuds it’s useful as many modern phones can share their battery to wirelessly charge another device, so you can top up your earbuds off of your phone while you’re out somewhere and not need to lug around a charger and cable.

For wirelessly charging phones, I agree the pad style chargers defeat a lot of the point, but I am a fan of the dock-style wireless chargers. I have one at my desk and can just glance at my phone to see notifications, and I have to set my phone somewhere anyways, so this lets me top up my phone without really thinking about it.

Yes. and why it’s wildly complicated on Windows machines where you have an audio output device for headphones and for headset, and once something starts using the mic the output device itself changes.

So joining team chat in a game will either make audio sound horrible or break it entirely if you had specified the output device instead of using default device.