3 ms·

you mean objective-c++? c++ has no idea about obj-c... another thing most people forget is that the entire programming community rejected obj-c as deficient in

by jheriko 10y ago

you mean objective-c++? c++ has no idea about obj-c... another thing most people forget is that the entire programming community rejected obj-c as deficient in its very early days... it only persists thanks to the ego of former nextstep employees afaik. and now apple employees got lumped with it... which i'd suspect helped create the internal pressure for swift... so some good came at the end of it all. :)

astrange 10y ago
Objective-C was the major inspiration for Java - you'll notice how little it looks like C++ - and therefore C# and co, so it's been very influential ever since the 90s. It's not worth listening to anyone who dislikes Obj-C just because of the [] syntax, which doesn't matter after the first 48 hours.
- _asummers 10y ago
  This about mirrors my opinions about Objective-C. http://twistedoakstudios.com/blog/Post8237_a-years-worth-of-opinions-about-objective-c http://twistedoakstudios.com/blog/Post8237_a-years-worth-of-...
  - astrange 10y ago
    > Lastly, neither has generic types. Not true anymore; ObjC has generics with type erasure. (But not all the cases can be exported to Swift.) > Instead, Objective-C has nil, which is like null except it won’t stop the program when you accidentally use it. That's… not quite right… but I guess he has the visible effects down. Anyway, ObjC has nullability annotations now for this. > For example, in Objective-C many objects have both a “core foundation” form and a “new style” “NeXTSTEP” form This is not legacy baggage, it's an intentional C bridge. > This is justified by conventions strongly favoring you not catching exceptions, and apparently the speed benefits are non-negligible, but it still blows my mind that Apple has their language default to incorrect behavior. He shouldn't use ARC+exceptions, because Cocoa itself is not exception-safe. Just quit the app if you get one.
- chillacy 10y ago
  > It's not worth listening to anyone who dislikes Obj-C just because of the [] syntax, which doesn't matter after the first 48 hours. That's pretty much my thoughts these days. If you have only the most superficial understanding of these languages, then that's what you'll get caught up on, but that's like saying Java and JavaScript are similar because they both use curly braces and dot notation for their methods. Yea, that is true, but it's a superficial similarity.
informatimago 10y ago
Objective-C is what makes developping applications on iOS so much more efficient than on Android; even if only indirectly, thru the frameworks provided: if Android cannot provide frameworks usable more efficiently than Apple, it's because they're using Java instead of Objective-C. https://infinum.co/the-capsized-eight/articles/android-development-is-30-percent-more-expensive-than-ios https://infinum.co/the-capsized-eight/articles/android-devel...

by jheriko 10y ago

astrange 10y ago

Objective-C was the major inspiration for Java - you'll notice how little it looks like C++ - and therefore C# and co, so it's been very influential ever since the 90s. It's not worth listening to anyone who dislikes Obj-C just because of the [] syntax, which doesn't matter after the first 48 hours.

_asummers 10y ago
This about mirrors my opinions about Objective-C. http://twistedoakstudios.com/blog/Post8237_a-years-worth-of-opinions-about-objective-c http://twistedoakstudios.com/blog/Post8237_a-years-worth-of-...
- astrange 10y ago
  > Lastly, neither has generic types. Not true anymore; ObjC has generics with type erasure. (But not all the cases can be exported to Swift.) > Instead, Objective-C has nil, which is like null except it won’t stop the program when you accidentally use it. That's… not quite right… but I guess he has the visible effects down. Anyway, ObjC has nullability annotations now for this. > For example, in Objective-C many objects have both a “core foundation” form and a “new style” “NeXTSTEP” form This is not legacy baggage, it's an intentional C bridge. > This is justified by conventions strongly favoring you not catching exceptions, and apparently the speed benefits are non-negligible, but it still blows my mind that Apple has their language default to incorrect behavior. He shouldn't use ARC+exceptions, because Cocoa itself is not exception-safe. Just quit the app if you get one.
chillacy 10y ago
> It's not worth listening to anyone who dislikes Obj-C just because of the [] syntax, which doesn't matter after the first 48 hours. That's pretty much my thoughts these days. If you have only the most superficial understanding of these languages, then that's what you'll get caught up on, but that's like saying Java and JavaScript are similar because they both use curly braces and dot notation for their methods. Yea, that is true, but it's a superficial similarity.

informatimago 10y ago

Objective-C is what makes developping applications on iOS so much more efficient than on Android; even if only indirectly, thru the frameworks provided: if Android cannot provide frameworks usable more efficiently than Apple, it's because they're using Java instead of Objective-C. https://infinum.co/the-capsized-eight/articles/android-development-is-30-percent-more-expensive-than-ios https://infinum.co/the-capsized-eight/articles/android-devel...