Darling, we have Java - maybe we'll see, at a later day, Objective-Java at a later date, as SUN works towards making the Java JVM more non-Java language friendly - but until then, I think that Objective-C still offers alot to developers, and its just a matter of Apple properly marketing their EXISTING technology, which can already solve ALOT of problems that programmers are still doing manually, rather than using the tools and language features that Apple has made available.
Oh, and regards to garbage collection, Objective-C/Cocoa already includes a limited amount of garbage collection already, so lets not go nuts on the garbage collection front.
What is required is not necessarily a new framework and language - Microsoft NEED it because win32 sucks so royally, and C++/C with win32 is the eqivilant of being kicked in the nutts a number of times, then having a cactus rammed up ones ass - not a pleasent experience by any stretch of the imagination.
Cocoa + Objective-C is a match made in heaven; and as long as Apple keep working towards providing better development tools for all the coders out there, the issue isn't so much features and garbage collection, its about developing tools that make tracking development easier, especially on large projects and providing as much ready-to-use code for developers to use rather than having to write their own code from scratch each time they want a certain function. It shouldn't be able removing control, the move should be providing more feature complete classes, better documentation, and superior tools.
I agree that Cocoa + Objective-C is a match made in heaven.
Cocoa(Openstep/NeXTSTEP) is built with Objective-C and NeXT's MVC specific design model.
Java-Objective-C will NEVER HAPPEN AGAIN. They killed the bridge because it was a collossal waste of resources.
Siracusa musn't develop much in Cocoa and Objective-C.
I agree with you on the garbage collection issue and clearly Siracusa doesn't get NSAutoReleasePool and how varied the counting options work within Objective-C.
Siracusa was one of them who couldn't handle us from NeXT merging with Apple and now he's concerned about OS X and Cocoa? And some notion of replacing Objective-C?
Objective-C will evolve and so will the Frameworks.
Comments
Originally posted by Placebo
This thread has the longest average post size I've seen in a while. Let me get you guys a new page here.
Ahhh damn, now I have to fill this page with more crap. Don't these things ever end?
Originally posted by kaiwai
Darling, we have Java - maybe we'll see, at a later day, Objective-Java at a later date, as SUN works towards making the Java JVM more non-Java language friendly - but until then, I think that Objective-C still offers alot to developers, and its just a matter of Apple properly marketing their EXISTING technology, which can already solve ALOT of problems that programmers are still doing manually, rather than using the tools and language features that Apple has made available.
Oh, and regards to garbage collection, Objective-C/Cocoa already includes a limited amount of garbage collection already, so lets not go nuts on the garbage collection front.
What is required is not necessarily a new framework and language - Microsoft NEED it because win32 sucks so royally, and C++/C with win32 is the eqivilant of being kicked in the nutts a number of times, then having a cactus rammed up ones ass - not a pleasent experience by any stretch of the imagination.
Cocoa + Objective-C is a match made in heaven; and as long as Apple keep working towards providing better development tools for all the coders out there, the issue isn't so much features and garbage collection, its about developing tools that make tracking development easier, especially on large projects and providing as much ready-to-use code for developers to use rather than having to write their own code from scratch each time they want a certain function. It shouldn't be able removing control, the move should be providing more feature complete classes, better documentation, and superior tools.
I agree that Cocoa + Objective-C is a match made in heaven.
Cocoa(Openstep/NeXTSTEP) is built with Objective-C and NeXT's MVC specific design model.
Java-Objective-C will NEVER HAPPEN AGAIN. They killed the bridge because it was a collossal waste of resources.
Siracusa musn't develop much in Cocoa and Objective-C.
I agree with you on the garbage collection issue and clearly Siracusa doesn't get NSAutoReleasePool and how varied the counting options work within Objective-C.
Siracusa was one of them who couldn't handle us from NeXT merging with Apple and now he's concerned about OS X and Cocoa? And some notion of replacing Objective-C?
Objective-C will evolve and so will the Frameworks.
Originally posted by ZO
I feel like at I'm at a very very very long tennis match...
Between two chess players...