Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

FastImageCache – iOS library for quickly displaying images while scrolling

github.com

Post reply on HN
Print view View original

31–35 of 35 posts

Re: FastImageCache – iOS library for quickly displaying images while scrolling

#31

Post by jdewald »

nielsbot wrote: post #26
mallorypaine wrote: post #16

Earlier quoted context omitted.

Hello. Mallory Paine here. I wrote FIC. This is not legacy code...it should be trivial to convert it to ARC and performance should be unaffected. I'm a bit old school myself so I chose to write it with manual retains. Does this approach make the code more difficult for you to use within an ARC project?

It might even be faster under ARC since I think the compiler can optimize some retain/release calls. I think the ARC retain and release may be faster than -retain/-release, but I'm not sure about that. Overall, yes, it's less smooth to include non-ARC code in an ARC project.

I was under the impression that ARC simply inserts the retain/releases into the code essentially write before the compile, so in theory would be equivalent.

Re: FastImageCache – iOS library for quickly displaying images while scrolling

#32

Post by dirtyaura »

sircambridge wrote: post #8

A better solution then dealing with 60fps scrolling : Don't scroll, Flip!

Not really, scrolling seems to be very natural interaction model on touch screens. If you compare UI approaches of different apps, most of the popular apps use scrolling, flipping hasn't really proven itself and it's a bit gimmicky

Re: FastImageCache – iOS library for quickly displaying images while scrolling

#33

Post by LinaLauneBaer »

jdewald wrote: post #31
nielsbot wrote: post #26

Earlier quoted context omitted.

It might even be faster under ARC since I think the compiler can optimize some retain/release calls. I think the ARC retain and release may be faster than -retain/-release, but I'm not sure about that. Overall, yes, it's less smooth to include non-ARC code in an ARC project.

I was under the impression that ARC simply inserts the retain/releases into the code essentially write before the compile, so in theory would be equivalent.

ARC inserts the retain/release calls but once that is done there is an additional step where duplicate retain/release pairs are eliminated.

Re: FastImageCache – iOS library for quickly displaying images while scrolling

#34

Post by rimantas »

cclogg wrote: post #21
mallorypaine wrote: post #16

Earlier quoted context omitted.

Hello. Mallory Paine here. I wrote FIC. This is not legacy code...it should be trivial to convert it to ARC and performance should be unaffected. I'm a bit old school myself so I chose to write it with manual retains. Does this approach make the code more difficult for you to use within an ARC project?

Actually you have my support for going manual. I still prefer to do all my projects without ARC (and I'm not old-school, unless 2009 is old-school). I just feel dirty everytime I use ARC, like I'm being sloppy haha. It also hides a lot about memory management that new people might never learn (and thus be in bigger trouble when something does go wrong). But I accept that it does have major advantages... One trouble n…

well, [Something alloc] also hides some about memory management…

Re: FastImageCache – iOS library for quickly displaying images while scrolling

#35

Post by lucastizma »

alayne wrote: post #15

It's not using ARC. Is this legacy code, or couldn't they get equivalent performance with ARC enabled?

As of Fast Image Cache 1.1, we now use ARC. Profiling it both ways, I didn't observe any noticeable changes to performance.
Post reply on HN