blockerList.json

[
    {
        "action": {
            "type": "block"
        },
        "trigger": {
            "url-filter": ".*",
            "resource-type": ["script"],
            "load-type": ["third-party"],
            "if-domain": ["imore.com"]

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

Cocoa Touch Best Practices

Speaker: Luke Hiesterman, UIKit Engineer

Agenda

• App lifecycle
• Views and view controllers
• Auto layout
• Table and collection views

Goals

CodaFi

#Every Single Option Under The Sun

• optimization level options
• automatic crashing options
• debug info options
• swift internal options
• swift debug/development internal options
• linker-specific options
• mode options

yoavniran

The Ultimate Unit Testing Cheat-sheet

---

• Sinon Chai
• Chai
• Sinon

neonichu

A common question regarding CocoaPods and Swift is which OS versions are supported.

• Swift is supported on OS X 10.9 / iOS 7 and newer, as stated by Apple numerous times.
• There is no support for building static archives with Swift (see http://openradar.appspot.com/radar?id=5536341827780608).
• Dynamic frameworks are supported on all versions of OS X.
• Dynamic frameworks are unsupported on iOS versions prior to 8:

ld: warning: embedded dylibs/frameworks only run on iOS 8 or later.

From this we can conclude that it is not possible to support Swift on any other platforms than OS X 10.9/10.10 and iOS 8.

bwhiteley

// Create CustomView.xib, set File's Owner to CustomView. 
// Link the top level view in the XIB to the contentView outlet.

class CustomView : UIView {
    @IBOutlet private var contentView:UIView?
    // other outlets
    
    override init(frame: CGRect) { // for using CustomView in code
        super.init(frame: frame)
        self.commonInit()

brock

#!/bin/bash
# node-reinstall
# credit: http://stackoverflow.com/a/11178106/2083544

## program version
VERSION="0.0.13"

## path prefix
PREFIX="${PREFIX:-/usr/local}"

nubbel

protocol ArrayRepresentable {
    typealias ArrayType
    
    func toArray() -> ArrayType[]
}

extension Range : ArrayRepresentable {
    func toArray() -> T[] {
        return T[](self)
    }

raven

<?xml version="1.0" encoding="UTF-8"?>
<Bucket
   type = "2"
   version = "2.0">
   <Breakpoints>
      <BreakpointProxy
         BreakpointExtensionID = "Xcode.Breakpoint.SymbolicBreakpoint">
         <BreakpointContent
            shouldBeEnabled = "Yes"
            ignoreCount = "0"