It still is mobile, it can go a bit up and down.

The space used by the smallest solar charger I've seen on Amazon seems to be similar to 6 or more batteries in the format the N900 was taking - so if you look at space, slow charging from solar charger, and reliance on sun conditions taking individual batteries seems to be the better option for a few days hike. It's also easier to stow individual batteries to wherever you still have space left.

I was referring to work setups with the overengineering - if I had a cent for every time I had to argue with somebody at work to not make things more complex than we actually need I'd have retired a long time ago.

I didn't do enough testing with different materials for a conclusive answer - but that was my guess as well.

I should have 3 different glow filaments somewhere, one PETG, two PLA. Typically I preferred the PLA versions - they had a bit more uniform glow. The PETG one had brighter spots, but as it was mostly transparent individual spots were more visible than with the PLA prints.

Gentoo is useless for learning how things work. Back in the 00s when I still had time to hang out at events it was always quite ridiculous at what kind of basic stuff the gentoo crowd got stuck at - and with the tooling 15+ years more polished now I'd expect what is actually going on is way more hidden than back then.

If you do want to understand how things work just build a minimal system - either on spare hardware, or qemu/kvm. Don't go with systemd, or other fat userland options - that just makes you compile a lot of dependencies not adding value for learning.

Use some lean init (or just write one yourself), and some lean shell.

Not really doing much docker, but a lot of LXC - everything scripted with ansible. I define basic container metadata in a yaml parsed by a custom inventory plugin - and that is sufficient for deploying a container before doing provisioning in it.

I now and then check Tesla share prices after that kind of bad news - and to my amazement it just keeps going up.

That they're not really good at the car building part has been well known for quite a while - and by now it should be blatantly obvious even for people not doing software stuff for a living that they're also not stellar at the software thing (which I assume their valuation is mainly based on, as it doesn't make much sense). They are better at least with the infotainment software than established car makers - but given how those suck at it that's really not hard.

I don't really see them spreading too much in the EU currently - they're currently trying very hard to piss off the Nordics, and I'd expect to see regulation eventually prohibiting new cards with touch only controls. It already is treated like a mobile device by law here - so touching any settings on your Teslas touch screen while driving can be very expensive, up to a temporary loss of license. Also having an accident while touching the screen will shift more of the blame to you.

Lack of accountability goes both ways, though...

Don't want to go into too much details - from a high level perspective the Windows version integrates better into the overall system. In Rosetta, once you're in the emulation layer it can be rather complicated to execute native components from there. In Windows - with some exceptions - that's not a problem.

more recently, tiling.

The author seems to have a different definition of "recently" than I do (have been using tiling window managers for over 2 decades now).

If a window wants to be maximized, instead of fitting in a tile, it will move to its own workspace.

So pretty much "out of the users view", which seems to be one of the main things they're complaining about.

Overall just reads like a shitty mash of tiling and non tiling concepts, which you already can get better on a modern dynamic tiling window manager.

emacs lisp already lets you use the full range of unicode.