My forth book titled Protocol Oriented Programming has been
released. You can buy a copy of the book
on Amazon or from Packt’s site.
This book is about protocol-oriented programming. When Apple
announced Swift 2 at the World Wide Developers Conference (WWDC) in 2015, they
also declared that Swift was the world's first protocol-oriented programming
language. By its name, we may assume that protocol-oriented programming is all
about the protocol; however, that would be a wrong assumption. Protocol-oriented
programming is about so much more than just the protocol; it is actually a new
way of not only writing applications, but also thinking about the design of our
application.
One of the biggest misconceptions about protocol-oriented
programming is that it is just another name for object-oriented programming. Chapter
1, Object-Oriented
and Protocol-Oriented Programming of this book immediately takes
on this myth by comparing protocol-oriented programming to object-oriented
programming to see what is similar and what the differences are. We will also
discuss the advantages and disadvantages of both the programming paradigms.
From Chapter 2, Our Type Choices to Chapter
5, Let's Extend
Some Types, we will take an in-depth look at each of the
components that make up the protocol-oriented programming paradigm. These
chapters are designed to give the reader a solid understanding of the different
components of protocol-oriented programming, so users will understand how they
can use tthem in their applications.
The last two chapters are written to help the reader
understand how they can design their application in a protocol-oriented
programming way. Chapter 6, Adopting Design Patterns in Swift
looks at how we would implement several design patterns in a protocol-oriented
way and Chapter 7, Case Studies looks at three
real-world case studies to reinforce everything previously discussed in the
book.
What this book covers by chapter:
Chapter 2, Our Type Choices, will look at
the different types that Swift offers (Structs, Classes, Enums, and Tuples). We
will show several examples on when to use the various types and when not to.
Chapter 3, Catching Our Errors, will look
at the various ways we can catch and report errors. This chapter will not only
cover the new Swift 2 do-try-catch blocks, but also the older error handling patterns.
Chapter 4, All about the Protocol, will be
all about the protocol. We will show the advantages of using protocols and why,
in our design, we should start with the protocol.
Chapter 5, Let's Extend Some Types, will
cover extensions in great detail. We will look at how to extend standard Swift
types, such as structures and classes. We will also look at protocol extensions
and discuss why they are so important in protocol-oriented programming.
Chapter 6, Adopting Design Patterns in Swift,
will be implementing several design patterns using protocol-oriented
programming. For each of the design patterns, we will look at the problem they
are designed to solve and how to implement the pattern.
Chapter 7, Case Studies, will explore
three case studies. This chapter is designed to pull everything from the first
six chapters together to show the reader how to use protocol-oriented
programming with design patterns in real-world situations.
You can read about Protocol Oriented Programming in my last blog post.
You can read about Protocol Oriented Programming in my last blog post.
If you are interested in using the new protocol oriented
programming paradigm in your next project or if you are curious about what it
is, I hope you will consider picking up my new book. You can pick up your copy from Amazon or from Packt’s site.
No comments:
Post a Comment