Searched for "February 1, 2019" in this user's bookmarks. Found 34 results

« earlier   

Twitter
Retain, release, and isUnique are all atomic, and ARC ensures that the read will ensure an independent retain for each thread. There should be no "between"

— Joe Groff (@jckarter) February 1, 2019
FavoriteTweet  jckarter 
18 days ago by mjtsai
Twitter
By Apple types, I actually meant the CoW types like Array. My concern is that if a struct is copied from a second thread, between the isUnique... call and the property set, you could have the copy actually change value, breaking value semantics.

— Drew McCormack (@drewmccormack) February 1, 2019
FavoriteTweet  drewmccormack 
18 days ago by mjtsai
Twitter
As mentioned I struggled a while with that as we'll ;-) Let me try: If isUnique returns yes, there can't be another "copy" of the struct (if there would be, the RC>1). If it returns no, the CoW code doesn't touch the struct (as any other concurrent modifier, because the RC>1!).

— Helge Heß (@helje5) February 1, 2019
FavoriteTweet  helje5 
18 days ago by mjtsai
Twitter
In other words, because of the `inout` exclusivity guarantee, `isUnique` returning true also implies that your thread is the only thread that can see the one outstanding reference

— Joe Groff (@jckarter) February 1, 2019
FavoriteTweet  jckarter 
18 days ago by mjtsai
Twitter
`isUnique` takes its argument `inout` intentionally to ensure this isn't a problem. Swift's `inout` requires exclusive access to the memory passed in, so by the time you have a local copy, it must be in a separate memory location with its own strong reference

— Joe Groff (@jckarter) February 1, 2019
FavoriteTweet  jckarter 
18 days ago by mjtsai
Twitter
Big uncovered scoop from @gruber:

“Apple effectively sells [Apple TV] at cost... I’ve heard the same thing about HomePod. I actually have reason to believe, Apple actually sells it at a loss.”https://t.co/gH4nOLBUlW

— Ryan Jones (@rjonesy) February 1, 2019
FavoriteTweet  rjonesy 
18 days ago by mjtsai
Twitter
I guess they key thing to understand is that this is not thread safe and needs synchronization:
```
var x = [ 1, 2, 3 ]
q.async( x.append(4) )
q.async( x.append(5) )
```
(like you said, thread safe to read©, but not writes)

— Helge Heß (@helje5) February 1, 2019
FavoriteTweet  helje5 
18 days ago by mjtsai
Twitter
If you implement your cow buffer the same way the standard library does, using `isUniquelyReferenced` to check whether copying is necessary before any modification, then you should get the same guarantee. The `isUniquelyReferenced` is itself threadsafe

— Joe Groff (@jckarter) February 1, 2019
FavoriteTweet  jckarter 
18 days ago by mjtsai
Twitter
The difference from an ObjC object would be that two threads can both copy from a common value and modify their local copy with a guarantee that the writes don't race, so this is valid:

let x = [1, 2, 3]

q.async { var y = x; y[0] = 4 }
q.async { var y = x; y[0] = 4 }

— Joe Groff (@jckarter) February 1, 2019
FavoriteTweet  jckarter 
18 days ago by mjtsai
Twitter
Searched various support pages for a solution to this, Apple Support, Stack Exchange. Tried blowing away the app store cache, resetting its catalog, rebooting, etc...nothing works.

— Bob Burrough (@bob_burrough) February 1, 2019
FavoriteTweet  bob_burrough 
18 days ago by mjtsai
Twitter
App Store redownloads 4.5GB Xcode payload even though it just finished doing exactly that.

— Bob Burrough (@bob_burrough) February 1, 2019
FavoriteTweet  bob_burrough 
18 days ago by mjtsai
Twitter
App Store thinks it needs to update Xcode when Xcode is already at the latest version.

— Bob Burrough (@bob_burrough) February 1, 2019
FavoriteTweet  bob_burrough 
18 days ago by mjtsai
Twitter
Apple TV and HomePod, I’d bet on. And based on quantities I’m probably wrong about AirPods, but I would bet they’re lower margin than usual.

— John Gruber (@gruber) February 1, 2019
FavoriteTweet  gruber 
18 days ago by mjtsai
Twitter
I think it’s possible, yes, and it’s what I heard from a trusted birdie.

— John Gruber (@gruber) February 1, 2019
FavoriteTweet  gruber 
18 days ago by mjtsai
Twitter
@gruber Before I quote it, you can to confirm that you think Apple TV, HomePod, and AirPods are sold approximately at cost? HomePod maybe even below cost.

— Ryan Jones (@rjonesy) February 1, 2019
FavoriteTweet  rjonesy 
18 days ago by mjtsai
Twitter
only when you own the hardware, software, and services can you create experiences for your customers that are *this* magical pic.twitter.com/g9yDi3Q9bH

— zach kahn (@zkahn) February 1, 2019
FavoriteTweet  zkahn 
18 days ago by mjtsai
Twitter
Has any of my fellow Mac devs figured out how to trick an ILMBRemoteMediaBrowserPanel or one of the releted classes (NSRemoteWindowController?), into notifying the host app when an image is double-clicked (instead of only magnifying it)?

— Ilja A. Iwas (@iljawascoding) February 1, 2019
FavoriteTweet  iljawascoding 
18 days ago by mjtsai
Twitter
Overall, I think Apple handled Facebook and Google well, but the question remains as to what Apple will do when Facebook does it again.

— Josh Centers (@jcenters) February 1, 2019
FavoriteTweet  jcenters 
18 days ago by mjtsai
Twitter
Notice to hiring managers: when posting job titles, there’s a big difference between “Mobile Engineer” and “Engineer who can support multiple locations”.

— Eric Blair (@jablair) February 1, 2019
FavoriteTweet  jablair 
18 days ago by mjtsai
Twitter
Perfect software is hard. Imperfect software is useful. The correct trade-off is often to write and deliver imperfect software to more people faster. Capitalism chooses those trade-offs using dollar signs, but that doesn't make those decisions necessarily wrong.

— Greg Parker (@gparker) February 1, 2019
FavoriteTweet  gparker 
18 days ago by mjtsai

« earlier   

Copy this bookmark:



description:


tags:



Copy this bookmark:



description:


tags: