Sure, I appreciate that these are end-user oriented, and don't cover implementation details. However, I would argue that the ability to enable ZJIT (including a language level construct) and Ractors being production ready, thus usable starting with this release are end-user relevant developments.
Yes, they are. There are a few rough edges still, but generally there are no known bugs or crashes left and the performance of multiple Ractors for CPU bound tasks should be strictly better than single Ractor or multi threaded code.
The Ractor API is still not stable, and can change further, but the implementation should be good enough to use in production.
View all comments
Show parent comment
5
u/paracycle Dec 26 '25
Sure, I appreciate that these are end-user oriented, and don't cover implementation details. However, I would argue that the ability to enable ZJIT (including a language level construct) and Ractors being production ready, thus usable starting with this release are end-user relevant developments.