Michael Tsai on Twitter: "@jckarter Will try to make a good example and file a bug. I suspect the runtime APIs are there, just that patching is easier from Obj-C."

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

Joe Groff ‏@jckarter May 11

Joe Groff Retweeted Zed

If you answered "yes" to @zedshaw's poll, what did you need to use ObjC for in your Swift app?https://twitter.com/zedshaw/status/730431644616646659 …

Joe Groff added,

Zed @zedshaw

Rephrase: If I want to use Swift to write a real serious iOS app I would still need to WRITE obj-c code.
9 retweets 15 likes
Michael Tsai ‏@mjtsai May 11

@jckarter Not done with app yet, but: handling exceptions raised by Cooca, avoiding bridging overhead for large plists, Obj-C runtime stuff.
1 like
Joe Groff ‏@jckarter May 11

@mjtsai Where are you seeing bridging overhead? Which ObjC runtime APIs do you need that aren't available in Swift?

Michael TsaiVerified account