Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Swift 5.3

You're reading from   Mastering Swift 5.3 Upgrade your knowledge and become an expert in the latest version of the Swift programming language

Arrow left icon
Product type Paperback
Published in Nov 2020
Publisher Packt
ISBN-13 9781800562158
Length 418 pages
Edition 6th Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Jon Hoffman Jon Hoffman
Author Profile Icon Jon Hoffman
Jon Hoffman
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Preface 1. Taking the First Steps with Swift 2. Swift Documentation and Installing Swift FREE CHAPTER 3. Learning about Variables, Constants, Strings, and Operators 4. Optional Types 5. Using Swift Collections 6. Control Flow 7. Functions 8. Classes, Structures, and Protocols 9. Protocols and Protocol Extensions 10. Protocol-Oriented Design 11. Generics 12. Error Handling and Availability 13. Custom Subscripting 14. Working with Closures 15. Advanced and Custom Operators 16. Concurrency and Parallelism in Swift 17. Custom Value Types 18. Memory Management 19. Swift Formatting and Style Guide 20. Adopting Design Patterns in Swift 21. Other Books You May Enjoy
22. Index

Summary

As we have read through this chapter and looked at some of the advantages that protocol-oriented design has over object-oriented design, we may think that protocol-oriented design is clearly superior to object-oriented design. However, this assumption would not be entirely correct.

Object-oriented design has been around since the 1970s and is a tried and true programming paradigm. Protocol-oriented design is the new kid on the block and was designed to correct some of the issues with object-oriented design.

Object-oriented and protocol-oriented design 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 is how these philosophies are implemented.

To me, the code base in a project that uses protocol-oriented design is much safer, easier to read, and easier to maintain as compared to a project that uses object-oriented design. This does not...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime