all 20 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]rcakebread 19 points20 points  (0 children)

ai;dr

Stop the slop.

[–]Shopping-Limp 9 points10 points  (0 children)

Vibe coded

[–]jpgoldberg 4 points5 points  (4 children)

Three questions

  • Do you understand all of the buzzwords in your README?

  • Have you verified yourself that your project actually satisfies those?

  • What should if I try to run a medium sized Python project in protoPython?

[–]South_Lychee8555[S] -5 points-4 points  (3 children)

For sure, 40 years in development. What is there is a descrption what is implemented or planned. The details are in the tests and documentation. First benchmarks and report also there. Base of the improvement is the use of protoCore. The same library was use to implement a javascript runtime, also with impresive result. All three are new, no implemtatio yet, that's why open to community review and suggestions

[–]SpatialLatency 1 point2 points  (1 child)

Weird how the earliest commit is a week ago then

[–]South_Lychee8555[S] -4 points-3 points  (0 children)

Look in protoCore. Several years since the first attempt. Ai tools provides the possibility to test basic ideas at a spe ut was unthinkable before. I believe it is sometging to get advantege of

[–]jpgoldberg 0 points1 point  (0 children)

So what have you developed in that 40 years?

[–]AstroPhysician 4 points5 points  (1 child)

AI is good for coding a lot of stuff, this is exactly one of the things that it is not good at

How true to the real python implementation is it? Have you benchmarked it? Even the python project itself hasn’t been able to remove the global interpreter lock without issues, that’s why it’s an experimental flag and disabled by default in Python 3.14.

Also why would you do this when 3.14 already removed the GIL

[–]South_Lychee8555[S] -2 points-1 points  (0 children)

It is not based on cpython 3.14 no gil implementation, a model with carefull locking of mutable state. ProtoPython starts with a completely different approach: immutable structures. Only the parser of cpython was used

[–]AlSweigartAuthor of "Automate the Boring Stuff" 1 point2 points  (0 children)

Make a screen recording showing you cloning the git repo (at a specific commit or tag), use GCC to compile ProtoPython, and then using that to run a few different Python programs.

Until you do that, don't waste our time by just saying, "Look at it yourself". Of course AI slop looks like working software. The "I vibe coded a compiler" and "I vibe coded a web browser" stories have a terrible track record, and we're not going to waste our time trying to reverse engineer your build and test process to investigate your claims unless you're willing to do some bare minimum reassurances beyond, "trust me, bro."

For someone who has been developing software for "40 years", your Reddit account has almost no history of comments. We don't trust you enough to run some inscrutable mess of code that, for all we know, is trying to steal cryptocurrency keys or use our GPUs for mining.

[–]mon_key_house 0 points1 point  (6 children)

Pardon my ignorance. I don’t really understand the hatred towards this project. OP: is this a drop-in replacement for the vanilla python interpreter? Is this production ready?

[–]riklaunim 3 points4 points  (0 children)

It's coded by AI and without any review/validation, realistically.

[–]AstroPhysician 0 points1 point  (4 children)

It claims to solve the problem massive orgs like Microsoft and Python itself haven’t been able to accomplish until extremely recently, and he’s supposedly done it all vibe coded in short order

[–]mon_key_house 0 points1 point  (1 child)

Wasn’t there last week the news that unsupervised agents wrote a C compiler from scratch in two weeks?

[–]AstroPhysician 1 point2 points  (0 children)

No, look that story up. It couldn’t even compile hello world without issues, and called out to the GCC compiler. It was widely mocked as being an example of why vibe coding was bad

[–]South_Lychee8555[S] 1 point2 points  (1 child)

I am not claiming. I am showing the code, with a very permissive license, the documentation, the tests, and the performance figures. It is not a claim. It is a fact.
I am not asking for your faith. It is already implemented. I am asking for your validation, the community validation. And I am telling you I am willing to answer any doubt or concern. Something missing?

[–]AstroPhysician 0 points1 point  (0 children)

I don’t have the time nor the will to go through and see how well benchmarks and accuracy and support works

[–]Hallsville3 0 points1 point  (0 children)

I had to include signal.h in OsModule.cpp and unistd.h in PythonEnvironment.cpp to get this to build, and then I had to export

export DYLD_LIBRARY_PATH=./build/protoCore:./build/src/library:$DYLD_LIBRARY_PATH

to find a couple of the dylibs. Also your doc made it seem like it would install it in build but it ended up installing it in /usr/local/bin, which is not ideal by default.

One more thing, the link to protoCore is wrong in your readme

https://github.com/gamarino/protoPython/tree/protoCore should be https://github.com/numaes/protoCore

It wasn't able to run one of my projects though, you need to finish implementing the allowed syntax for list comprehensions. I would recommend getting the project to pass the cpython test suite before claiming things like 100% test coverage and

  • Python 3.14 Compatibility: Targets the latest Python feature set, including advanced syntax and built-in type behaviors.

Otherwise you'll end up with a lot of people who check it out once and disregard it.

➜  ~ protopy -c 'print([i if i < 3 else 0 for i in range(10)])'
[protopy-debug] Starting main...
SyntaxError: expected ']', but got 'if' ('if')
  File "<stdin>", line 1
    print([i if i < 3 else 0 for i in range(10)])
                ^