All blog posts from MiraNova Studios
MiraNova Studios is temporarily pausing active development on Lyric and Nova this week to allow focused time for completing Michael’s personal novel project.
This short pause ensures creative continuity and provides a clear mental transition before the next development phase.
Regular development will resume next Monday or earlier as inspiration allows.
— MiraNova Studios
It’s been another exciting week here at MiraNova Studios. Here are some of our key accomplishments for the week.
Infrastructure:
Lyric Core Enhancements:
Completed a major type system refactor with explicit declarations (int x = 5, def add(int a, int b)).
Added class constructor support, improved exception handling, and introduced new control-flow keywords (break, continue).
Added AST line-number tracking for clearer parser and runtime error reporting.
Watching Lyric grow from concept to prototype to core implementation has been a dream come true — and we're excited for what's next.
(edited)
Build. Learn. Iterate.
— MiraNova Studios
I’ve decided not to release a developer preview of Lyric. Instead, I’ll continue refining the language and move toward a more stable public release.
My goal has always been to deliver something complete, reliable, and genuinely useful — not just “in progress.” Taking this extra time will help make Lyric more stable and true to the vision I started with.
Development is still moving quickly, and I’ll share more updates soon as we approach the release milestone.
I opened CloudFront's graphs tonight to check our site traffic.
I'm still not sure if I found requests data or a lost piece of digital art.
If anyone can explain what these charts actually mean, please let me know (or send an art critic).
Thank you
This week we ran the first performance comparison between Lyric and native Python, and the results surprised us.
In our first performance test, Lyric version 0.5.0 completed a series of simple computation and function call benchmarks 1.33× faster than native Python, with execution times of 0.99 seconds versus 1.31 seconds respectively. (This is assuming importpy time is working correctly, which we think it is.)
Python execution time: 1.3136 seconds
Lyric execution time: 0.9891 seconds
Lyric is 1.33x faster than Python
Performance difference: 0.3245 seconds
Here are the test scripts we used for our first benchmark:
We're excited to go live with Lyric's documentation and home page — lyric-lang.org — planned for Friday evening.
We're also preparing to release a developer preview of Lyric 0.6.0 over the weekend.
(edited)
It’s been just one week since we officially began development at MiraNova Studios — and what a week it’s been.
We’ve validated our AI-assisted development strategy, built a working prototype of our programming language Lyric, bootstrapped the Nova AI editor project, and launched our studio website. Lyric already runs real code through its interpreter, and Nova is taking shape as the foundation for everything we’ll build next.
We also secured lyric-lang.org and published our reserved package lyric-lang on PyPI, marking the first official presence of Lyric in the wider ecosystem.
Most importantly, this week proved that our approach works. With structured sprints, AI collaboration, and disciplined documentation, we’re moving faster — and learning more — than we ever thought possible.
This is just the beginning.
Build. Learn. Iterate.
— MiraNova Studios
Welcome to Pulse, the heartbeat of MiraNova Studios! This is our first blog post, and we're excited to share our journey with you.
In the coming weeks and months, you'll find: