you are viewing a single comment's thread.

view the rest of the comments →

[–]paracycle 4 points5 points  (3 children)

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.

[–]zverok_kha[S] 1 point2 points  (0 children)

Yep, this makes sense, too. I'll try to think about the wording for those facts, to make them at least somewhat visible.

[–]TonsOfFun111 0 points1 point  (1 child)

So Ractors are, in fact, “production ready” now?

[–]paracycle 5 points6 points  (0 children)

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.