While there are definitely some iOS/macOS devs using Swift in tasks that aren’t directly related to Apple’s ecosystem, I wonder how many companies are there, looking for people specifically with server-side Swift experience or experience with Swift developer tools (compiler, SwiftPM etc). Anyone looking for server-side or full-stack Swift developers? If so, let me know, I will be happy to publish a link to a related job description in the future issues.
In the meantime, Brian Gesiak tweeted about vacancies for developers interested in open-source tools.
In the previous issue I’ve mentioned benchmarks done by IBM, where they compared performance of Kitura with Vapor. Qutheory weren’t able to reproduce the benchmarks on their hardware as you can see from their post. I look forward to seeing comprehensive benchmarks done on various hardware, ideally performed on regular basis with visible changes version by version, which would hugely benefit the community.
It looks like yet another Swift Evolution proposal might be accepted for Swift 3.0. Is quite late in the development cycle, but the actual proposal is quite important in the light of promised Swift 4.0 binary compatibility. Here is motivation from the proposal text:
We only realized very recently that, although Swift 3.0 is not shipping with a stable ABI, the promise that Swift 3.0 code will work with Swift 4.0 means that many of the standard library’s protocols will be locked down now. Especially where these protocols show up in refinement hierarchies, we won’t be able to keep Swift 3 code working in the future without carrying them forward into future standard library binaries.
Another week, another link to a great talk! This one is by Aaron Grattafiori speaking on DockerCon 2016 about impact of microservices on systems security. The talk starts with a nice summary of all the drawbacks and benefits of monolithic/microservices architectures and proceeds with a list of best practices that you would follow when building microservices. While some of the examples are Docker-specific, I would say that most of the info is very useful to anyone interested in security of backend systems.
Marcin Krzyzanowski published a quite comprehensive page with a description of Package.swift file that’s used by Swift Package Manager. This is very neat, as I personally find quite hard to get started quickly by following just official Apple’s documentation on SwiftPM.
Imagine a Linux where you can test and roll back configuration changes, where multiple versions of the same library or application can live in harmony, and where the full state of the system is recorded declaratively. As any promotional paragraph beginning with “imagine” implies, this thing exists: NixOS
I think machine learning and computer vision (and the rest of the things labelled as AI these days) are going to be very powerful in cloud applications. If not focused solely on cloud, augmenting front-end ML code is as important. Thus I continue picking some of the links that provide gentle introduction to these topics.
Finding this was quite a surprise to me, as it isn’t published under Zewo’s GitHub organisation, while it references Zewo’s Slack team on its README page. So far it looks very promising:
Quark is a framework heavily inspired by the Clean Architecture and The Twelve-Factor App. We believe that frameworks should do their best to make the developer’s life easier while maintaining freedom. Applications built with Quark are architected in a way that the business logic is separated from the delivery mechanism (the web). This provides longevity for your application to evolve as the web evolves and incorporate new ways to deliver your application (real-time web apps for example). Quark’s architecture also allows you to test your business logic with no dependencies on the web or the database. You can have integration tests without booting up a server too.