Book Image

Mastering macOS Programming.

By : Gregory Casamento
Book Image

Mastering macOS Programming.

By: Gregory Casamento

Overview of this book

macOS continues to lead the way in desktop operating systems, with its tight integration across the Apple ecosystem of platforms and devices. With this book, you will get an in-depth knowledge of working on macOS, enabling you to unleash the full potential of the latest version using Swift 3 to build applications. This book will help you broaden your horizons by taking your programming skills to next level. The initial chapters will show you all about the environment that surrounds a developer at the start of a project. It introduces you to the new features that Swift 3 and Xcode 8 offers and also covers the common design patterns that you need to know for planning anything more than trivial projects. You will then learn the advanced Swift programming concepts, including memory management, generics, protocol orientated and functional programming and with this knowledge you will be able to tackle the next several chapters that deal with Apple’s own Cocoa frameworks. It also covers AppKit, Foundation, and Core Data in detail which is a part of the Cocoa umbrella framework. The rest of the book will cover the challenges posed by asynchronous programming, error handling, debugging, and many other areas that are an indispensable part of producing software in a professional environment. By the end of this book, you will be well acquainted with Swift, Cocoa, and AppKit, as well as a plethora of other essential tools, and you will be ready to tackle much more complex and advanced software projects.
Table of Contents (28 chapters)
Title Page
About the Author
About the Reviewer
Customer Feedback
LLDB and the Command Line

The price of complexity

As with all the shiny toys that are available to developers, package management begs the question: is it worth it? Adding package management in any form undeniably adds another layer of complexity to a project, and as we all know, complexity is the enemy. So it's worth thinking good and hard about whether a project really needs any of the tools covered in this chapter.

If you work alone, and your project only uses a handful of libraries, ones that don't have a complex dependency graph of their own, then there's a good argument for keeping things manual. Changes in the tools won't affect your project, changes in the libraries can be updated manually, and you know exactly what's going on all the time.

If you work in a team, or a large project, that already uses some form of package management, then you have no choice, you need to follow the pack. If you need a proprietary framework that is only available through a package manager, the same holds true.

And between those...