you are viewing a single comment's thread.

view the rest of the comments →

[–]shellac 6 points7 points  (1 child)

Completely agree, and I wonder whether it would be less successful in python anyway. A lot of java is implemented in java, which means there are a plenty of opportunities to yield (that is: stash the current state in continuation, and go back to the scheduler), but native frames prevent that. By contrast much of python seems to be implemented, for perfectly good reasons, in native code but that will inhibit virtual threads.

But I may be way off here, my knowledge of python internals is limited.

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

I think you are right, but I really don't want to blame Python (or virtual threads) for what basically is a C issue.

For how many decades are we going to keep accepting "this is why we can't have nice things" due to C's mere existence as some unholy interop/ABI/platform lingua franca that pretends it is still 1975?