[swift-server-dev] HTTP Parser
BAILEYC at uk.ibm.com
Sun Nov 6 03:44:11 CST 2016
Whilst it might not feel like it, it seems to be that we're all pulling in
the same direction.
>> I think if the API design feels “alien” to Foundation, then we either
need to update the Foundation API to feel like it fits in with Swift or
design the server API to fit in with Foundation.
>> I’ll keep pushing for this throughout the process. It’s really
important that we have a coherent stack of software from top to bottom.
Ending up with different model objects for URLRequest used in the same app
via two frameworks would be really unfortunate.
I think this completely aligns with what everyone is saying - we want/need
a coherent API stack with seamless interop between any new APIs and the
existing ones. The only thing we need to work on is the approach to
For me, and I think that this is the approach that Paulo is pushing for,
is that we should first look at "what do we think is the right approach",
without any constraints. Once we understand that, and any gap there is
between that and the Foundation approach, we can determine how we close
that gap - whether we can do that by evolving APIs, or whether it requires
compromises for the sake of developer experience and application code
From: Paulo Faria via swift-server-dev <swift-server-dev at swift.org>
To: Tony Parker <anthony.parker at apple.com>
Cc: Swift Server Dev <swift-server-dev at swift.org>
Date: 04/11/2016 23:08
Subject: Re: [swift-server-dev] HTTP Parser
Sent by: swift-server-dev-bounces at swift.org
> With respect to adopting other core Swift ideas like value types: we
turned 20 classes into value types last year. This included a ton of work
to adopt standard library protocols and improve type safety. It is an
absolutely huge surface amount of Foundation’s total API surface area.
It’s a large statement about how much we value making Foundation’s API
consistent for Swift.
Yeah! I really love the effort you’re putting into making Foundation more
“Swifty”. That doesn’t go unnoticed.
On Nov 4, 2016, at 8:49 PM, Tony Parker <anthony.parker at apple.com> wrote:
However, I do not believe there is such a fundamental conceptual mismatch
here that we cannot preserve one of the most useful aspects of developing
with the iOS, macOS SDKs - consistent types and low impedance mismatch
between API at all levels of the stack.
I definitely value "consistent types and low impedance mismatch between
API at all levels of the stack”. I just hope the APIs are designed with
the best of Swift in mind. Then after we get a good design, we can see if
it fits Foundation, and then make the adaptations there. I think this
approach would make Foundation follow along and become even more
“Swiftier” with time. Of course this is easier said than done, but I
believe that’s what would make the ecosystem as a whole become better for
swift-server-dev mailing list
swift-server-dev at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-server-dev