Can a lawsuit be served using Slashdot also?

.NET/C# has had AoT (compile at installation) compilation since day 1, since .NET 1.0, since 2002. No-one uses it. For good reasons.

Worst feature. Ever. systemd saw this "feature" in windows, and have tried to implement it in linux as journalctl.

Semantic logging as implemented in the windows NT kernel, is a very complex framework kernel component but also very low performant, of course claims the contrary in the documented overview, but actually admits the subpar performance and non-robust implementation in other, not easily found, parts of the official msdn documentation.

For an inexperienced novice, heavily typed log messages can appear to solve problems, and such novice developers might think of untyped text causing problems. On the contrary, semantic logging, which journalctl is an obvious implementation of, do increase the complexity considerable, and many people before me have pointed out this critical design flaw. This complexity is easy to disregard in the name of heavily typed logging, complexity in software is hard to quantize, you need to accumulate experience before you realize complexity is very dangerous in software.

Logfiles that cannot be parsed by simple text based generic tools any longer is of course too complex. Instead heavy weight tools are now needed to be able to retrieve any information from systemd's behaviour. The "advanced query" functionality is said to require semantic logging. This is wrong (a lie actually), advanced querying tools for text based logfiles did already exist long before systemd was hacked together, no need to reinvent the square wheel.

Symptoms of too much complexity in software can appear in many forms, and TFS is a valid example as good as any. The bug in TFS is not unnatural, it's even expected to happen more frequently compared to more simple systems.

KISS FTW.