aard

My wife does that. I've been wondering more than once if I need to get her brain checked.

I'd just start from very simple kernel and static init, and work my way up to adding more functionality. I'd use kvm with rootfs on p9fs - that allows playing with it without having to build images. I can throw together the initial invocation, if you're interested.

Then start building simple core elements in a language allowing easy static linking - I'd use C with dietlibc or go. Start adding core userland programs, explore initramfs (without using something like dracut), add dynamic libraries and explore the dynamic linker, ... - if you're interested we could set up a matrix channel for questions (typically with some lag, though), and do a github repo to follow along.

LFS iirc goes for full desktop - the high level userland is very complex, but easy to understand when you know the basics. You pretty much learn how to compile lots of libraries - which has limited use. A full LFS style desktop I'd no longer recommend nowadays - it's just too many dependencies to deal with. I used to build my own system (not following LFS) until the Xorg fork made it sigificantly more complicated - and things got just worse since then, and I never was using a complicated UI stack.

edit: I had a few minutes, so I've thrown this together https://github.com/bwachter/lll - you should easily get a kernel with a custom init running, and have enough to start experimenting. If you or anyone else is interested to go deeper I'll set up a matrix channel for guidance.

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 was wondering a few years ago how far you could get with implementing some simple markup syntax with just regex. Turns out, surprisingly far, but once stuff starts going wrong you're in a less than ideal situation.

https://github.com/bwachter/awfulcms/blob/master/lib/AwfulCMS/SynBasic.pm

I guess that explains why I'm not seeing it - my workstation has 64 threads and more than enough memory, and on my notebook I'm scheduling load intensive stuff to not interfere with interactive device usage.

...which everybody with half a brain knew already over a decade ago when that stuff started.

I do understand that you guys have shittier taxi service over there than we generally do have in Europe, and it was tempting to go for something new - but there's a service like this has fixed costs, including car maintenance, and giving a higher cut to the app company than you was doing during taxi times where you was hardly getting by doesn't really work, once the venture capital dries up, and they try to make a profit.

Since everybody was running after uber like sheep you my end up with the actually sustainable transport destroyed - fortunately regulation saved us from the worst over here, though uber did have some negative impact.

You're describing Wayland running into issues due to overall high system load, and not been given enough scheduler time to accept messages?

edit: This issue? https://gitlab.freedesktop.org/wayland/wayland/-/issues/159 - didn't find anything else matching the description, and personally have never seen that, both on my low specs notebook or my workstation, which probably counts as higher spec.

Would be interesting if this is more on Firefox side, or on compositor side. I've been running Firefox in Wayland for about 9 months now, without any issues.

That sounds more like a compositor problem - typically a client should not have control over where windows are placed, and that X11 allowed that got heavily abused with negative impact on UI. Wayland fortunately fixed that, so it is now up to the compositor where to place windows. Those can send hints, but the compositor is free to ignore them.

In your situation your compositor should remember where to stick the windows.

A big issue I see here is retroactively applying the new legislation. While I do think designers absolutely should be paid extra in cases like this I also think applying it back until 2003 like Sweden is doing is already too long - it violates the principle of legal certainty. It'd be very interesting for somebody to take this up to ECJ.

Applying it back until the 90s like in this case I'd expect them to have no chance - while again I agree that this lady deserved the money it also seems she might have a legal claim to continued payments back then as the company was referring to the legal situation no longer valid when they stopped the payment it'd be way beyond statue of limitations by now.

Legally I don't think she has a chance, morally I think the company should just do as she suggests and start that fund.

Outside of tech circles pretty much nobody seems to have noticed how bad google search has become over the least years - unfortunately there's no single search engine that's "general purpose good", like google used to be.

It's somewhat ironic that nowadays using metasearch engines often makes sense again - for those too young to remember, that was the default way of searching in the mid to late 90s, until google came along with consistently good search results.