Hi Carra!
Cool project! I don't use Twitter or Discord and I couldn't find your email address (on github or your webpage) so I thought I'd open a github ticket ticket to give some feedback and ask a couple of questions if you don't mind?
I have to mention the Uzebox first. You do know about it right? Its the OG open source 8 bit console so I was a bit disappointed to not see it mentioned on https://www.vircon32.com/about.html. You should check it out if you've never heard of it and join the forums:
https://uzebox.org/
Its for people who like restrictions, weird platforms, retro computing/games and DIY electronics - I think that might include yourself?
The Vircion32 is much more powerful than the Uzebox but the Uzebox seems to still have a few advantages. First, its been around since 2008 so its got a lot more documentation, source code and games. It has had at least 30 different clones made in the last couple of decades. It is also a real, physical console that electronics beginners can build themselves for less than $50 and the Uzebox Omega only uses one chip.
I like pretty much everything about the Vircon32 apart from it using a variant of C. Most Uzebox games are written in regular C and compiled with avr-gcc, or you can use AVR assembly. You say in the FAQ that the Vircon32 won't support standard C so this another advantage for the Uzebox in my eyes at least. The Uzebox has its own C API but it uses regular C (or C++).
The only other thing I'm uncertain about is the CPU. Is the Vircon32 using a custom CPU? Why? Surely it would've made more sense to use a RISCV, ARM or another standard CPU to take advantage of existing toolchains? I'd like to know your thinking behind using a custom CPU if thats what you've done.
Keep up the good work!
Hi Carra!
Cool project! I don't use Twitter or Discord and I couldn't find your email address (on github or your webpage) so I thought I'd open a github ticket ticket to give some feedback and ask a couple of questions if you don't mind?
I have to mention the Uzebox first. You do know about it right? Its the OG open source 8 bit console so I was a bit disappointed to not see it mentioned on https://www.vircon32.com/about.html. You should check it out if you've never heard of it and join the forums:
https://uzebox.org/
Its for people who like restrictions, weird platforms, retro computing/games and DIY electronics - I think that might include yourself?
The Vircion32 is much more powerful than the Uzebox but the Uzebox seems to still have a few advantages. First, its been around since 2008 so its got a lot more documentation, source code and games. It has had at least 30 different clones made in the last couple of decades. It is also a real, physical console that electronics beginners can build themselves for less than $50 and the Uzebox Omega only uses one chip.
I like pretty much everything about the Vircon32 apart from it using a variant of C. Most Uzebox games are written in regular C and compiled with avr-gcc, or you can use AVR assembly. You say in the FAQ that the Vircon32 won't support standard C so this another advantage for the Uzebox in my eyes at least. The Uzebox has its own C API but it uses regular C (or C++).
The only other thing I'm uncertain about is the CPU. Is the Vircon32 using a custom CPU? Why? Surely it would've made more sense to use a RISCV, ARM or another standard CPU to take advantage of existing toolchains? I'd like to know your thinking behind using a custom CPU if thats what you've done.
Keep up the good work!