61–70 of 119 posts
Before that, I considered Apple users to be a group of gay douchebags, but today I have learned that there is at least a sane person on the other riverside.
(I have neither developed for any smartphone nor do I possess one, so no need for "Stupid FANDROID!1!")
Seems like a very balanced article to me. The comments about Eclipse made me laugh (I just had to start using Eclipse for a different reason and hate it with the heat of a thousand suns).
Interestingly (but inevitably) as a java developer who first learned Android and then moved to iOS, the sticking points he mentions are exactly the same ones I found, but the other way around. I think Eclipse makes sense if you think like a java coder, Xcode not so much, and Objective-C will fry your mind... That said, Eclipse and the Android SDK is a pain to install even if you are a java wizard.
Why would ObjC fry anybodie's mind? I am that weird to like it (coming from web dev background: PHP, Ruby, JavaSript)?
I'm curious how it fries your mind exactly? Fries like Haskell in that it makes you learn different paradigms or fries as in challenges base assumptions on how things like OO/etc... work?
This is a great and honest article and has changed the way I think about Apple users/developers. Before that, I considered Apple users to be a group of gay douchebags, but today I have learned that there is at least a sane person on the other riverside. (I have neither developed for any smartphone nor do I possess one, so no need for "Stupid FANDROID!1!")
Why do you "have to kiss that silky smooth scrolling goodbye" if you setup your UITableViewCells in Interface Builder? I've used it for all of my apps and the scrolling is just as fast as any of Apple's native apps. Interface Builder just packages up all that initial layout code and then it is executed when the nib when it is unpackaged. After that there is no difference.
Actually there is a difference. If you create a table with a considerable number of cells (say, over 20) that contain a couple of labels and maybe an image when you swipe really fast the scrolling will hang, even if you are using the dequeue mechanism. The alternative is to paint the contents of the cell manually (that is without using UILabels and the such) using CoreGraphics. Check out the drawContentView: method h…
However I just finished an application with a UITableViewCell, defined in a nib, that had 3 labels and a image. The labels depend on the data that the row was displaying and the image was the same in every row (it was a custom disclosure image).
One of the table views that that used this cell had 100 rows and it loaded and scrolled without a hitch.
Most of the slowdowns people experience with scrolling is if they have transparent cells and/or they don't load lazy load images on a background thread.
I agree that if you've tried all sorts of optimizations and you are still experiencing slow scrolling then painting the contents manually will probably be faster but it is IMO more work then 99% of people need to do and, like naz said below, there can be accessibility issues.
When Loren Brichter wrote that 3 years ago it was a much bigger deal. The iPhone 3G was extremely underpowered compared to most of the devices people run iOS on today.
Ouch!
Interestingly (but inevitably) as a java developer who first learned Android and then moved to iOS, the sticking points he mentions are exactly the same ones I found, but the other way around. I think Eclipse makes sense if you think like a java coder, Xcode not so much, and Objective-C will fry your mind... That said, Eclipse and the Android SDK is a pain to install even if you are a java wizard.
Why would ObjC fry anybodie's mind? I am that weird to like it (coming from web dev background: PHP, Ruby, JavaSript)?
Another problem some people have is that ObjC brings to the table all the pain of C. You've got memory management and bounds checking and unsafe casts all dumped into your lap. It can be pretty painful if you're not experienced in C, C++, or ASM programming.
What a wonderful approach to development. Skip the ideological critiquing and start shipping some awesome products.. I guess that is really what separates the great developer from the good developer.
Agreed, the attitude is refreshing. Nice quote: Java is a high level programming language. It’s unproductive to have an opinion about it.
What a wonderful approach to development. Skip the ideological critiquing and start shipping some awesome products.. I guess that is really what separates the great developer from the good developer.
Agreed, the attitude is refreshing. Nice quote: Java is a high level programming language. It’s unproductive to have an opinion about it.
What's unproductive is to decide to avoid the biggest-by-number-of-units mobile platform because of Java.