Kostiantyn Koval kostiakoval

Purpose of this list is to gather a source of information on how many people are working on iOS application.
I often wonder how many people are behind Facebook's app or Twitter's. If you're as curious as me, please share and please add apps 😉.

* - it's a rumoured value only. Needs confirmation from someone inside the company.

Fishbrain - 3
Artsy - 5
Truecaller - 5
Lifesum - 4 or 5
Spotify - 50*

с утра посвизлил - весь день свободен
украл, посвиззлил - в тюрьму
волков бояться - в лесу не свиззлить
не все золото что свиззлит
свиззлинг - всему голова
и рыбку съесть, и посвиззлить
в большой семье свиззлом не щелкают

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:

Swift Don'ts

Don't add code cruft. Avoid parentheses around conditions in if-statements or with the return keyword. Don't add semicolons except where syntactically demanded in statements or to separate statements on the same line.
Don't use ALL_CAPS; use camelCase
Don't fight type inference. Use enumeration prefixes, self-references, and class names (with constructors) only when necessary or to clarify coding intent.
Don't use var when let is appropriate, especially for properties. The compiler better optimizes let statements for items whose values will not change during their lifetime. For example, Apple writes, "It is good practice to create immutable collections in all cases where the collection does not need to change. Doing so enables the Swift compiler to optimize the performance of the collections you create."
Don't use classes when structs will do. Use class

	#!/bin/bash
	#
	# Faster toolchain build: skips as much as possible.
	#
	# To use this toolchain from the command line:"
	# export TOOLCHAINS=$(whoami)
	#
	# we build to the same prefix every time (instead of building
	# to a versioned prefix) because every time the prefix changes
	# everything rebuilds.

	import Foundation

	public func getASTString() -> String {

	// get the file path for the file "test.json" in the playground bundle
	// let filePath = NSBundle.mainBundle().pathForResource("FirstTtest", ofType: "ast")

	// get the contentData
	let contentData = NSFileManager.defaultManager().contentsAtPath("a.txt")

	// Make initialization + configuration of mutable classes (such as views) easier.
	@warn_unused_result
	public func Init<Type>(value : Type, @noescape block: (object: Type) throws -> Void) rethrows -> Type
	{
	try block(object: value)
	return value
	}

	func example()
	{

	post_install do \|installer\|
	app_plist = "Emergence/Info.plist"
	plist_buddy = "/usr/libexec/PlistBuddy"
	version = `#{plist_buddy} -c "Print CFBundleShortVersionString" #{app_plist}`.split
	puts "Updating CocoaPods' version numbers to #{version}"

	installer.pods_project.targets.each do \|target\|
	`#{plist_buddy} -c "Set CFBundleShortVersionString #{version}" "Pods/Target Support Files/#{target}/Info.plist"`
	end
	end

	import Cocoa

	struct Person {
	var name: String = "John"
	var age: Int = 50
	var dutch: Bool = false
	var address: Address? = Address(street: "Market St.")
	}

	struct Address {

	protocol OptionalType {
	typealias T
	var optional: T? { get }
	}

	extension Optional : OptionalType {
	var optional: T? { return self }
	}

	extension SequenceType where Generator.Element: OptionalType {