Michael Tsai on Twitter: "@roopeshchander @jckarter @curtclifton the realities of developing apps are not appreciated/understood. Old system was accidentally good."

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

Michael Tsai ‏@mjtsai 21 Dec 2015

@curtclifton @jckarter @owensd I don’t see how it advances the platform to have everyone relying on middleware instead of the frameworks.
1 like
Joe Groff ‏@jckarter 21 Dec 2015

@mjtsai @curtclifton @owensd Well defined modular components make everyone's life easier. Today's frameworks aren't there, sure.
1 like
JΛЯΣD ‏@jaredsinclair 21 Dec 2015

@jckarter @mjtsai @curtclifton @owensd Consider UITextView in iOS 7. Unusably broken for *a year* w/out subclass workarounds.
1 retweet 4 likes
Joe Groff ‏@jckarter 21 Dec 2015

@jaredsinclair @mjtsai @curtclifton @owensd Like I said, Swift's defaults won't change how ObjC works or even the policy of new frameworks.
2 likes
Roopesh Chander ‏@roopeshchander 21 Dec 2015

@jckarter @mjtsai @curtclifton What about when Apple writes a framework in Swift? Will it remain swizzlable, probably for use from Obj-C?
Joe Groff ‏@jckarter 21 Dec 2015

@roopeshchander @mjtsai @curtclifton That's a call API review can make when it happens.
1 like
Joe Groff ‏@jckarter 21 Dec 2015

@roopeshchander @mjtsai @curtclifton The goal of the resilience defaults is to avoid developers making irrevocable promises they can't keep.
Joe Groff ‏@jckarter 21 Dec 2015

@roopeshchander @mjtsai @curtclifton Being too final or too static is a mistake you can safely fix, but not the other way.
3 retweets 2 likes
Roopesh Chander ‏@roopeshchander 21 Dec 2015

@jckarter @mjtsai @curtclifton I see your point. A default final is a different issue from future Apple frameworks being un-overrideable.
2 likes
Roopesh Chander ‏@roopeshchander 21 Dec 2015

@jckarter @mjtsai @curtclifton Coz, it’s not like Apple can’t add final to all public API even if it’s not a language default. :)

1. View other replies

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

Michael TsaiVerified account

@mjtsai

Loading seems to be taking a while.

false

Saved searches

Michael TsaiVerified account

@mjtsai

Go to a person's profile

Saved searches

Retweet this to your followers?

Saved searches

Are you sure you want to delete this Tweet?

Promote this Tweet

Block

Add a location to your Tweets

Profile summary

Your lists

Create a new list

Copy link to Tweet

Embed this Tweet

Embed this Video

Preview

Log in to Twitter

Sign up for Twitter

Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

Two-way (sending and receiving) short codes:

Confirmation

Buy Now

Hmm... Something went wrong. Please try again.

Welcome home!

Tweets not working for you?

Say a lot with a little

Spread the word

Join the conversation

Learn the latest

Get more of what you love

Find what's happening

Never miss a Moment

Loading seems to be taking a while.

Promoted Tweet

false