Having used KDE 2, 3, skipped 4, and now 5, it's the most polished desktop environment I can think of. OSX is too weird and Windows is a hodgepodge of "GUI trend of the day". Not that either of those matter, since they're not FLOSS.
The way I'd do this, is by separating concerns into separate tables. If you have a table with (id, name) and a table with (id, parent_id), any doc with a parent will have a corresponding record in the second table.
Software tends to get thrown away after a few years. Nothing I've written as a professional programmer has survived the test of time. No regrets, though. Why would I carry the burden of self importance to even be bothered about this? Do we really need to cast our work in stone? It's just work and you probably got paid a bunch. Nothing wrong with that.
My advice would be to find whatever motivates you in your life. What makes you happy? Challenge yourself and everything you've got.
Linux always boots perfectly fine with TPM hardware support disabled, even when there actually is such a chip built in.
The real showstopper would be if "SecureBoot" would be enforced. I hope it never actually happens for personal computers. Everything else in the consumer electronics business is pretty much a lost cause already.
I made it because I don't like all the existing frameworks. That said, it uses Laminas Diactoros because not using that would be to reinvent the wheel.
This extension is pretty cool and I already found a bug. It doesn't work for elements whose font-family has been set with a !important flag.
It would be crude to set font-family to "Flow Circular" !important on every element (in the style attribute), but it would probably be much more effective.
This site provides a nice overview, cool. It makes me wonder though, because IMHO PHP is adding too much new features that are often somewhat half-baked. What would be better is to have an actual specification to improve the core language. IIRC, Python gradually adds features where they are opt-in first (from __future__ import foo).
I'd gladly take a language which offers stability and gradual improvement over a language that just keeps adding new toys to play with. The software development cycle can take many years and from my experience, changes in the language or runtime are a burden.
But my biggest gripe isn't with PHP, it's that cheap web hosting still comes with PHP and MySQL. And I honestly can't blame them.
It's pretty cool actually that this is possible and I also can't help but think that this is a solution to a problem that need not exist in the first place. Systemd has this problem and the solution is to use a feature in systemd, right?
IMHO systemd has amassed too many features, both documented and undocumented. Having worked with GNU+Linux for over 2 decades, I still find Devuan and Void easier to manage than Fedora and Ubuntu. The latter is fine for basic desktop needs though.
The way I deal with dependencies lately is I place them in a separate directory (called lib) right next to the project source itself (called src). So the project and its dependencies are the same repository and I can have peace of mind. Also, I've got a few patches for those dependencies and those commits consist of only the patch and a clear log message. This helps when the time comes to update the patched dependencies.
Would I recommend this method to everyone? No. Is it useful in certain cases? Definitely yes.