Warrior Maid

---

Summary

The Warrior Maid programming language is intended for critical (safety-critical, mission-critical, business-critical, and security-critical) software in harsh environments and high performance computing.

A short (and edited, no-context) story of how the idea of the Warrior Maid programming language came about.

It occured to me that none of the well known programming languages have a female logo or mascot. Even Ada (named for Augusta Ada Lovelace) doesn’t even have a female logo or mascot (not even an oldtimed locket with an image of her). With tens of thousands of programming languages, there might be an exception. Rust does have an anthropomorphic crab mascot with the slogan "“My pronouns are any—she/he/they/it are all great!”

I have long thought that the warrior maid trope in anime and manga was an interesting balance between masculinity and femininity.

Once I had settled on the name Warrior Maid for the programming language, the next question (which includes backstory and context) was what kind of language would fit that name and more specifically what kind of language that fits that name brings anything new or useful to programming languges.

Critical software. So far the best attempt has been Ada, but that is an old language and had serious problems on day one of release.

I would like to see Warrior Maid provide the reliability and mathematical soundness of functional programming (with distributed and parallel computing capabilities of Erlang/Elixir) combined with strong low level programming capabilies.

If the actor-message passing distributed system was applied between the functional programming and low level programming realms, then the two can be well isolated in different threads, core, or machines where a low level failure does not bring down the reliable functional programming code but provides the speed of low level code when needed.

That’s the basic idea of the Warrior Maid programming language.