So, C speed with Python semantics?
That's already what PyPy is, isn't it? (Not really C speed, but the method in the article is just calling the PyPy interpreter, so it's not quite C speed anyway.)
Implementing programming language interpreters is a bigger topic than a HN topic... but in general when things are easier from the programmer's perspective, then the machine needs to do significantly more work to get things right.
This is especially true in Python, where 1 + 1 doesn't necessarily mean "add one to one" because the integer literals (1) and the addition operator (+) can be overloaded to mean different things. Even at runtime, it's possible to have the same written code and different semantics.
C's semantics are much closer to how the hardware operates. In order to code effectively and efficiently in C, you need to understand much more nitty gritty details about how computers operate.
This is one of the approaches I am pursuing to polish off something I put together recently: rapid prototyping of LD_PRELOADs in Python.
I presented an early approach at PyData London last week using LD_AUDIT and `cython`: https://www.youtube.com/watch?v=L3j2qw9XZCc
It doesn't seem that amazing to be able to write:
@preload
def open(pathname: 'const char*', flags: 'int') -> 'int':
return __open__(pathname, flags)
After all, this is only slightly more convenient syntax than in C. However, imagine how much functionality you could quickly develop with access to the Python standard library.Even using my clumsy `cython` and `LD_AUDIT` approach, I was able to rapidly develop libraries that interpose file-handling library calls and implement:
# `less` is used as an example of a libc programme with no concept of Python, git, &c.
$ COMMIT_HASH=abc123 gitit less test # interact with files as-of some commit in a git repo via pygit (libgit2)
$ runit less test.py # redirect read() so that the contents of the file appears to be the results emitted of having run the file
$ zipit less test.gz # redirect read()/write() to transparently handle gzip files
Each one of these took about half an hour to throw together, which is substantially faster than I could reliably develop them in pure-C (not to mention how much code I avoid having to write myself by relying on Python's rich stdlib & ecosystem.)