Pemu 2 announcement

Although the full release of Pemu was very close, I have decided to nearly scrap Pemu 1 entirely. Work on Pemu 2 has commenced, and the speed increase is expected to be immense. Pemu 2 will have lots of the features a real computer has but that Pemu doesn't, such as variable length instructions and flags. The instruction set of Pemu 2 will be entirely different to Pemu 1, but it will come with a assembler to handle all the fine details. Pemu 1 was (mostly) 16 bit, but Pemu 2 will be fully 32 bit. The new assembler will have support for writing binary and hex, not just the current decimal.  About 1/13 of Pemu 2 is complete, and that is from 3 days of progress. Just to finish Pemu 2 will likely take 2-4 weeks. Pemu 2's assembler will likely take about a week to get done as well. I plan on releasing Pemu 2 when the assembler is done, not after I finish the new version of Plow. I also plan on releasing Plow 2 for Pemu 2. I'm considering adding support for writing binary code directly into the assembly code, despite it's meaninglessness since Pasm 2 will be a direct translation to Pemu 2 code. I plan to move this binary support up to the highest level of Peak 2.  In the source code Pemu 1 and Pemu 2 will be similar, just Pemu 2 will be considerably easier to maintain partially because Pemu 2 will be written in Python. The target language is still Rust though, so no performance losses. Considering making the target language C just to really maximize performance, but the generated code is already so fast I can't test it's fastest speeds on my high-end computer.

I don't really know why anyone else would be as interested in this very niche subject as I am, but I enjoy looking at every single layer of abstraction that builds up to something like Python.  I have done my partial best to ensure it as easy for someone else to buildup their own layer of abstraction from any point in the layers, from Pemu to Plow. So like if you don't like my syntax choices for Plow or Pasm or the compilation times you could write your own compiler. Although I am always open to suggestions.