swift-protobuf VS Swinject

https://docs.rs/prost/latest/prost/ crate lets you encode / decode protobuf messages. You can write a message which represents your struct or whatever data type is, set the fields, and then encode it into bytes. Decoding in swift can be done with something like this https://github.com/apple/swift-protobuf ig.

I’ve used Protobuf in Swift and it was pretty straightforward. Apple already provides a tool chain [1] so using a third party is a hard sell.

[1] https://github.com/apple/swift-protobuf

> Why should they? That isn't their target audience.

Because they need it?

Apple discontinued macOS server, i bet they use Linux in some of their servers

All their networking related libs are available and tested for Linux [1, 2]

Let's not forget that they package Swift for Linux, and now also for Windows [3]

Swift is crossplatform language (you not wanting to understand it doesn't change this fact), it's not a macOS framework

[1] - https://github.com/apple/swift-nio

[2] - https://github.com/apple/swift-protobuf/blob/main/.github/wo...

[3] - https://forums.swift.org/t/announcing-swift-5-6-2-for-linux-...

Swift Protobuf - Plugin and runtime library for using protobuf with Swift. Language: Swift.

I need to explore using Protobuf -> Swift (https://github.com/apple/swift-protobuf) then using the Kotlin Native to Swift interop: https://kotlinlang.org/docs/native-objc-interop.html

Thanks. I downloaded and installed https://github.com/apple/swift-protobuf. Is that the tool you are talking about? This creates a blank .proto file and generates .pb.swift files but I am stuck on creating the Starlink .proto file. Do you have a StarLink .proto file? I was successful in creating a protoset file but not a .proto file. Any advice would be greatly appreciated.

DI is a concept which makes a class independent of its dependency management. It achieves that by decoupling the usage of an object from its creation. This helps you to follow SOLID’s dependency inversion and single responsibility principles. To achieve this in Swift one of the most appreciated library is Swinject. This library not only provides DI but also have many other features like:-

Swinject - Dependency injection framework for Swift. Language: Swift.

We use Swinject which is probably quite similar https://github.com/Swinject/Swinject

So, how do we fix this? There is a cleaner solution. By using a dependency injection framework, such as Swinject we can create a base module that we might call the DI module.