Alexis Gallagher algal

Using Swift libraries in Python

So... this is obviously totally, 100%, like for. real. not. supported. by. Apple. …yet?

But still... I thought it was pretty badass. And, seeing how there's already a Swift buildpack for Heroku you could move some slow code into Swift can call it as a library function. But, you know, not in production or anything. That would be silly, right?

Now, having said that, the actual Python/Swift interop may have bugs. I'll leave that as an exercise to the reader.

How to get Python code calling Swift functions:

Himawari-8 animation tutorial

Here’s how to make animations like this one. It requires intermediate Unix command-line knowledge, to install some tools and to debug if they don’t work. You’ll need these utilities:

curl (or you can translate to wget)
convert and montage, part of ImageMagick
ffmpeg, plus whatever codecs
parallel, for iteration that’s nicer than shell for loops or xargs
run everything in zsh for leading 0s in numerical ranges to work

Profiling an application in Mac OS X

Finding which process to profile

If your system is running slowly, perhaps a process is using too much CPU time and won't let other processes run smoothly. To find out which processes are taking up a lot of CPU time, you can use Apple's Activity Monitor.

The CPU pane shows how processes are affecting CPU (processor) activity:

Thoughts on Swift 2 Errors

When Swift was first announced, I was gratified to see that one of the (few) philosophies that it shared with Objective-C was that exceptions should not be used for control flow, only for highlighting fatal programming errors at development time.

So it came as a surprise to me when Swift 2 brought (What appeared to be) traditional exception handling to the language.

Similarly surprised were the functional Swift programmers, who had put their faith in the Haskell-style approach to error handling, where every function returns an enum (or monad, if you like) containing either a valid result or an error. This seemed like a natural fit for Swift, so why did Apple instead opt for a solution originally designed for clumsy imperative languages?

I'm going to cover three things in this post:

	#!/bin/bash

	echo "=== List of available, shared Schemes ==="
	set -x
	# if you use a Workspace (.xcworkspace) file
	xcodebuild -workspace $BITRISE_PROJECT_PATH -list
	# or if you use a Project file (.xcodeproj) instead
	xcodebuild -project $BITRISE_PROJECT_PATH -list
	set +x
	echo "============================================="

	protocol ValidatorType {
	typealias ValidatedType
	func isValid(object: ValidatedType) -> Bool
	}

	// You might want to make it a reference type, depending on your case.
	struct AnyValidator<T>: ValidatorType {
	private let validatorBlock: (T) -> Bool

	init<V: ValidatorType where V.ValidatedType == T>(validator: V) {

	// See also https://github.com/CocoaLumberjack/CocoaLumberjack/blob/master/Classes/DDASLLogCapture.m


	#import "GFASLProxy.h"
	#include <asl.h>
	#include <notify.h>
	#include <notify_keys.h>
	#include <sys/time.h>

	@implementation GFASLProxy

	//
	// RN3DTouchGestureRecognizer.swift
	//
	// Created by Ryan Nystrom on 10/10/15.
	// Copyright © 2015 Ryan Nystrom. All rights reserved.
	//

	import UIKit.UIGestureRecognizerSubclass

	class RN3DTouchGestureRecognizer: UIGestureRecognizer {

	'''A simple utility for running UNIX shell commands'''

	KEEP_STDOUT = 0x1
	KEEP_STDERR = 0x1 << 1
	ECHO_STDOUT = 0x1 << 2
	ECHO_STDERR = 0x1 << 3


	def shell(command, input_=None, output_=(KEEP_STDOUT \| KEEP_STDERR \| ECHO_STDOUT \| ECHO_STDERR), wait=True):
	'''

	(require '[clojure.core.async :as async]
	'[clj-http.client :as client]
	'[clojure.data.json :as json])

	(def concurrency 5)

	(let [in (async/chan)
	out (async/chan)
	request-handler (fn [url out*]
	(async/go