Joe Groff on Twitter: "@mjtsai Many users would prematurely reach for 'final' to get a similar effect and be stuck with it w/o the new default behavior."

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

Colin Cornaby ‏@colincornaby Jul 18

@jckarter Sure, I just prefer that restriction to be explicit over implicit. I think a lot of classes will be unnecessarily final.
1 like
Colin Cornaby ‏@colincornaby Jul 18

@jckarter I do a heck of a lot of subclassing things that aren't even meant to be subclassed for mocking tests around my own code.
1 like
Joe Groff ‏@jckarter Jul 18

@colincornaby OTOH, components that interface with protocols have *more* flexibility for mocking and hotfixing than subclassing.
1 retweet 6 likes
Dr. Sneed ‏@bsneed Jul 18

@jckarter @colincornaby , and this proposal isn't really forcing them to do that, it feels more like just creating pain on end-users.
1 like
Joe Groff ‏@jckarter Jul 18

@bsneed @colincornaby It doesn't affect end users at all. The frameworks aren't going to spontaneously rewrite themselves in Swift.
2 likes
Michael Tsai ‏@mjtsai Jul 18

@jckarter @bsneed @colincornaby If it truly “doesn’t affect end users at all,” what could be the point of the change?
2 likes
Joe Groff ‏@jckarter Jul 18

Joe Groff Retweeted Joe Groff

@mjtsai @bsneed @colincornabyhttps://twitter.com/jckarter/status/755149856994316288 …

Joe Groff added,

Joe Groff @jckarter

@bsneed @colincornaby The default is all about making sure API authors don't make irrevocable mistakes without thinking about them.
Michael Tsai ‏@mjtsai Jul 18

@jckarter Right, but presumably you expect that to ultimately benefit end users (indirectly).
Joe Groff ‏@jckarter Jul 18

@mjtsai Users who are third-party framework devs I expect will benefit the most.
1 retweet 5 likes
Michael Tsai ‏@mjtsai Jul 18

@jckarter You’re saying no change for Apple Swift frameworks because you consider the API, but it’s about protecting others who don’t?

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.

Saved searches

Joe Groff

@jckarter

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