Khoa onmyway133

iOS 9 App Transport Security

Starting from iOS 9, App Transport Security enforces to use secure HTTPS requests by default.

App Transport Security

App Transport Security (ATS) enforces best practices in the secure connections between an app and its back end. ATS prevents accidental disclosure, provides secure default behavior, and is easy to adopt; it is also on by default in iOS 9 and OS X v10.11. You should adopt ATS as soon as possible, regardless of whether you’re creating a new app or updating an existing one.

If you’re developing a new app, you should use HTTPS exclusively. If you have an existing app, you

###Let's install Vagrant###

Install VirtualBox: https://www.virtualbox.org/
Install Vagrant: http://vagrantup.com/

###Select a Vagrant Box from https://vagrantcloud.com###

#add it to your list of boxes
vagrant box add hashicorp/precise32
#create a new folder for your project &amp; init vagrant

Videos

Introduction to Functional Programming Johannes Weiß - http://kcy.me/1ngiv
ReactiveCocoa at MobiDevDay Andrew Sardone - http://kcy.me/1nhl3
The Future Of ReactiveCocoa Justin Spahr-Summers - http://kcy.me/1nhs7
Enemy of the State Justin Spahr-Summers - http://kcy.me/1njzs
WWDC 2014 Session 229 - Advanced iOS Application Architecture and Patterns Andy Matuschak - http://kcy.me/1pyva
Functioning as a Functionalist Andy Matuschak - http://kcy.me/22o45
Controlling Complexity in Swift Andy Matuschak - http://kcy.me/23sc9
Functional and reactive programming with Swift Ash Furrow -

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

So you're curious in learning this new thing called Reactive Programming, particularly its variant comprising of Rx, Bacon.js, RAC, and others.

Learning it is hard, even harder by the lack of good material. When I started, I tried looking for tutorials. I found only a handful of practical guides, but they just scratched the surface and never tackled the challenge of building the whole architecture around it. Library documentations often don't help when you're trying to understand some function. I mean, honestly, look at this:

Rx.Observable.prototype.flatMapLatest(selector, [thisArg])

Projects each element of an observable sequence into a new sequence of observable sequences by incorporating the element's index and then transforms an observable sequence of observable sequences into an observable sequence producing values only from the most recent observable sequence.

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:

	import Foundation

	struct Box<T> {}

	protocol Functor {
	typealias A
	typealias B
	typealias Boxed = Box<B>

	func fmap<B>(f: A -> B) -> Boxed

	// Monad
	operator infix >>= {
	precedence 10
	associativity left
	}

	struct _MReturn {
	}
	@transparent func _mreturn<Args>(a: Args) -> (_MReturn, Args) {
	return (_MReturn(), a)

	#import <Foundation/Foundation.h>

	@interface JNWThrottledBlock : NSObject

	// Runs the block after the buffer time _only_ if another call with the same identifier is not received
	// within the buffer time. If a new call is received within that time period the buffer will be reset.
	// The block will be run on the main queue.
	//
	// Identifier and block must not be nil.
	+ (void)runBlock:(void (^)())block withIdentifier:(NSString *)identifier throttle:(CFTimeInterval)bufferTime;

	#import <Foundation/Foundation.h>

	int main (int argc, const char * argv[])
	{
	NSDateFormatter *dateFormatter = [[NSDateFormatter alloc] init];
	dateFormatter.dateFormat = @"YYYY";
	NSDate *date = [NSDate dateWithTimeIntervalSince1970:1419872056];

	NSLog (@"%@", [dateFormatter stringFromDate:date]); // 2015

	// Taken from the commercial iOS PDF framework http://pspdfkit.com.
	// Copyright (c) 2014 Peter Steinberger, PSPDFKit GmbH. All rights reserved.
	// Licensed under MIT (http://opensource.org/licenses/MIT)
	//
	// You should only use this in debug builds. It doesn't use private API, but I wouldn't ship it.

	#import <objc/runtime.h>
	#import <objc/message.h>

	// Compile-time selector checks.