Someone Copied the SNAP Source Code to Github Before Sony Pulled it Down
github.com
github.com
There’s a couple of major players, namely Microsoft and Oracle; I wouldn’t be surprised if Apple was unhappy with this and moved to keep their skill-bank walled in.
Other than that, maybe a pointy-haired boss wanted something like .NET because it sounded more internet-y.
I would find this surprising: more companies using obj-c means more people using obj-c means more people able to code on Apple platforms, which use obj-c nigh-exclusively.
If this effort went through, GNUStep could eventually be used to port Mac software to other platforms (Windows included) or to run it against controlled environments that would render iTunes DRM useless, and that's something Apple won't let happen.
Of course, this isn't the same as if, for example, Sony directly circumvented or undermined Apple's security or certification technology.
I am not so sure. OpenStep (the spec) is probably safe, but that doesn't make sure the rest of Cocoa (which implements a superset of OpenStep) is immune from a patent or IP-related offensive.
GNUstep has already been tracking Apple's Cocoa for years without Apple complaining.
If you had any sort of evidence to support your wild theory I would be all ears.
If enough momentum is built behind GNUStep and it becomes a superset of Cocoa, it would be rather trivial to build a Wine-like environment for running OSX software on other OSs and that, I am sure, Apple would strongly oppose.
There are already people releasing software for both:
http://en.wikipedia.org/wiki/GNUstep#Ported_from_NeXTSTEP.2C...
Regardless of whether or not they are exactly compatible (some tweaking is necessary) I wonder where you get the idea that Apple would attack the GNUstep folks. Sounds like standard-grade FUD to me.
It's not FUD: it's just sane business strategy. If and when Apple sees GNUStep as a competitive threat (i.e. if a product based on it robs some market share), they'll attack it with whatever weapons they find most effective at the time. As it is now, it's not threatening them and Apple may even benefit from it, so, they'll leave GNUStep alone for the time being.
At least that's what I would do in their shoes.
As for why Sony halted its project, my bet would be the implicit patent grant in LGPLv2.1. That may feel uncomfortable for someone who needs to cross-license IP.
One could make up doomsday scenarios all day, but the fact is that Apple has nothing to lose by wider adoption of Objective-C and similar libraries.
Is Chrome in any way critical or considered a competitive advantage for Apple?
[0] http://blog.deliciousrobots.com/2010/11/27/sonys-changes-to-...
[1] http://www.engadget.com/2010/11/28/sony-fires-barrage-of-tou...
I think it's far more likely that it was shelved due to internal politics or pressure from Google than any other theory.
How many editors out there lack regex and multiple clipboards, both of which have been around forever in vi?
Know the past or you may accidentally reimplement a solution to a problem that has already solved in a better way.
ObjC is basically Smalltalk weakened by some dangerous efficiency hacks we haven't needed for a decade.
IBM and others are actively working on bringing Smalltalk into the future.
Similarly, virtual memory backed by paging to a swapfile is the beautiful, "right" solution to me intuitively for a memory architecture that is made of several storage classes of highly different access times; yet, I have to admit that hourglasses/beachballs aren't a part of most "mobile" systems but often are — frustratingly — part of the desktop OS experience.
In actual practice, there's very little unchecked pointer arithmetic in a Cocoa [Touch] app — you don't access the elements of an NSDictionary via direct (to you) pointer arithmetic but through well-tested methods that fail similarly to how to out-of-bounds collection access fails in managed systems.
Anyway, it's unfortunate that such things are essentially non-comparable in a scientific way to my knowledge; but my experience of ObjC apps is not that they tend to be more crashy or likely to corrupt my data than the Java/C# apps that I also use day-to-day.
we haven't needed for a decade.
You've hit the nail on the head with regard to my complaint.