thoughtbot Build Phase #41
swiftのtypeの話
Optional type
haskelのtypeは良い
haskelは実装系ではなくスペック
=== の挙動が変わった
round table discussion
funny
playful
keynote
ibooks
out of shadow steve jobs
swift
ios8
marvelicks
not consumer
my wife
no interest changing language
ns user activity
excited
know about google map
one password
default
lots of complexity
default web browser
safari chrome
mail client
data type
address tel
set default app ios
spotlight
turned off spotlight
remove keyboard
bartender
switch back spotlight
need extensivity
yosemite
app store
app script
web view
tell app app store
itms url scheme
search populated
advance
swift
type
safe runtime
coercing
huge
cast back
bang
as question mark
take string
optional view
huge
flat out compiler error
clang
diagnostic
turn that off
warnings
index
conforming protocol
jerks
huge
retrospect
iteration
objective c
brilliant
mix swift objective c
thousand lines
take a day
one class
easier
c code
legacy
could end up
funny
objective c old
llvm
apple employee
minimal
playing swift
enjoying swift
protest
type system
not as good as haskel type system
not worry about rubtime error
swift dont use bang
let
switch statement
enjoy haskel
function
multiple definition
more powerful
monatic
another one
optional
some none
enum
haskell
objective c wrong
not happy capacity
structs enum
specific use case
close to classes
memory management
class pass by reference
structs
dectate architecture
inheritance
base class
protocol
direction
ns object protocol
arc
look at
bult in
much more haskell
printable
description
very recentry
ruby tos
description
name of method
overrode random method
description
debug description
string interpolation
wired
ns object
dig through
inherit
ns object beast
alloc init
needed to be able to instanciate
equals equals
changed
same instance
== used to
object identity
happens to
maintain
new language
no legacy in langage
not that crap
good change
how old haskell
haskell 95
reference
spec
no compiler
no implementation
spec
jrubu
rubinious
mri ruby
ghc
reference standard
apple iterating
binary compatibility
break
wwdc
new announcement
brand new language
protect private
no stack
function definition
monad
cant wrap
totally
framework
develop language
existing framework
better
look different
baggage
api starting change
new api
functionally different
better
new api in objective c ugly
concrete
first argument
decoration
not you can force
language design
good to go
excited
next four months
next year
