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 3

You're reading from   Mastering Swift 3 Build incredible apps for iOS and OS X

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781786466129
Length 392 pages
Edition 1st Edition
Languages
Tools
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 (18) Chapters Close

Preface 1. Taking the First Steps with Swift FREE CHAPTER 2. Learning About Variables, Constants, Strings, and Operators 3. Using Swift Collections and the Tuple Type 4. Control Flow and Functions 5. Classes and Structures 6. Using Protocols and Protocol Extensions 7. Protocol-Oriented Design 8. Writing Safer Code with Availability and Error Handling 9. Custom Subscripting 10. Using Optional Types 11. Working with Generics 12. Working with Closures 13. Using Mix and Match 14. Concurrency and Parallelism in Swift 15. Swift Formatting and Style Guide 16. Swifts Core Libraries 17. Adopting Design Patterns in Swift

Summary

As we were reading through this chapter and seeing some of the advantages that POP has over OOP, we may think 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 true 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 is 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 altogether. I can still see plenty of need for class hierarchy and inheritance...

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 $19.99/month. Cancel anytime