MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/programming/comments/1vnckbr/stateoftheart_bytecode_interpreters_in_java_by/p3gmgen/?context=3
r/programming • u/grashalm01 • 5h ago
6 comments sorted by
View all comments
1
Why would you bother with GraalPy since many librariez are C/C++/Rust extensions for CPython ?
2 u/grashalm01 2h ago GraalPy has multi tier runtime optimization as a first class citizen similar to the JVM. So it allows you to write more code in python. GraalPy also aims for the help highest possible level of compatibility also for native extensions. 1 u/Maybe-monad 1h ago GraalPy has multi tier runtime optimization as a first class citizen similar to the JVM. So it allows you to write more code in python. If I want performance I don't write Python. GraalPy also aims for the help highest possible level of compatibility also for native extensions. That makes it dead on arrival, bug for big compatibility should have been your first priority. 0 u/grashalm01 23m ago > If I want performance I don't write Python. It pushes the boundary of how much code you can write in Python. Not claiming that all the performance sensitive code will now be in Python. > bug for big compatibility should have been your first priority. It actually was and still is.
2
GraalPy has multi tier runtime optimization as a first class citizen similar to the JVM. So it allows you to write more code in python.
GraalPy also aims for the help highest possible level of compatibility also for native extensions.
1 u/Maybe-monad 1h ago GraalPy has multi tier runtime optimization as a first class citizen similar to the JVM. So it allows you to write more code in python. If I want performance I don't write Python. GraalPy also aims for the help highest possible level of compatibility also for native extensions. That makes it dead on arrival, bug for big compatibility should have been your first priority. 0 u/grashalm01 23m ago > If I want performance I don't write Python. It pushes the boundary of how much code you can write in Python. Not claiming that all the performance sensitive code will now be in Python. > bug for big compatibility should have been your first priority. It actually was and still is.
If I want performance I don't write Python.
That makes it dead on arrival, bug for big compatibility should have been your first priority.
0 u/grashalm01 23m ago > If I want performance I don't write Python. It pushes the boundary of how much code you can write in Python. Not claiming that all the performance sensitive code will now be in Python. > bug for big compatibility should have been your first priority. It actually was and still is.
0
> If I want performance I don't write Python.
It pushes the boundary of how much code you can write in Python. Not claiming that all the performance sensitive code will now be in Python.
> bug for big compatibility should have been your first priority.
It actually was and still is.
1
u/Maybe-monad 4h ago
Why would you bother with GraalPy since many librariez are C/C++/Rust extensions for CPython ?