On 6/3/2020 at 2:06 AM, StephenHorn said:
It's not that it's completely unreasonable to bring Python to a 65c02, at least in a theoretical sense. It's more that there's already a relatively inexpensive platform available that runs Python, allows for bit-banging on GPIO, outputs video, and will generally do everything the X16 can. I just don't see the point in programming with Python on an X16.
Yes, fine, the RPi is bogged down with its Linux OS, and there's more layers of encapsulation separating the programmer from the bare metal. But wouldn't that still apply to a Python implementation running on an X16? And if there's no appeal to PEEK and POKE things by hand (and VPEEK and VPOKE), and instead you want to add more libraries on top to reimplement the graphical features that'll be present in BASIC... well, again, why are we doing this on the X16, again? It strikes me as one of those college projects to run Linux on a toaster: the only purpose is to say "I did it", and then never touch it again. I'd reiterate that there's nothing wrong with that, but then it becomes a question of "why are people asking others to do the work for them, instead of working on it themselves"?
My response, right after I explain how Python is a terrible programming language and no one should ever use it, is to say "Go ahead and build it."
I figure you shouldn't be allowed to actually use Python until you can implement the virtual machine yourself. ?