-
Ha, nice! I've used the Swift shebang before, but honestly once you have something that works as a "script," it's so easy to convert it to a real command line utility via Swift Argument Parser [0] that I usually spend the 5 minutes to wrap it up.
[0]: https://github.com/apple/swift-argument-parser
-
Stream
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
-
As with other languages, you’d need bindings to another UI framework. In that sense, I wish SwiftUI had a different name because it seems intrinsic to Swift when it’s really no different than UIKit.
There’s stuff like SwiftCrossUI that does multiple backend bindings
https://github.com/stackotter/swift-cross-ui
And Qt was exploring some bindings using the new C++ interoperability.
-
C# does pretty well as far as WASM support goes, unlike Go which is abysmal :)
https://bootsharp.com/guide/llvm / https://github.com/elringus/bootsharp
-
-
> It would be a long time until Swift is even remotely ready for something like this and I don’t feel there is a burning need to have “yet another wasm platform”.
I mean, well, it actually does exist? It's been around for a long time and works pretty great, with multithreading, access to JS objects, etc.
https://swiftwasm.org/
-
Shaft
A cross-platform GUI framework for Swift, built for demanding workloads and developer ergonomics
There’s also Shaft, which is Flutter ported to Swift:
https://github.com/ShaftUI/Shaft
Like Flutter, this paints everything itself. It doesn’t need to bind to a UI framework directly. Instead, it needs the platform to provide primitives like a surface to draw into and input events.