HN user

altyus

22 karma
Posts2
Comments13
View on HN

To address the "moving off of Parse" comment: The way I've dealt with this is to use the Parse REST Client instead of the Parse SDK. That way you're object model isn't tied to parse PFObjects and you can swap out the Networking layer if you choose to move to another vendor. If you control the full stack, you can even model your backend to more-or-less mimic Parse's Rest API.

iOS6 user base will be miniscule in a few weeks unless you are targeting corporate or education markets which update slowly.

Swift impressions 12 years ago

That is completely irrelevant to this articles point of illustrating Objective-C bugs that are fixed by Swift. Nowhere did it claim that no other language had solutions for @Override

Swift impressions 12 years ago

haha these answers are cracking me up. Who cares? Do people develop iPhone apps using Go? Swift never claimed to invent new paradigms that didn't exist in other languages, it simply brought them to Cocoa.

Swift impressions 12 years ago

That's kind of irrelevant. The only thing that really matters since swift is built to natively support Cocoa, is was this possible in Objective-C (and to a lesser extent C and C++).

Goodbye Academia 12 years ago

I stopped reading at the first paragraph. What an inflated sense of self to think that ones' own feelings after leaving academia imply a dire situation for all of academia.