Martin Pilkington on Twitter: "@mjtsai @amyruthworrall True, but technically you should only be doing that for either debugging or as an absolute last resort"

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

Martin Pilkington ‏@pilky 11 Jun 2014

Regarding my tweets yesterday about Swift not being dynamic, as long as Obj-C sticks around I don't see that being an issue
1 retweet 3 likes
Amy Worrall ‏@amyruthworrall 11 Jun 2014

@pilky I do. The problem is when I want to interoperate with others’ code. If they thought “this doesn’t need to be dynamic”, it’s harder.
1 like
Martin Pilkington ‏@pilky 11 Jun 2014

@amyruthworrall But I'd wager that 90+% of the Obj-C code you've ever written isn't inherently dynamic code
Amy Worrall ‏@amyruthworrall 11 Jun 2014

@pilky Most of my apps have a classFromString, or a class_addMethod, or a resolveInstanceMethod. It’s a style I like.
Martin Pilkington ‏@pilky 11 Jun 2014

@amyruthworrall And is there something that would prevent those particular parts of your app being written in Obj-C?
Michael Tsai ‏@mjtsai 11 Jun 2014

@pilky @amyruthworrall If you're trying to do dynamic stuff with other people's compiled code, it's easier if they didn't use Swift.

‏@pilky

@mjtsai @amyruthworrall True, but technically you should only be doing that for either debugging or as an absolute last resort

6:49 AM - 11 Jun 2014

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.