maxsz

class DelayedBlockOperation: NSOperation {
	private var delay: NSTimeInterval = 0
	private var block: (() -> Void)? = nil
	private var queue: dispatch_queue_t = dispatch_get_main_queue()
	
	override var asynchronous: Bool { return true }
	override var executing : Bool {
		get { return _executing }
		set { 
			willChangeValueForKey("isExecuting")

fchaillou

import Alamofire
import Foundation
import enum Result.Result

extension Alamofire.Result {
    func toStandard() -> Result<Value, Error> {
        switch(self) {
            case Alamofire.Result.Success(let value) : return Result.Success(value)
            case Alamofire.Result.Failure(let error) : return Result.Failure(error)
        }

Mistobaan

These instructions will explain how to install tensorflow on mac with cuda enabled GPU suport. I assume you know what tensorflow is and why you would want to have a deep learning framework running on your computer.

Prerequisites

Make sure to update your homebrew formulas

brew update

geoff-nixon

#!/usr/bin/sudo sh

## ruby_revealer.sh -- decrypt obfuscated GHE .rb files. 2.0.0 to 2.3.1+.

## From `strings ruby_concealer.so`:
##
## > This obfuscation is intended to discourage GitHub Enterprise customers
## > from making modifications to the VM.
##
## Well, good, as long as its not intended to discourage *me* from doing this!

praeclarum

//
//  ArrayDiff.swift
//
//  Created by Frank A. Krueger on 6/30/15.
//  Copyright © 2015 Krueger Systems, Inc. All rights reserved.
//  License: MIT http://opensource.org/licenses/MIT
//

import Foundation

nicklockwood

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:

rbobbins

PS: If you liked this talk or like this concept, let's chat about iOS development at Stitch Fix! #shamelessplug

Protocol-Oriented Programming in Swift

Speaker: David Abrahams. (Tech lead for Swift standard library)

• "Crusty" is an old-school programmer who doesn't trust IDE's, debuggers, programming fads. He's cynical, grumpy.

• OOP has been around since the 1970's. It's not actually new.

• Classes are Awesome

  • Encapsulation
  • Access control

carlfish

Response to a question on Twitter:

Either and Promises/Futures are useful and I’ll use them next time they’re appropriate. But outside Haskell does their monad-ness matter?

(All code below is written in some made-up Java-like syntax, and inevitably contains bugs/typos. I'm also saying "point/flatMap" instead of "return/bind" because that's my audience. Any correspondance with anything that either be programatically or mathematically useful is coincidental)

What is a monad? A refresher.

A monad is something that implements "point" and "flatMap" correctly.

phatblat

#!/bin/bash -e

#
# package-ipa.sh
#
# Bundles an iOS app correctly, using the same directory structure that Xcode does when using the export functionality.
#

xcarchive="$1"
output_ipa="$2"

seapy

RailsConf 2015 Schedule

RailsConf 2015 Room 202 Day 1

• Opening Keynote - DHH
• Prying Open The Black Box - Godfrey Chan
  • slide
• Riding Rails for 10 Years - John Duff
• DevOps for The Lazy - Aja Hammerly
• Docker isn’t just for deployment - Ben Dixon