|
My background was originally C# where i worked on a variety of platforms such as ASP.Net, Silverlight, WPF, etc.. So after spending 6+ years working mainly in C#, I was both excited and hesitant to take a look at Objective-C. The first few months i spent a lot of time switching back and forth between Google and XCode(the IDE for iOS), as i familiarized myself with the syntax and API's of this "foreign" language. And although it wasn't nearly as hard as i thought it would be, it would have saved me a lot of time if there was a centralized place where i could get all the information i needed. Thus i've decided to share what i've learned in this series of posts, where i'll take you step by step through some of the areas that slowed me down, to make your experience a much smoother one. @"This will be an interesting series to follow";
|
|
|
|
|
Objective C looks as alkward as COBOL.
|
|
|
|
|
Awkward yes, but it doesn't have nearly enouch CAPITALIZATION OF BOILERPLATE[^] to reach the depths that COBOL calls home.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Not really very knowledgable on COBOL. Just know I started in Basic and FORTRAN, and one look at COBOL convinced me I did not want to work in that language.
|
|
|
|