Increasing visibility of server side swift platform gaps?

[taylorswift]

@hassila

hoping that we'll over time evolve an ecosystem with smaller packages that supplants Foundation as things move forward - it is quite painful now though with things like calendars and timezones etc...)

@AlexanderM

Right now we're in a nonsensical middle-ground, where Apple owns the direction and API design, but has no incentive to implement anything that isn't for their platforms.

@mickeyl

I think the main problem is that many people in the "Server-side Swift" community seem to take the "server" very seriously, thus completely ignoring developers who want to write cross-platform software that does not necessarily do "server" things.

one question we really need to answer as a community is “what does cross-platform mean”?

1. packages that support linux only, instead of Apple platforms only, or
2. packages that support linux and Apple platforms.

as a “server” library developer, #1 is easy for me, since my personal use case is almost always linux first.

on the other hand, i and others have had great difficulty ([0], [1], [2]) achieving the latter. which is not ideal.