5 ms·

My understanding (and I invite correction if I'm mistaken) is that the Swift Foundation was created to address the principal concerns you've articulated. But po

My understanding (and I invite correction if I'm mistaken) is that the Swift Foundation was created to address the principal concerns you've articulated. But ports have been slow: Linux works but with the previously mentioned lack of libraries, and there is a threadbare port to Windows which barely runs. The app I was working on was CLI-based that generated a log; and even for that non-UI use case, basic libraries were effectively missing. It's a shame because it's truly an elegant language.

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 ago
  Distributed 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.
DaiPlusPlus 5y ago
> is that the Swift Foundation was created to address the principal concerns you've articulated Swift does not have an incorporated "Swift Foundation", instead Swift.org's about-us page is surprisingly frank about Apple's control over the language and ecosystem ( https://swift.org/community/ https://swift.org/community/ ): > Apple Inc. is the project lead and serves as the arbiter for the project. The project lead makes senior appointments to leadership roles, with those leaders coming from the worldwide Swift community of contributors And the site's footnote reminds us that Swift.org is not separate from Apple, but again, owned by Apple Inc. -------------- On an unrelated note, the .NET Foundation had an upset a few weeks ago: https://www.theregister.com/2021/10/11/dotnet_foundation_community_issues/ https://www.theregister.com/2021/10/11/dotnet_foundation_com...

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 ago
Distributed 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.

DaiPlusPlus 5y ago

> is that the Swift Foundation was created to address the principal concerns you've articulated Swift does not have an incorporated "Swift Foundation", instead Swift.org's about-us page is surprisingly frank about Apple's control over the language and ecosystem ( https://swift.org/community/ https://swift.org/community/ ): > Apple Inc. is the project lead and serves as the arbiter for the project. The project lead makes senior appointments to leadership roles, with those leaders coming from the worldwide Swift community of contributors And the site's footnote reminds us that Swift.org is not separate from Apple, but again, owned by Apple Inc. -------------- On an unrelated note, the .NET Foundation had an upset a few weeks ago: https://www.theregister.com/2021/10/11/dotnet_foundation_community_issues/ https://www.theregister.com/2021/10/11/dotnet_foundation_com...