Book Image

Mastering Swift 3 - Linux

By : Jon Hoffman
Book Image

Mastering Swift 3 - Linux

By: Jon Hoffman

Overview of this book

Swift is a modern, fast, and safe programming language created by Apple. Writing Swift is interactive and fun, the syntax is concise yet expressive, and the code runs lightning-fast. Swift’s move to open source has been embraced with open arms and has seen increased adoption in the Linux platform. Our book will introduce you to the Swift language, further delving into all the key concepts you need to create applications for desktop, server, and embedded Linux platforms. We will teach you the best practices to design an application with Swift 3 via design patterns and Protocol-Oriented Programming. Further on, you will learn how to catch and respond to errors within your application. When you have gained a strong knowledge of using Swift in Linux, we’ll show you how to build IoT and robotic projects using Swift on single board computers. By the end of the book, you will have a solid understanding of the Swift Language with Linux and will be able to create your own applications with ease.
Table of Contents (24 chapters)
Mastering Swift 3 - Linux
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
2
Learning About Variables, Constants, Strings, and Operators

Summary


When we read through this chapter and see some of the advantages that POP has over OOP, we might concluded that POP is clearly superior to OOP. However, this assumption would not be entirely correct.

OOP has been around since the 1970s and is a tried and tested programming paradigm. POP is the new kid on the block and was designed to correct some of the issues with OOP. I have personally used the POP paradigm in a couple of projects and I am very excited about its possibilities.

OOP and POP have similar philosophies, such as creating custom types that model real-world objects and polymorphism to use a single interface to interact with multiple types. The difference lies in how these philosophies are implemented.

To me, the code base in a project that uses POP is much safer, easier to read, and easier to maintain as compared to a project that uses OOP. This does not mean that I am going to stop using OOP all together. I can still see plenty of need for class hierarchies and inheritance...