We often talk about Apple constantly within its environment or ecosystem. If it's at a development level, It is natural to assume that Apple languages like Swift only work to make apps for their locations, but we'll be making a big mistake thinking this. Swift is an open source language, has official support for Linux (and soon for Windows, which is in the testing phase) and incorrectly (due to the developer community above) we can use it on different programs like Raspberry UPi, Arduino and even support servers on it. cloud across all major infrastructure like AWS, Azure, Heroku or Google Cloud.
In the support line for your own programs, Apple has just announced the launch of Swift Crypto, an open source crypto library based on your current development of your locations.
Apple knows that the app is not just the development of any of its platforms. Today, any more sophisticated operating system has what we know as server side either server side: roll back, a cloud server in which our application is connected to store and exchange data, which when our app formatts so we can see that information in a way that is easy to understand.
The server side (or server-side) is the back part of our application (which is why it is known as a backend) that stores and processes information so we can access it from any application or installation.
When we talk about server side development, it's common to talk about technologies such as Node.js, Java and others, based on non-Apple languages (obviously). However What if we could make server side improvements in the same language we use for applications? It is on the same basis that most popular libraries that allow mobile applications are used: Javascript through him forward (our operating system) as well back (server and data).
Apple is betting heavily on this, and it is actually the Swift language team that plans it you have a work group called SSWG (Server-Side Workgroup) building developers from Apple itself and Steam's open source library. Previously there were IBM members, but the blue company decided to opt out of the project to redo their machines as we notify you here.
Swift's Linux editing allows our backend to be compiled at a binary level, and thus confirms and detects any error in the code in a more efficient and efficient way to use resources.
Compared to other major technologies, server side development with Swift may seem unpleasant, but it is slowly recovering and there are already many large companies that are betting on this. You have to keep that in mind Swift server side is integrated at the binary level, something very few existing infrastructure builds on. That gives you great speed, security, prevention of code errors and the use of free resources hardware in the proper way.
Swift Crypto
One of the most important steps for the developer community, Apple has just announced and released Crypto Swift, a very important library that will provide the most development for people working with non-Apple systems, in the Apple Swift language.
Crypto Swift is the API version introduced by Apple for iOS 13 and other major versions of its applications last September: CryptoKit. Swift Library is a native of Cocaoa and Cocaoa (Apple's closed libraries) but now has an open version on Swift running on Linux systems or one of these supported as Swift 5.1.
Crypto Swift uses most of the CryptoKit API, in the same way that it was used when making applications. In this way, any code or implementation we have made, will work without any changes to Linux programs and we can have unique cryptography and encryption code that holds that data, boosting the display capabilities and security.
Apple has confirmed in its performance, the complete compliance of the code between its closed-loop library CriptoKit and the new Swift Crypto. The same code will always return the same result for all systems.
There are some APIs left out, however only those that depend hardware by Apple and its chips Support Security that is, for obvious reasons, which is absent from other programs.
But every part of the encryption, it checks to hurry, signature, authentication, cryptography by standards such as AES-GCM or Cha-Cha Poly and others, is also available for the simplest and most accurate use. Exactly Apple talks about the exchange of keys, subtraction, encryption and encryption, hashing or message authentication, among others.
As part of encryption cannot be done in the traditional way and depends on hardware Apple, Cupertino have made a very interesting game: support all crypto management in Google's open source library, BoringSSL, fork typical of the largest Open OpenSSL G.
The cryptographic engine for Swift Crypto, has been installed on BoringSSL, Google's open source library.
The library is distributed through Swift Package Manager, Swift Package Manager, which makes its life cycle and inclusion in our projects (or any bookstore we want to use) more transparent and integrated by the developer.
Apple has taken special care in testing and verifying that The result that CryptoKit provides an app in the Apple environment is exactly the same as this new Swift Crypto book, based on Google's crypto engine. Not only that, also at the code level, so that the same code in Apple environments (using Swift) returns the same result for Swift Crypto in Linux-based environments or something else supported.
In addition, the Apple team confirms that Swift Crypto will appear on CryptoKit, so that any new changes to the library that are closed in future versions of Apple's systems will work to keep up with its open source version.
Apple's commitment to improving beyond its systems is becoming increasingly important, because they know full well that creating an app is not just a unique development, but a natural process.
Without a doubt, it's a big step it shows how Apple is poised to improve beyond its plans to make it easier for developers working on their platforms.
Now alone we hope that the next step is to introduce Merge, the asynchronous programming library and introduced with the latest versions of the program, as an open source. So that we can use it on Linux and other programs. Apple's best work, of course.
Via | Swift.org blog
