kentbrew

The Problem

Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)

The temptingly easy but ultimately wrong solution:

Alter the port the script talks to from 8000 to 80:

}).listen(80);

soffes

extension Array {
    func each(block: ((Element) -> Void)) {
        for i in 0..<count {
            block(self[i])
        }
    }
    
    func eachWithIndex(block: ((Element, Int) -> Void)) {
        for i in 0..<count {
            block(self[i], i)

mackuba

Here's my own list of the interesting stuff announced during this year's WWDC, collected from the keynotes, various Apple docs, blog posts and tweets.

If you're planning to watch the videos, I really recommend this Mac app that helps you download and watch them: https://github.com/insidegui/WWDC.

OS X El Capitan

http://www.apple.com/osx/elcapitan-preview/

• split view - two apps side by side on full screen

erica

Introducing the !! "Unwrap or Die" operator to the Swift Standard Library

• Proposal: SE-TBD
• Author(s): Ben Cohen, Erica Sadun, Paul Cantrell and several other folk
• Status: tbd
• Review manager: tbd

Introduction

This proposal introduces an annotated forced unwrapping operator to the Swift standard library, completing the ?, ??, and ! family with !!. The "unwrap or die" operator provides text feedback on failed unwraps, to support defensive programming. This operator is commonly implemented in the larger Swift Community and should be considered for official adoption.