3 ms·
Well to start with, there are patent problems. IANAL, but I presume Apple's thought long and hard about this. Then you have the licensing issues. To get the
by drewcrawford 17y ago
Well to start with, there are patent problems. IANAL, but I presume Apple's thought long and hard about this.
Then you have the licensing issues. To get the documentation, you need to clickwrap through the license that says you can't clone it. So it's not even like cleanroom engineering, where it's possible to legally document some assembly code you bought in a box.
Then there's the real problem--Apple's SDKs are really quite good, all things considered. Cloning them would be very hard. There is some serious, complicated stuff going on under the hood, especially to make it performant. To say that a couple of clever Lisp hackers can clone it is to say that Apple could have built the API with a couple of clever hackers to begin with. It's to say that Jobs is stupid for having hundreds of people work on it.
- stcredzero 17y agoWhat makes you think that hundreds of people are working in the SDK? I suspect the core frameworks are really only being worked on by small groups. If one targeted a specific kind of application, let's say 2D gaming, then the amount of functionality is well within the size of what one or two talented hackers can do. After all, they wouldn't have to write an SDK. All they have to do is to write an Objective-C parser and target another 2D game SDK on another platform.
- drewcrawford 17y agoLet's say on average, 2D games only use 20% of the APIs. Problem: Every 2D game uses a different 20%.
- stcredzero 17y agoI don't see it. How do you explain something like PyGlet?