[sigh] The *real* problem is not that there now is an _optional_ "birthDate" field in systemd. The *real* problem is that those laws are even proposed in the first place.
I'm not a systemd fanboi, but I am old enough to remember sysvinit. It SUCKED!
| blog | https://blog.researchmonger.com |
[sigh] The *real* problem is not that there now is an _optional_ "birthDate" field in systemd. The *real* problem is that those laws are even proposed in the first place.
I'm not a systemd fanboi, but I am old enough to remember sysvinit. It SUCKED!
I just heard about this game and this one minute trailer has completely sold me on it. Instant day one purchase.

It’s that time of the year again - someone (me) wanting to try replacing #gentoo ‘s #portage with a #Z3 #SMT solver. Well, this time I did it! Or at least started to… got 2x performance boost but it’s not quite black and white.
https://blog.researchmonger.com/2025/12/integrating-z3-smt-solver-into-gentoo.html?m=1
My decompiler reached a milestone - I can now lift every instruction in this sample function I've been using, which includes rep.movsd instructions.... though no floating point yet. The rest has been a lot of "internal" updates for how I handle going from basic blocks to abstract syntax trees. Hopefully this will speed up the process later.
I've also added basic symbol resolving logic that tracks scope of the high-level variables.... Of course nothing is creating them yet so that's why you see a lot of the "unresolved" symbols.
The rest of updates include some quality of life updates like being able to click on keywords, assignment operators, and function calls and that will take the assembly view to the instruction responsible for that operation. I've also added the little block offset drop down lines, which was easy to implement but surprisingly useful.