#swiftnio — Public Fediverse posts

Books I would like to write but have no time:
- Robotic #Astronomy (actually, I do work on this)
- Server-Side #Swift with #SwiftNIO
- Astronomical Image Processing with #FITS
- Understanding Swift Macros
- Understanding Swift Concurancy
- Neuromuscular disorders - molecular pathways
- Understanding Computational Molecular Biology
- Writing Modern Unix Tools with Swift
- Designing an Exabyte File Archive
- Making Your Old House #Energy and Food Independent
- High Performance Swift

Today I was asked again (N-th time) to explain #SwiftNIO

My reaction: create a Git repository called `swiftnio-book`
—

My hope was that either @twostraws or @dimsumthinking will create such repo before me. Well, I still hope, and would gladly do `rm -rf swiftnio-book` if they do.

Introducing Oblivious HTTP support in Swift

#Swift #Programming #Networking #SwiftNIO #ObliviousHTTP
https://www.swift.org/blog/introducing-swift-nio-oblivious-http/

Last month I went to 2 Swift conferences and asked many #swift developers if they know anyone who is working on properly documenting #SwiftNIO.
It seams nobody that I know does this. So I am seriously considering to write a series of blogposts or even a book on the subject. Although SwiftNIO is one of the most important frameworks released by Apple, it is difficult to understand its architecture and design patterns and even more difficult to teach.

Any feedback?

Every time I return to coding Proxygen for Mac it kinda surprises me how awesome it is to be developing it. It ticks so many boxes for me: Mac development using AppKit, working with HTTP and networking, requires some amount of thinking and consideration of app architecture.

And it’s just so much more fun to click “Build and Run” and see the app launch on the same desktop.

And I get to use my own TestFlight build at work the following week.

So cool 🥰

#appkit #swift #swiftnio

“SwiftNIO is Apple non-blocking networking library. It can be used to write either client libraries or server frameworks and works on macOS, iOS and Linux.”

#SwiftNIO #Concurrency #Programming #iOS #macOS #Linux
https://www.process-one.net/blog/swiftnio-futures-and-promises/

If you use or want to use gRPC Swift, I have great news for you – work for gRPC #Swift v2 is currently being planned out:

https://forums.swift.org/t/grpc-swift-plans-for-v2/67361

IMO the biggest feature is the pluggable transport. This will allow client apps on Apple platforms to not require #SwiftNIO anymore. Instead Network.framework or URLSession can be used in those cases.

1. I feel seen.
2. There should be an option to select both. There are people who use Quick & Nimble, or even all three in the same codebase.

https://chaos.social/@fabianfett/110996267535170507

#Swift #SwiftOnServer #SwiftNIO #SwiftServer #SwiftLang

🧑‍💻⁉️ Please make your voice heard in the #Swift Server Working Group developer survey. Please do so, even if you don‘t use #SwiftOnServer today. We would love to understand your reasons.

#SwiftNIO #SwiftServer #SwiftLang

https://forums.swift.org/t/sswg-community-survey-2023/67084

I’m excited to help move #RediStack, a #Swift #Redis client build on top of #SwiftNIO, forward.

Read about @joannis and my plans:
https://forums.swift.org/t/redistack-future-plans/65703

I didn’t know that there is a Multicast Networking Entitlement which you need to request from Apple. Let’s see what Apple will respond.
Does someone has experience with this request?

https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_developer_networking_multicast

#Swift #iOSdev #swiftnio

@helge #Swift 5.5.0 has an issue with Sendability checking that was fixed in #Swift 5.5.2. Sadly #SwiftNIO runs right into this.