rockshassa
Joined 12 years ago
Joined 12 years ago
If a variable is read-only, you're forced to think about that by deciding between let/var. contrast this with objc, where all vars are writable unless you do the extra work of adding the const keyword. objc makes us do more work to get the faster (and safer) behavior.
Similar with Optionals, you're now forced to decide right away if a parameter can ever be nil, whereas with objc you didn't need to declare nullability. Again, it makes the safest and fastest choice easier to make, and allowing nullability is actually more work.
Generally Swift forces you to pass as much information to the compiler as possible at compile time, and it does it with a delightfully readable syntax. This theme repeats itself throughout the language. more information at compile time is always going to result in safer and more predictable behavior.
full disclosure: i'm an iOS dev working in objc and swift. i love both languages, and i think swift is the obvious path forward.
Taxi drivers also never know the destination, I got pretty good at giving my directions speech (to a well known neighborhood)
And taxis cost more!
As far as I'm concerned, the old way of hailing can rot, the old taxis can rot. they can't hold a candle to uber, and they'll never be able to become competitive on price or quality given the cost of a medallion.
so either the vendor screwed up, or something is insecure..