Yes, let's leave this in parenthesis and pretend it never happened, pretend they never turned KHTML into one of the most successful open source projects, across many platforms, and endlessly complain about something that happened for a few months while Apple was setting up their real project.
Because cooling a 27 kilometer long object to 1.9 K takes a lot of time. You can't just keep heating it up and cooling it back down again. You cool it down once, and keep it cooled permanently.
Part of the reason this whole thing took so long in the first place was that it had to be heated up and cooled down again.
If you're going to go out of your way to use obscure formats, you really don't have anything to complain about when you find it hard to play back your music.
3) Audio codecs. Apple players don't even support half of the codecs that other players support. Again, this is part of their strategy to lock you into the "itunes" universe.
Do you live in an alternative universe where iPods don't play MP3s, or what?
This kind of investigative journalism? The kind that puts confusing and irrelevant babble about phonecalls from friends at the start of the article? I'd hope those chances are pretty low.
Attending an Ubuntu party gets you geek points. Plus, you get a chance to meet people you might know from a mailing list. You discover that people you see every day on the subway are also Ubuntu users.
An OS X party is the closest thing to a Mac religion you can get. People go there because they want to belong with the "in crowd" of Mac users.
I like how you treat these two cases as if they were in any way different from each other.
I'm not sure what you're arguing against. Apps can include local copies of frameworks just fine on the app store, and the iPhone OS provides frameworks that apps use. It wouldn't work at all without those.
What is specifically not allowed is using external frameworks distributed separately, or internal OS frameworks.
That's linking to internal system frameworks that are not meant to be used, and may change in ways that break apps that use them on any system upgrade. It should be obvious why Apple doesn't want that.
How the hell do you get a linux desktop to become unresponsive?
Run any app that gobbles up all the memory it can find, such Firefox when it goes out of control. Locks up my Linux machine *solid* for fifteen-twenty minutes until the OOM killer finally manages to run and kill the process.
Slashdot Mirror
Do you have even the slightest idea what the ITU is?
(this has improved)
Yes, let's leave this in parenthesis and pretend it never happened, pretend they never turned KHTML into one of the most successful open source projects, across many platforms, and endlessly complain about something that happened for a few months while Apple was setting up their real project.
Because cooling a 27 kilometer long object to 1.9 K takes a lot of time. You can't just keep heating it up and cooling it back down again. You cool it down once, and keep it cooled permanently.
Part of the reason this whole thing took so long in the first place was that it had to be heated up and cooled down again.
And whaddya know, it's "+5 Insightful".
Ah yes, the cry of a man who has heard something he does not really understand, but knows he doesn't like.
Why do we care what has been "recently noted" on some mailing list we haven't ever heard of?
If you're going to go out of your way to use obscure formats, you really don't have anything to complain about when you find it hard to play back your music.
3) Audio codecs. Apple players don't even support half of the codecs that other players support. Again, this is part of their strategy to lock you into the "itunes" universe.
Do you live in an alternative universe where iPods don't play MP3s, or what?
Too bad it turns out the people with guns are the ones that are the most happy to hand over their rights, just so long as they get to keep their guns.
This kind of investigative journalism? The kind that puts confusing and irrelevant babble about phonecalls from friends at the start of the article? I'd hope those chances are pretty low.
I like how this is modded +5 Informative when it is entirely made up.
Attending an Ubuntu party gets you geek points. Plus, you get a chance to meet people you might know from a mailing list. You discover that people you see every day on the subway are also Ubuntu users.
An OS X party is the closest thing to a Mac religion you can get. People go there because they want to belong with the "in crowd" of Mac users.
I like how you treat these two cases as if they were in any way different from each other.
It's not an Apple product, so WE MUST DUMP ON IT!
Yes, nobody ever dumps on Apple products in here! They get that free pass, you know! You won't hear a single bad word about the App Store!
Just use http://www.perian.org/ instead.
Anybody who uses Vorbis and h.264 together deserves to be smacked.
And the released the source for GCD because? What about launchd? Darwin Streaming Server? Bonjour?
Also, LLVM.
Don't worry, nobody is really expecting you to be honest.
It takes you literally a single mouse click to find out who I am, but I guess that would take a little bit of marbles, huh?
Is it Crackpot Hour on Slashdot tonight? First electric universe, and now free energy?
Are those fair use applications?
Pretty sure the answer to that is "yes, of course".
I'm not sure what you're arguing against. Apps can include local copies of frameworks just fine on the app store, and the iPhone OS provides frameworks that apps use. It wouldn't work at all without those.
What is specifically not allowed is using external frameworks distributed separately, or internal OS frameworks.
Uhm... Why not?
Because that leads to dependency hell, and that leads to horrible user experience.
That's linking to internal system frameworks that are not meant to be used, and may change in ways that break apps that use them on any system upgrade. It should be obvious why Apple doesn't want that.
How the hell do you get a linux desktop to become unresponsive?
Run any app that gobbles up all the memory it can find, such Firefox when it goes out of control. Locks up my Linux machine *solid* for fifteen-twenty minutes until the OOM killer finally manages to run and kill the process.