Status¶
MakrellPy is currently one of the strongest reference points in the family for:
core language behaviour
macros and metaprogramming
pattern matching
Python host interop
Practical reading of that status¶
MakrellPy matters because it still answers many of the questions readers are likely to ask first about the language family:
what do the language forms feel like in regular use?
how do macros and meta execution work in practice?
what does strong host interop look like in a mature implementation?
It is not the only important implementation, but it remains one of the most useful places to understand the family in depth.
What this means for readers¶
If you are exploring the family and want a practical language-oriented entry point, MakrellPy is often a good starting choice. It gives you a broad view of:
everyday language flow
functional patterns
macros and quote/unquote
pattern-oriented programming
Python integration
That makes it especially useful as a comparison point when you later look at MakrellTS or Makrell#.
What this does not mean¶
MakrellPy being a strong reference point does not mean it is the only track that matters. The TypeScript and .NET implementations are important in their own host ecosystems and for testing the family design across different runtime worlds.
Instead, the practical takeaway is:
MakrellPy is often the best place to learn broad language behaviour
MakrellTS is often the best place to learn JS/TS alignment
Makrell# is often the best place to learn CLR and .NET integration