81–90 of 140 posts
Earlier quoted context omitted.
Why?
Time-cost for machines instead of willing knowledgeable humans. The former requires money, the latter requires passion. Arguably, passion for a project is without price.
Earlier quoted context omitted.
Even if it does cost thousands (does it? I genuinely have no idea how to scope such a thing) that might be a good price if a custom compiler to your custom target is something you really want. People have paid far more for far less. If you're a hobbyist trying to compile python to your weird little arduino based thing, then that's a lot of money and you would want to use somebody else's solution, no doubt. But if you…
> Even if it does cost thousands (does it? I genuinely have no idea how to scope such a thing) that might be a good price if a custom compiler to your custom target is something you really want. People have paid far more for far less. I wouldn't spend $100K in tokens to get a custom bare metal Python. Or even $10K. And I'd guess that most devs wouldn't either, unless they spend $10K like it's nothing. People that hav…
Earlier quoted context omitted.
"Without ai assistance" - ok, but what about with ai assistance?
For a project like this, relying on AI assistance also makes it effectively dead in the water.
https://github.com/Nonannet/copapy uses copy and patch, discussed here https://news.ycombinator.com/item?id=46972392
Single-pass SSA bytecode compiler and threaded-code stack VM for a sandboxed Python subset https://github.com/dylan-sutton-chavez/edge-python
Is it faster than the original interpreter? Maybe if you optimize out the primitives and certain well-known object types, unless you do some more advanced static analysis.
A few problems with this Fable's project: 1. It's not Python by any means, it's a subset with its own runtime, its own quirks and nuances; 2. It will be impossible to maintain parity with CPython without AI assistance; 3. It will die the same way as dozens of similar (even non-AI projects) died before, and reasons will be the same: (1) and (2).
Reading is hard. It runs and passes the full cpython testsuite, just 5x faster. With AI it's 100x easier to maintain than by hand. It reminds my on pperl. same approach using crane lift. Looks good
> Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that"
Earlier quoted context omitted.
>1. It's not Python by any means, it's a subset with its own runtime, its own quirks and nuances; A subset of python is python. Half a tomato is still tomato >2. It will be impossible to maintain parity with CPython without AI assistance What does that even mean? If you would have said that it's impossible to update to python 3.15 of further, I'd get it.
> A subset of python is python. Half a tomato is still tomato A subset of a calculator is still a calculator, but that subset definitely can't do everything the full version can.
A few problems with this Fable's project: 1. It's not Python by any means, it's a subset with its own runtime, its own quirks and nuances; 2. It will be impossible to maintain parity with CPython without AI assistance; 3. It will die the same way as dozens of similar (even non-AI projects) died before, and reasons will be the same: (1) and (2).
Reading is hard. It runs and passes the full cpython testsuite, just 5x faster. With AI it's 100x easier to maintain than by hand. It reminds my on pperl. same approach using crane lift. Looks good
The irony…
I hate to be that guy, but... one week old project, clear signs of vibing. I will be shocked if the remaining work listed (cpython test suite) proceeds in any reasonable timeline. This is a pretty hard problem to just solve in a week. EDIT: and man, these kind of comments LLM created comments are really starting to grind my gears as my job slowly turns into reviewing LLM PRs: > Known gaps at the language level are bu…
of course it is vibed. it doesn't matter as long as it works.