2 ms·
It's taking a long time because they don't want to break existing code, and don't want to loose too much single core performance. I'd say that counts as inheren
by Zababa 5y ago
It's taking a long time because they don't want to break existing code, and don't want to loose too much single core performance. I'd say that counts as inherent difficulty in changing the language. I'm not aware of other languages trying to retrofit multicore without breaking existing code, but I'm sure if any did other people will correct me and can say how it went.
Edit: they're also working on an effect system at the same time, making everything fit into a 25 years old language that's really stable is not trivial.
- UncleOxidant 5y agoI kind of wonder why they don't make multicore an option to the compiler so that if you were willing to sacrifice single-core performance to get multi-core benefits you'd just say 'ocaml -mc' or something.