![]() ![]() Don’t get us wrong, probably if you look hard enough, you’ll still find demand for Objective-C development (probably maintenance is a more suited word here). Looking at some statistics from the StackOverflow 2021 survey, we see that 5.1% of respondents use Swift, whereas 2.8% use Objective-C, making it an approximate 2:1 ratio. There are a lot of indicators telling us there’s still a ton of legacy Objective-C code, both from Apple and from other developers, that’s still in use. Furthermore, Objective-C is a piece of art, creators packed genius solutions and were constantly improving it, so us developers were able to use it at our advantage. ![]() We’d like to point out that our developers mostly loved programming in Objective-C and still love it for its power to deliver products. ![]() We know our initial thoughts are rather harsh towards Objective-C. After giving it some thought, however, we can’t come up with an edge case that would make the decision leaning toward using Objective-C for iOS mobile application development.ĭisclaimer: we’re assuming you are a company that doesn’t only hire developers with Objective-C knowledge at their disposal. Sure, developers may deliver apps or libraries regardless of whether the chosen language is Swift or Objective-C. There’s a good chance going with Swift would yield quicker results. It’s probably easy to say that whatever end goal you would want to achieve with Objective-C you can achieve it with as well with Swift. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |