Timeline for Was Objective-C really a hindrance to Apple software development? [closed]
Current License: CC BY-SA 4.0
33 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2020 at 11:14 | vote | accept | Neil Meyer | ||
| Sep 6, 2019 at 13:46 | comment | added | spnkr | to play devil's advocate: objective-c was/is very off-putting for low-skill-level developers. so when that was the only choice, only high skill level developers could make apps. so mac apps were good because only very smart people made them. | |
| Apr 26, 2019 at 7:43 | vote | accept | Neil Meyer | ||
| Aug 26, 2020 at 11:14 | |||||
| Apr 24, 2019 at 10:12 | comment | added | JeremyP | Unfortunately, this interesting question has been put on hold. Even more unfortunately, the reason is justified. Anyway, no is the answer. Most of the competition was using C++ or even still is using C++. Objective-C is vastly superior to C++ for building GUI based application user interfaces. | |
| Apr 24, 2019 at 7:51 | history | closed |
Raffzahn tofro isanae Brian Tompsett - 汤莱恩 pipe |
Opinion-based | |
| Apr 24, 2019 at 7:45 | comment | added | Aaron F | "greybeards"... "of this era"... it wasn't that long ago! :-) | |
| Apr 24, 2019 at 7:28 | comment | added | ChatterOne | So... you're asking someone on the internet if it was just the experience of someone on the internet? | |
| Apr 24, 2019 at 0:13 | comment | added | aaa90210 | Actually apples was going down the gurgler around the time Jobs returned (and brought Obj-C with him), and it was up up up after that. Did it need to be replaced with a more modern language? Probably, but look how far it got them. | |
| Apr 23, 2019 at 23:56 | answer | added | Justin Ohms | timeline score: 3 | |
| Apr 23, 2019 at 22:54 | answer | added | Christophe | timeline score: 6 | |
| Apr 23, 2019 at 22:50 | comment | added | Alexander | Someone (I don't know enough to do it well myself) should delve into the ObjC runtime, and how important it was to the success of Apple platforms because of Interface Builder, Cocoa bindings, and KVO. | |
| Apr 23, 2019 at 22:11 | answer | added | Mohair | timeline score: 3 | |
| S Apr 23, 2019 at 21:35 | history | suggested | Warren Young | CC BY-SA 4.0 |
spelling and capitalization fixes
|
| Apr 23, 2019 at 20:32 | comment | added | Kelvin Sherlock | Javascript hipsters complain about Objective C, but people don't usually call them "greybeards". | |
| Apr 23, 2019 at 20:18 | review | Suggested edits | |||
| S Apr 23, 2019 at 21:35 | |||||
| Apr 23, 2019 at 20:02 | answer | added | gnasher729 | timeline score: 4 | |
| Apr 23, 2019 at 17:14 | comment | added | D. Patrick | @MasonWheeler, Chris Lattner's first commit to Swift was in July of 2010. Steve Jobs resigned August 24th, 2011. Jobs was still at the helm when they started working on Swift. | |
| Apr 23, 2019 at 16:28 | answer | added | Brian H | timeline score: 6 | |
| Apr 23, 2019 at 16:21 | comment | added | Brian H | Just as a counter argument, the fact that development was not hindered by Obj-C is self-evident just by looking at the massive success of the App Store. After all, the great mass of Obj-C developers are NOT Apple employees; they are 3rd party iOS developers. | |
| Apr 23, 2019 at 16:20 | comment | added | Raffzahn | @MasonWheeler Err... you may want to take a look at it first. The message handling is the key idea about OOP in ObjC, it's not really needed to 'support infrastructure' as that can be done from any language. Keeping that core principle meant it's worth it - while C like parts got removed. But hey, this is ofc a very opinionated. Like there are people prefer cryptic C code over Pascal clarity. So each in his own way. | |
| Apr 23, 2019 at 16:04 | comment | added | Mason Wheeler | @Raffzahn Yeah, they kind of had to keep support for the infrastructure that all the OS APIs were built on... | |
| Apr 23, 2019 at 15:59 | comment | added | Raffzahn | @MasonWheeler Hmm, looking at Swift, it is noteworthy that the Objective C style of message based dynamic linking was kept, while the C style parts were dropped. Seams like Objective C's merits did outlast Jobs time on the planet. | |
| Apr 23, 2019 at 15:57 | answer | added | Raffzahn | timeline score: 8 | |
| Apr 23, 2019 at 15:32 | comment | added | dashnick | Probably because Jobs wasn't a programmer :) | |
| Apr 23, 2019 at 15:30 | comment | added | Mason Wheeler | Whatever various people's anecdotes may claim, it's hard to argue with the timing evidence. Objective-C was introduced at Apple when Steve Jobs came back and started stuffing it down everyone's throats, and when it was announced that he had terminal cancer, Apple didn't even wait for him to be dead before they started working on a replacement for it! It's difficult to draw any other conclusion than that Obj-C was something that Jobs personally loved and most of the rest of the company hated. | |
| Apr 23, 2019 at 15:25 | answer | added | DarkDust | timeline score: 7 | |
| Apr 23, 2019 at 15:22 | answer | added | Maury Markowitz | timeline score: 35 | |
| Apr 23, 2019 at 15:05 | review | Close votes | |||
| Apr 23, 2019 at 17:30 | |||||
| Apr 23, 2019 at 14:54 | history | became hot network question | |||
| Apr 23, 2019 at 13:26 | answer | added | Tommy | timeline score: 23 | |
| Apr 23, 2019 at 13:26 | answer | added | Brian Knoblauch | timeline score: 5 | |
| Apr 23, 2019 at 13:01 | history | edited | Omar and Lorraine |
edited tags
|
|
| Apr 23, 2019 at 12:07 | history | asked | Neil Meyer | CC BY-SA 4.0 |