Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Mastering macOS Programming
  • Toc
  • feedback
Mastering macOS Programming

Mastering macOS Programming

By : Gregory Casamento, Stuart Grimshaw
3.2 (6)
close
Mastering macOS Programming

Mastering macOS Programming

3.2 (6)
By: Gregory Casamento, Stuart Grimshaw

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 (21 chapters)
close
18
LLDB and the Command Line

Pros and cons

Using third-party code is not always the best way to go (that is, assuming that you have found third-party code that meets your requirements), but rejecting it outright is similarly unwise.

The decision ultimately rests with whatever combination of requirements, timelines, developers, managers, and clients is involved in a project (as well as all of those who have been involved on the project in the past, if that's the case).

But let's take a look at both sides of the scales.

The case for third - party code

There are very good reasons to use third-party code. Some very good developers do it all the time, and most do it often. So here are some reasons to resist the temptation to announce proudly I don't use third-party code on principle...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete