3 ms·

>Funny how Apple still relies on language without any form of namespace support for their system. Yeah, very funny, especially since they don't have any other

by batista 14y ago

>Funny how Apple still relies on language without any form of namespace support for their system. Yeah, very funny, especially since they don't have any other pragmatic reasons to use it, ie. it being a more dynamic OO C than C++ while retaining full C power, them having huge API libraries for it over 25 years of NeXT/OS X development, etc etc. >Prefixes are not a solution as they have no ways to avoid collisions. It's not like you use lots of third party libs (if any at all) in OS X. >So much for supporting large scale development with Objective-C. Yeah, I mean they have just those tiny projects in it, like iPhoto, Final Cut Pro, Pages, Numbers, the whole Cocoa and Cocoa Touch stack, etc. But we need more support for large scale development, because there are many many teams of 100s of programmers that also want to write 20 million lines Objective-C programs. And C is even worse, you just have small projects like the Linux kernel written in it, due to the severe issue of lack of namespaces. /s

pjmlp 14y ago
> It's not like you use lots of third party libs (if any at all) in OS X. Yeah, that only works if you don't use any third party stuff. > Yeah, I mean they have just those tiny projects in it, like iPhoto, Final Cut Pro, Pages, Numbers, the whole Cocoa and Cocoa Touch stack, etc. There are all internal Apple projects, as such the company can decide which prefixes to use. If they happen to clash with some third party small company, bad luck for the external company. > But we need more support for large scale development, because there are many many teams of 100s of programmers that also want to write 20 million lines Objective-C programs. Well, most projects I work on professionally, are the typical enterprise projects with 100+ developers, scattered across the globe. > And C is even worse, you just have small projects like the Linux kernel written in it, due to the severe issue of lack of namespaces. While you're being sarcastic here, let me tell you that Linux kernel works, because everyone that wants to add code to the kernel is obliged to follow certain conventions. You cannot have that with third party code that you don't control. Specially if it is delivered as commercial closed source libraries, which is quite common in the enterprise world.

by batista 14y ago

pjmlp 14y ago

> It's not like you use lots of third party libs (if any at all) in OS X. Yeah, that only works if you don't use any third party stuff. > Yeah, I mean they have just those tiny projects in it, like iPhoto, Final Cut Pro, Pages, Numbers, the whole Cocoa and Cocoa Touch stack, etc. There are all internal Apple projects, as such the company can decide which prefixes to use. If they happen to clash with some third party small company, bad luck for the external company. > But we need more support for large scale development, because there are many many teams of 100s of programmers that also want to write 20 million lines Objective-C programs. Well, most projects I work on professionally, are the typical enterprise projects with 100+ developers, scattered across the globe. > And C is even worse, you just have small projects like the Linux kernel written in it, due to the severe issue of lack of namespaces. While you're being sarcastic here, let me tell you that Linux kernel works, because everyone that wants to add code to the kernel is obliged to follow certain conventions. You cannot have that with third party code that you don't control. Specially if it is delivered as commercial closed source libraries, which is quite common in the enterprise world.