This is awesome! Thank you so much for helping me ditch FAT32
If anyone knows how to convince xp to write to a device like that (via a 3rd party driver or whatever) I'm all ears!
Robert's Rules of Order are under copyright. Those rules are used by many groups within our government. Hopefully the version from the 50s will be out of copyright eventually.
This is a *much* bigger deal than Micky Mouse IMO.
I'll rephrase a bit. The bubble that Apple forces you into if you are a developer, is to write your code in XCode.
I'd be surprised if any approved apps in the AppStore were not written using XCode. XCode only runs on OSX. OSX only runs on Apple hardware.
The two bubbles you mention are valid, but there are more than two bubbles.
To get an app into the AppStore you must be developing using Apple hardware running OSX.
Regarding the 'Everything else is very open.' statement. If that were true, it would be easy to sync my mp3s over to my iPhone under linux. It would be easy to sync my oggs over the iTunes in the iPhone using linux. It would be easy to change cellular providers. It would be easy to play my movies purchased through iTunes under linux
In summary: Apple at every turn chooses the path that locks their customers into using their products.
Apple does make slick products, but they are not 'open'. I'd love to hear ways in which they are open though.
| There are only two bubbles Apple "forces" you into:
|
| 1. Mac OS X only runs (without hacking) on Apple hardware.
| 2. iPhones OS only runs (without hacking) App Store software.
|
| Everything else is very open.
Not quite accurate:
* To write code for the iPhone, you essentially need XCode running on Apple hardware.
* Code written for the iPhone (ObjC) is a PITA to port to any other OS other than OSX.
* I still can't sync music to my iPhone from Linux on the new firmware.
* I still can't play ogg files on the iPhone
So this 'Everything else' must not include much that I care about.
If he wants a filter that is more difficult to bypass by the child, Privoxy is pretty handy.
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?