4 ms·
It's made quite clear every summer that Apple has a stranglehold on the language steering committee. When a new language feature that just so happen to enable a
by b3morales 5y ago
It's made quite clear every summer that Apple has a stranglehold on the language steering committee. When a new language feature that just so happen to enable a closed-source Apple framework drops out of the blue and then goes through a retroactive pseudo-open review.
Frankly, this distributed actors thing is more of the same -- it's something that someone at Apple thinks is important, so, despite it being just a library, it gets active support from the compiler and OS teams. There's absolutely no way that an outsider could have gotten anywhere proposing anything like this.
I like Apple's platforms and enjoy working with the language as well, but the openness is rather a charade.
- ecs78 5y agoDistributed actors don’t actually have compiler support. They use a standalone code generator much like GRPC. The plan is to call the generator automatically during a build process using upcoming SPM plugin support. EDIT: It looks like there is a plan to remove the SPM plugin and make it a first class feature. This work just started and is going through a normal evolution process.
- b3morales 5y ago> Distributed actors don’t actually have compiler support. I said from the compiler and OS teams -- there are at least two compiler engineers listed on the proposal. But this is insupportable nonsense anyways: `distributed` is a brand new keyword, there are new rules about how inits work, magic property behavior... I haven't followed the proposal carefully, but there are also new toolchains being generated to enable the feature.