No particular reason. I've liked high-level capabilities that would translate into very low level code and amount of control, but on the other hand I couldn't use existing AVR backend because it produced very verbose code, so I ended up using Zig-to-C and avr-gcc, but it also produced subpar machine code which I was unhappy with. E.g. for loops that were bound by less than 255 iterations — 1 byte — it produced 4 instructions while 3 were enough, if I remember correctly). And for protocol implementations where timings are strict I've simply ended up with sprinkling code with ASM insets here and there to match timings. I also liked the fact that I could set ATTiny fuses straight in zig's comptime, but then they updated zig and that particular edge-case stopped to work.
How so? Even in a jurisdiction where corporate officers aren't required to be a natural person, trying to have an AI CEO is like trying to make a cat/dog a CEO. As a practical matter, it is not a legal entity recognized as capable of entering into agreements so no government or other business will accept legal documents, contracts, etc. signed by the AI CEO or signed by a human claiming to act under the AI's (not valid) authority as CEO delegated to them. If I had to guess the latter would likely be considered fraud.
Unless some movement forms to get broad agreement that an AI instance can constitute a legal person (some kind of AI equivalent of corporate personhood, which nobody seems to like), this project is DOA.
reply