Working with extended attributes in Swift. They’re straightforward using shell commands, but that is not the best way ahead.
How much more difficult is it to write your own code to handle user preferences, rather than letting UserDefaults handle them?
Which String.contains() variant should you use, and how can you give access to regex searching? More answers coded in Swift 3.1.
A crashing app points out the problems of using functions that return values of ‘Any’ type. Here’s one solution.
Creating a drop-down sheet to let the user change preference settings is a bit intricate, but straightforward.
In some respects at least as good as any other Swift playground product, and its AppleScript support has improved considerably. But in other respects still falls short. In a class of one.
Want to write to Sierra’s log from a language or app which doesn’t give easy access? Use this free tool which now writes anything you want.
A classic scripting task: iterate through a folder and its entire contents, testing to see if each file is readable or writable. It’s straightforward in Swift too.
There are lots of different ways to modify a string, but some would turn out to be very inefficient. A gentle wander through CharacterView and a mapping closure.