Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Python 3.14 compiled to metal – no interpreter

github.com

Post reply on HN
Print view View original

21–30 of 140 posts

Re: Python 3.14 compiled to metal – no interpreter

#21

Post by Dilettante_ »

himata4113 wrote: post #9
ubercore wrote: post #2

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…

This is written by fable with the guidance of a very experienced, highly skilled person. See their previous work.

"Very experienced" might mean different things to you. The oldest repo on their GH is from 2017. As for highly skilled: Could you point closer to which parts of their portfolio we are supposed to be awestruck by?

Re: Python 3.14 compiled to metal – no interpreter

#22

Post by ubercore »

mcphage wrote: post #10
baq wrote: post #4

Earlier quoted context omitted.

of course it is vibed. it doesn't matter as long as it works.

Given the stdlib modules listed as "explicitly not done yet", I'm going to say: it doesn't yet, in any meaningful sense. The question then becomes: how confident do we feel that it will work in the near future ?

I was trying to say "not confident at all" but hedged a bit too much.

I see this as a case of the "quick to get to a POC that falls apart after sustained development for the same reasons it didn't work pre-Fable" problem.

Re: Python 3.14 compiled to metal – no interpreter

#24

Post by bt1a »

subarctic wrote: post #12
leobuskin wrote: post #11

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).

"Without ai assistance" - ok, but what about with ai assistance?

it will be impossible to maintain parity with wetware

Re: Python 3.14 compiled to metal – no interpreter

#26

Post by all2 »

minimaxir wrote: post #18
zahlman wrote: post #14

Earlier quoted context omitted.

For a project like this, relying on AI assistance also makes it effectively dead in the water.

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.

Re: Python 3.14 compiled to metal – no interpreter

#27

Post by rurban »

leobuskin wrote: post #11

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

Re: Python 3.14 compiled to metal – no interpreter

#29

Post by ubercore »

rurban wrote: post #27
leobuskin wrote: post #11

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

How am I misreading this part of the readme?

> What is explicitly not done yet — this is the active roadmap, in order: > CPython test suite (cpython-full): the standing grind; failures are clustered and burned down per wave.

Re: Python 3.14 compiled to metal – no interpreter

#30

Post by leobuskin »

rurban wrote: post #27
leobuskin wrote: post #11

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

It passes only curated corpus (snippets), not the full CPython test suite. So, yes, reading is hard. Nothing against AI, btw.
Post reply on HN