Viewing profile — hwpythonner

Compilers and optimizers are great tools for some use cases, but not all. Just to name a few limitations: - Many rely heavily on the CPython runtime, meaning garbage collection, in…

PyXL is a bit more direct :)

PyXL deliberately avoids tying itself to Python’s high-level syntax or rapid surface changes. The system compiles Python source to CPython ByteCode, and then from ByteCode to a har…

Fair point if you're looking at it through a strict compiler-theory lens, but just to clarify—when I say "runs Python directly," I mean there is no virtual machine or interpreter l…

Thank you so much — that really means a lot! It's still early days and there’s a lot more work ahead, but I'm very excited about the possibilities. I definitely see areas like embe…

Great question! You're right that it can definitely be faster — there's real room for optimization. When I have time, I may write a blog post that will explain where the cycles go,…

Thanks — yes, licensing is something I'm open to exploring in the future. PyXL already communicates with the ARM side over AXI today (Zynq platform).

Thank you!

No, I'm not paying for ModelSim. I've been using free tools like Icarus Verilog — it was good enough for my needs so far. If I need more performance later, I might migrate to Veril…

Good question — I’m not 100% sure. I'm not an expert on Ruby or JS internals, and I haven’t studied their execution models deeply. But in theory, if the language is stack-based (or…

Python’s execution model is already very stack-oriented — CPython bytecode operates by pushing and popping values almost constantly. Building PyXL as a stack machine made it much m…

Thanks so much — really appreciate it! Yes, it's been a one-person project so far — just a lot of spare time, persistence, and iteration.

Thanks — appreciate it! You're right that dynamic typing makes high-frequency execution tricky, and modern OoO cores are incredibly good at hiding latencies. But PyXL isn't trying …

Thanks — appreciate it! Good question. In theory, you can compile anything Turing-complete to anything else — ARM and Python are both Turing-complete. But practically, Python's mod…

The source isn’t public at this stage. I'm still deciding the best path forward after PyCon.

I'm a software engineer by background, mostly in high-frequency trading (HFT), HPC, systems programming, and networking — so a lot of focus on efficiency and low-level behavior. I …

Thanks so much — really appreciate it! Right now, the plan is to present it at PyCon first (next month) and then publish more about the internals afterward. Long-term, I'm keeping …

Not yet — I'm currently testing on a Zynq-7000 platform (embedded-class FPGA), mainly because it has an ARM CPU tightly integrated (and it's rather cheap). I use the ARM side to ha…

Thanks — really appreciate your insights. You're absolutely right that CPython bytecode changes over time and isn’t perfectly documented — I’ve also had to read the CPython source …

Thanks — and no worries, that’s a great question! Right now, PyXL runs fully in-order with no speculative execution. This is intentional for a couple of reasons: First, determinism…

Just running on FPGA at the moment. This is still an early-stage project — it's not completed yet, and fabricating a custom chip would involve huge costs. I'm a solo developer work…

Good question! PyXL today is aimed more at embedded and real-time systems. For server-class use, I'd need to mature heap management, add basic concurrency, a simple network stack, …

Thanks — really appreciate the interest! There are definitely some limitations beyond just memory or OS interaction. Right now, PyXL supports a subset of real Python. Many features…

Great points! Peripheral drivers (like UART, SPI, etc.) are definitely on the roadmap - They'd obviously be implemented in HW. You're absolutely right — once you have basic IO, you…

That's a great question! I actually thought a lot about that early on. In theory, you could build a CPU that directly interprets Python bytecode — but Python bytecode is quite high…