asarazan

7 ms·

1.
by asarazan 5y ago
Does this mean we have to get rid of Speechless at Google IO?
2.
by asarazan 7y ago
I'm really hoping somebody at Oculus/HTC/Microsoft sees this and wants to develop it, because I agree the hardware industry needs to step up its game to make this a reality.
3.
by asarazan 9y ago
Android Lead from Capital One SF here. I did and it was one of the best hires I ever made. He's the most enthusiastic and motivated person on my entire team, and is also amazing at UI and performance optimization. I've been beggin
4.
KBuilders for Kotlin(levelmoney.github.io)
2 points by asarazan 11y ago|0 comments
5.
by asarazan 12y ago
Did this get killed? I can't find it on the list
6.
by asarazan 12y ago
I failed pretty hard. 1/5
7.
CueTableReloader - Automatically infer animations for UITableView(github.com)
8 points by asarazan 13y ago|0 comments
8.
by asarazan 13y ago
If "most cases" means the average small team (2-3 developers), then you probably have a point. Once you have more than that, I think it's absolutely necessary to enforce code style in this way.
9.
by asarazan 13y ago
Thanks for reading the article so thoroughly.
10.
by asarazan 13y ago
Yeah this is the general idea we went with. We did our best to synchronize around it, but unfortunately we can never have total control, which necessarily introduces race conditions. I would imagine this is what leads to the 0.4% crash rate
11.
by asarazan 13y ago
I was going for more of a sly joke with the title, but it appears to have not gone over well. I now regret my decision.
12.
by asarazan 13y ago
I agree. Would be nice to stop having to worry about this crap at every turn when developing on iOS.
13.
by asarazan 13y ago
We do this for various other reasons (clearing possibly corrupted state, etc), but we've never uploaded the statistics to the servers. We may begin doing this in the future.
14.
by asarazan 13y ago
We've been using Crittercism in the past and recently switched to Crashlytics, unfortunately memory crashes are one of the few exceptions (hah) to the rule, as they are SIGKILLs from the OS. Another commenter recommended touching a fil
15.
by asarazan 13y ago
I won't argue too strongly on this, as you're far more knowledgable about it than I am. However, imo the intention and semantics behind a call like CFMakeCollectable implies a transfer of ownership to an external system. A newbie
16.
by asarazan 13y ago
I would disagree pretty strongly with that. The function CFMakeCollectable is explicitly a function for dealing with the garbage collector, and its unpredictability in non-garbage-collected code is the direct cause of the bug. Doesn't
17.
by asarazan 13y ago
I should clarify. iOS does not have garbage collection and has never had garbage collection. The root of this bug is in old legacy cruft from the garbage collected days of OSX. The code is dormant in a lot of old CoreFoundation classes, and
18.
by asarazan 13y ago
I should note that, while we saw something like 0.4% increased crash rate, we actually don't have a number to compare it against for memory crashes. This is because if memory usage gets too high, the OS will send a kill signal to the p
19.
How a bug in ported garbage-collected code trashed our iOS app(tech.cueup.com)
66 points by asarazan 13y ago|29 comments
20.
by asarazan 13y ago
Worked quite well for me, then started 404'ing. Load issues I presume. Either way bravo, great idea.
21.
by asarazan 13y ago
I've been thinking about this since yesterday, and it seems like a really good solution for some use cases, but isn't there quite a bit of overhead to using a dispatche queue for fine-grained operations? I mean it seems like the overhead of
22.
by asarazan 13y ago
Hah, good catch! Fixing.
23.
by asarazan 13y ago
That would certainly be an interesting project, although the performance implications on a mobile platform may be an issue (although that's becoming more moot with each generation). In this case, however, our goal was to take common, famili
24.
by asarazan 13y ago
Fascinating. I'll have to give that a shot. Thanks!
25.
by asarazan 13y ago
As opposed to using a simple or recursive mutex while forgoing concurrent reads, in this case. There was an order of magnitude speed difference in raw lock/unlock performance. Obviously this can still be useful in read-heavy systems where t
26.
by asarazan 13y ago
As a small post-mortem, one interesting thing we learned while building this library: The reason Apple never included a read/write lock. They're hard to get right (probably not a problem for Apple), and their overhead usually counterbalance
27.
TheKitchenSync - A Tool Belt for iOS Concurrency(tech.cueup.com)
34 points by asarazan 13y ago|19 comments
28.
by asarazan 14y ago
My fiance and I had to tag team the site to finally get an 8GB after the 16GBs ran out. Got a confirmation number and receipt, but haven't received the confirmation email yet. It's like trying to get a bag o crap, but with a phone!(tm)
29.
by asarazan 14y ago
I'm a big fan of Minefold. Also, being no stranger to... "problematic" launches, I can totally sympathize here. Can't wait to see what you guys have in store with the new update, and as long as Cook or Schiller doesn't suddenly kick the buc
30.
by asarazan 14y ago
Will this check in both people travelling under the same confirmation number?

More ›