Updated: June 2020
I’ve created this page to informally explain some behind-the-scenes points about the development of Microvium — things that probably don’t belong in the repository or formal documentation, but which nevertheless may be interesting to some people.
I’ll treat my normal blog posts as essentially an immutable history of things I’ve been doing (Microvium or otherwise), while I’ll try to instead keep this page updated with the latest information1.
Started in February 2020. Still a baby.
Microvium also brings its own unique flavor and tradeoffs to the table of options to choose from.
Expect these numbers to change a bit over time.
Compiled for a 16-bit architecture:
- The engine currently uses 8 kB of ROM in its most-compact configuration.
- A bytecode image has a fixed overhead of 44 B of ROM.
- Each instance of a VM has a fixed overhead of about 24 B of RAM while idle.
- Beyond that, the usage depends on how big your script is and what it does.
The reasons are mostly personal. I think Microvium would be almost exactly as useful if it were closed-source, but by making it open-source, I don’t need to develop the project on my own in silence and isolation like I was with MetalScript. I much prefer being able to openly share ideas and collaborate.
Not only have I open-sourced it, but I’ve also used a very permissive license (MIT) for both the compiler and bytecode interpreter, making it easy for anyone to incorporate Microvium into other projects, without needing to worry much about legal issues, security issues, or what happens if Microvium stops being maintained.
(I might change this at some point to a dual-licensing model, where you can use it for free for non-commercial use but contribute financially to its development if you use it for commercial use)
I’m intentionally trying to avoid committing formally or informally to any particular development path or schedule. It just adds unnecessary stress to my life. Just on a personal level, I’m starting to realize that always having my head in the future, on what-could-be-but-isn’t-yet, is detracting from the great things that already exist right now and putting me in a kind of psychological “debt” — a deep and unsatisfying sense that the current reality is always less than I want it to be.
Having said that, no doubt there will be many cool things coming to Microvium in the future — the list of possibilities of directions I could go with this seems endless. Subscribe to my blog to get updates on new developments.