In Obj-C I have to constantly try and remember which objects I 'own', when it's mandatory to [retain] or [release] and when it's forbidden to do so, and if I ever get anything wrong, I'll end up with a silent memory leak and/or code crashing when it tries to access freed memory. It's really not very much better than using straight malloc()/free() in C. I feel like I'm spending too much time tracking details that the language should handle automatically.
Well, I'm afraid you just didn't 'get' memory management yet. Once you do, it's actually pretty simple.
To everyone who just pointed out that I'm a thimblewit and that it does in fact work. - I just installed the new version and bugger me if it doesn't work. Either they just fixed this, or I hallucinated the whole thing.
They fixed it. The Title column wasn't movable in iTunes 9.
Unfortunately there is still at least one case where you can't move a column: The Album column in the new Album List view. Oh, and you can't move the track number either.
If you don't like Safari, why not get some other browser?
There are quite a few for the iPhone. I'm not sure they are ported for the iPad just yet, but they probably will be soon enough.
Of course all those bowsers have to use the built-in WebKit as their rendering engine. But since your complaints were about the UI only, that shouldn't be a hindrance.
Now, no one outside of Apple knows *exactly* what they are looking for. But a few criteria are apparent: - use of private APIs - obvious crashing bugs - log output that indicates some problem
From what I understand they recently pulled some apps related to wifi for using undocumented APIs. If they pulled it after they fact they didn't audit the source in the first place,
From what *I* understand this happend because they changed their internal review policies. I.e. in the beginning it was 'frowned upon' to use those APIs, later it simply got forbidden.
Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.
It is.
But why?
Isn't that obvious? Because they choose not to use the system frameworks.
They should just use the video framework provided by the OS.
So instead of having one or two well supported codecs, you'd have a hundred and one that might work. You'd be back to the plugin-hell that online video was before Flash came along.
I don't see a plug-in hell if everyone is standardizing on h264. You might have the option to use one of several decoders, yes. And that's a good thing!
Anyway, it would not be Mozilla's problem. But it is if they simply refuse to play back h264 altogether.
It's hard to find a good comparison, but most seem to be pretty favorable to Theora.
That's the first time I hear this. Care to give just one example?
Anyway, I don't believe Theora has a chance. It's just like it was with MP3/Vorbis. Everything supports H264 and most people have absolutely no incentive to use anything else, let alone some obscure OSS codec.
Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.
It is.
Repeat after me: H.264 is NOT FREE, not by a long way. If Firefox included H.264 support then Firefox would also NOT BE FREE. It would be illegal for most of us to distribute a copy.
They should just use the video framework provided by the OS.
But they don't want to. Because then they wouldn't get to push their 'free' (albeit inferior) OSS codec.
The iPod runs a closed source OS that doesn't even support multitasking
Of course the iPhone OS supports multitasking.
It's just that Apple decided that third party developers are not allowed to let their applications run in the background. That is not a deficiency of the OS.
If you have a song you bought on iTunes that is DRM'd, you cannot sync it
Why not? You can do with your DRM'd files whatever you want. Copy them a thousand times. To your Pre, your cell phone or wherever the heck you want. What you *can't* do is *play* them back on anything else than an authorized Apple device.
(Good thing all music from the iTunes Store has been DRM free for some time now.)
calling that monstrosity of a data structure "plain straightforward XML" is a stretch! I've used it as an example of how NOT to format data - it's almost as if they wanted to appear to be helpful and open but in fact make life as hard as possible.
It is in Apple's property list format. This is not supposed to be pretty; it's just *very* easy to use with the built in libraries. You can read more about property lists here:
Touch, Multi-Touch, and Pen are all already supported in the core of the Windows 7 operating system. This isn't a small feat. No other OS has that today.
Mac OS X *does* have Touch and Multi-Touch support build in.
There's als support for Tablets and Pen input. (Though I'm not sure how it compares to Windows.)
How long does it take now for an average new player to level up to 85? I'm asking in actual game hours -- not how quickly one can accomplish it with massive doses of caffeine.
I don't know how many hours you'll need. This will obviously depend on your familiarity with the game and your playing style.
But recent patches made leveling - especially from 20-60 - a lot faster than it was before. And with Cataclysm they are redoing many quest lines. So I guess leveling to 85 will take about the same time it took to level to 60 in the original game.
I don't know why Apple went and turned the Windows Key into their Ctrl equivalent.
They didn't. When Mac OS was created, there was no Windows. And obviously no Windows key.
Since Windows was made to work on DOS PCs, Microsoft had to support the existing keyboards - which lacked a specific command key. So they went and (mis-)used the Control key instead.
Only when Windows became the de-facto standard OS for generic PCs was when they introduced a Windows key. Sadly they went with the easiest route and did *not* remap shortcuts from Control to the Windows key. Which is why the Windows key on Windows is still largely useless.
Slashdot Mirror
I'm still trying to get "Donuts, Beer, and Hookers" made.
On second thought, forget about the Donuts and the Beer.
(Sorry, I had too. ;))
I really cannot comprehend how it can be legal to sell a camera whose recording which i made I cannot distribute without paying to some third party.
You can. Unless you are raking in money with it, in which case you would have no problem paying a minor fee for a great video codec.
Which camera would you buy, one with WebM encoder or with H.264?
H.264. It's just better and has support by almost everything.
What if they [...]
They won't.
How would you like that, fanboy?
Look, just because someone doesn't HATE Apple and has a more realistic view of the company than you, he is not necessarily a fanboy.
In Obj-C I have to constantly try and remember which objects I 'own', when it's mandatory to [retain] or [release] and when it's forbidden to do so, and if I ever get anything wrong, I'll end up with a silent memory leak and/or code crashing when it tries to access freed memory. It's really not very much better than using straight malloc()/free() in C. I feel like I'm spending too much time tracking details that the language should handle automatically.
Well, I'm afraid you just didn't 'get' memory management yet. Once you do, it's actually pretty simple.
This is what you need to learn:
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/MemoryMgmt/MemoryMgmt.html
Most important is the use of accessors and understanding the autorelease pool.
If you are using a current version of Safari, there's also an extension:
http://hoyois.github.com/safariextensions/clicktoflash/
To everyone who just pointed out that I'm a thimblewit and that it does in fact work. - I just installed the new version and bugger me if it doesn't work. Either they just fixed this, or I hallucinated the whole thing.
They fixed it. The Title column wasn't movable in iTunes 9.
Unfortunately there is still at least one case where you can't move a column: The Album column in the new Album List view. Oh, and you can't move the track number either.
If you don't like Safari, why not get some other browser?
There are quite a few for the iPhone. I'm not sure they are ported for the iPad just yet, but they probably will be soon enough.
Of course all those bowsers have to use the built-in WebKit as their rendering engine. But since your complaints were about the UI only, that shouldn't be a hindrance.
but I don't think Apple is doing an audit
They do.
Now, no one outside of Apple knows *exactly* what they are looking for. But a few criteria are apparent:
- use of private APIs
- obvious crashing bugs
- log output that indicates some problem
From what I understand they recently pulled some apps related to wifi for using undocumented APIs. If they pulled it after they fact they didn't audit the source in the first place,
From what *I* understand this happend because they changed their internal review policies. I.e. in the beginning it was 'frowned upon' to use those APIs, later it simply got forbidden.
Oh, and did I mention, we now do rounded borders?!
That's nice. What about gradients?
But why?
Isn't that obvious? Because they choose not to use the system frameworks.
So instead of having one or two well supported codecs, you'd have a hundred and one that might work. You'd be back to the plugin-hell that online video was before Flash came along.
I don't see a plug-in hell if everyone is standardizing on h264. You might have the option to use one of several decoders, yes. And that's a good thing!
Anyway, it would not be Mozilla's problem. But it is if they simply refuse to play back h264 altogether.
It's hard to find a good comparison, but most seem to be pretty favorable to Theora.
That's the first time I hear this. Care to give just one example?
Anyway, I don't believe Theora has a chance. It's just like it was with MP3/Vorbis. Everything supports H264 and most people have absolutely no incentive to use anything else, let alone some obscure OSS codec.
Host codes aren't intended to be exposed to the hostile web.
In case of the Quicktime framework, they certainly are.
You'd get 0wned up quicker than you could even say "video".
That's a problem of the provider of the codec then. Let them worry about it.
The most common host platforms don't ship with a h264 codec in their media framework.
But it can be added. Which actually is all the point about a system provided media framework.
Everytime this topic comes up I am amazed at how many people think that it's somehow Mozilla's fault that Firefox doesn't support H.264.
It is.
Repeat after me: H.264 is NOT FREE, not by a long way. If Firefox included H.264 support then Firefox would also NOT BE FREE. It would be illegal for most of us to distribute a copy.
They should just use the video framework provided by the OS.
But they don't want to. Because then they wouldn't get to push their 'free' (albeit inferior) OSS codec.
The iPod runs a closed source OS that doesn't even support multitasking
Of course the iPhone OS supports multitasking.
It's just that Apple decided that third party developers are not allowed to let their applications run in the background. That is not a deficiency of the OS.
I can't, but google can:
[...]
http://images.google.nl/search?q=osx+virus+in+the+wild
I guess you did not bother to actually check the search results, right?
Because I can't find any report about a real virus in the wild.
Oh, by the way, Google says Barack Obama is a Jew:
http://www.google.com/search?rls=en&q=barrack+obama+jew
(Hint: He's not.)
If you have a song you bought on iTunes that is DRM'd, you cannot sync it
Why not? You can do with your DRM'd files whatever you want. Copy them a thousand times. To your Pre, your cell phone or wherever the heck you want. What you *can't* do is *play* them back on anything else than an authorized Apple device.
(Good thing all music from the iTunes Store has been DRM free for some time now.)
calling that monstrosity of a data structure "plain straightforward XML" is a stretch! I've used it as an example of how NOT to format data - it's almost as if they wanted to appear to be helpful and open but in fact make life as hard as possible.
It is in Apple's property list format. This is not supposed to be pretty; it's just *very* easy to use with the built in libraries. You can read more about property lists here:
http://developer.apple.com/mac/library/documentation/General/Conceptual/DevPedia-CocoaCore/PropertyList.html
Or drags and drops without rubbing their finger raw and/or dropping things all over the desktop?
You never used a MacBook?
Just double-tap-and-hold and the item 'sticks' to the mouse pointer. Move it to the target an tap.
Touch, Multi-Touch, and Pen are all already supported in the core of the Windows 7 operating system. This isn't a small feat. No other OS has that today.
Mac OS X *does* have Touch and Multi-Touch support build in.
There's als support for Tablets and Pen input.
(Though I'm not sure how it compares to Windows.)
http://developer.apple.com/mac/library/documentation/AppKit/Reference/NSTouch_Class/Reference/Reference.html
I vote for the "plain fucking stupid" option...
Is that in any way related to the "Cowboy Neal" option?
I would like to add that most of those phrases are horribly wrong. Like google-translation-wrong. ;-)
If there's no way to turn this off, like their damn "you just downloaded this file, do you want to open it" dialog, [...]
Try this:
http://www.macosxhints.com/article.php?story=2009081808315511
How long does it take now for an average new player to level up to 85? I'm asking in actual game hours -- not how quickly one can accomplish it with massive doses of caffeine.
I don't know how many hours you'll need. This will obviously depend on your familiarity with the game and your playing style.
But recent patches made leveling - especially from 20-60 - a lot faster than it was before. And with Cataclysm they are redoing many quest lines. So I guess leveling to 85 will take about the same time it took to level to 60 in the original game.
If I don't want to pay the fee, I can grab the source and compile it for myself.
Well, yes. But you can't install it on your iPhone unless you jailbreaked the device or you pay the yearly $99 developer fee.
Just saying.
I don't know why Apple went and turned the Windows Key into their Ctrl equivalent.
They didn't. When Mac OS was created, there was no Windows. And obviously no Windows key.
Since Windows was made to work on DOS PCs, Microsoft had to support the existing keyboards - which lacked a specific command key. So they went and (mis-)used the Control key instead.
Only when Windows became the de-facto standard OS for generic PCs was when they introduced a Windows key. Sadly they went with the easiest route and did *not* remap shortcuts from Control to the Windows key. Which is why the Windows key on Windows is still largely useless.