Clearly I have no alternative but to rip all cables from my macs, stuff the offending sockets with wine gums, toss each useless hunk of plastic and silicon into a vat of cement and sit rocking in the corner of my room, tears streaming down my cheeks as the flames slowly engulf a photo of Steve Jobs. Oh, the humanity!
Qttask is (as the name implies) the taskbar process. Quicktime involves more than a taskbar icon.
The folder you zipped was probably the one containing Movie Player and suchlike. The libraries/extensions that handle MPEG decoding will have been installed wherever Windows usually keeps that type of thing.
Yeah, and driving to work "just works" because of all the effort the road builders put in, not because of some fad called "a car".
Perhaps you don't understand. Rendezvous is a service discovery technology. It automatically finds machines on a network offering a service. Without Rendezvous, you'd have to find out the IP address yourself.
It really IS plug and play, in that as soon as I plug my iBook into a network, I show up on everyone's iChat Rendezvous list. Pretty smart, and much more than a 'fad' in my view.
Fire has an option to 'snap' to window edges. With this option turned on, attempting to move a Fire window beneath the Dock causes it to slide back to an uncovered position.
In other words, this most likely a feature of Fire rather than a bug with the Dock.
I don't think so; maybe they share the same graphics code but they certainly don't behave the same.
I can't think of any significant examples of this. If I click a button or pull down a menu the same thing happens in both a Carbon and a Cocoa application. Perhaps I'm missing something.
Unlike Macintosh, however, if you run something like KDE on X11, you really do get a single toolkit and a completely consistent user interface.
Correct me if I'm wrong, but I think you're comparing oranges and apples here. A better comparison would be Cocoa and KDE surely? After all, in KDE on Linux, OpenOffice has a complete different set of GUI features from, say, AbiWord.
There's nothing forcing a Mac OS X user to run Swing, Classic or X11 applications in the same way as there's nothing forcing a KDE user to run OO. Like you said in your initial post, the only way to ensure consistency is to use a consistent set of applications, and it seems that running KDE offers you no more help in that respect than Mac OS X does.
We *are* talking about the same Mac OS X? This is the OS where half of the UIs are brushed metal, and half are candy-cane-looking?
Well, yes. Brushed metal windows aren't drastically different from pinstripe windows. They still behave the same, and use the same widgets.
I'm not saying it's perfect; I'm just saying that most Mac OS X applications have a familiar feel the first time I start them up. It's easy to pick on the metal/pinstripe distinction, and I'm not convinced with Apple's reasoning for introducing this second theme. But whatever the reasons, it's been implemented in a way that doesn't damage consistency as much as it could have done.
When I look at the alternatives, this transgression seems reasonably minor.
Apple is even worse, officially supporting OS 9, Carbon, Swing, and Cocoa-based applications on the same desktop, and now also X11; and in addition to all that, toolkits like Gtk+, FLTK, Swing are also being ported to native Quartz backends.
To be fair, Carbon and Cocoa applications use the same standard widgets, and the Aqua look-and-feel for Swing is pretty consistent (bar the per-window menus). X11 windows behave like regular Aqua windows, even if the contents are down to the X toolkit.
In fact, I've found that Mac OS X is the most consistent desktop environment I've used. Obviously programmers will do as they please, but I think Apple has done a good job in making it easy to put together an application that looks and behaves as users are used to.
Unless you host your own webserver, initially uploading enough of your files to make your site useful to downloaders would take far too long and be far too costly in terms of bandwidth.
With a P2P application you make your entire library of files available to the network with practially no setup.
This makes HTTP sharing pretty useless to anyone who can't/won't run their own webserver (which, I imagine, covers a large proportion of current P2P users).
That rather depends on what sort of filesystem you use, surely.
All the manufacturer needs to state is how many physical bytes their drive can hold. What done with that capacity afterwards is none of their concern, nor should it be.
Slashdot Mirror
(or should I say 'United Kingdom' in order not to alienate my Irish/Welsh/Scottish compatriates?)
*cough* Northern Irish.
Carry on!
... unless you're an 80-year-old mac user instead.
Clearly I have no alternative but to rip all cables from my macs, stuff the offending sockets with wine gums, toss each useless hunk of plastic and silicon into a vat of cement and sit rocking in the corner of my room, tears streaming down my cheeks as the flames slowly engulf a photo of Steve Jobs. Oh, the humanity!
Qttask is (as the name implies) the taskbar process. Quicktime involves more than a taskbar icon.
The folder you zipped was probably the one containing Movie Player and suchlike. The libraries/extensions that handle MPEG decoding will have been installed wherever Windows usually keeps that type of thing.
Quicktime is Apple's multimedia framework. It's what iTunes uses to en/decode MP3 and AAC.
Yeah, and driving to work "just works" because of all the effort the road builders put in, not because of some fad called "a car".
Perhaps you don't understand. Rendezvous is a service discovery technology. It automatically finds machines on a network offering a service. Without Rendezvous, you'd have to find out the IP address yourself.
It really IS plug and play, in that as soon as I plug my iBook into a network, I show up on everyone's iChat Rendezvous list. Pretty smart, and much more than a 'fad' in my view.
Fire has an option to 'snap' to window edges. With this option turned on, attempting to move a Fire window beneath the Dock causes it to slide back to an uncovered position.
In other words, this most likely a feature of Fire rather than a bug with the Dock.
I don't think so; maybe they share the same graphics code but they certainly don't behave the same.
I can't think of any significant examples of this. If I click a button or pull down a menu the same thing happens in both a Carbon and a Cocoa application. Perhaps I'm missing something.
Unlike Macintosh, however, if you run something like KDE on X11, you really do get a single toolkit and a completely consistent user interface.
Correct me if I'm wrong, but I think you're comparing oranges and apples here. A better comparison would be Cocoa and KDE surely? After all, in KDE on Linux, OpenOffice has a complete different set of GUI features from, say, AbiWord.
There's nothing forcing a Mac OS X user to run Swing, Classic or X11 applications in the same way as there's nothing forcing a KDE user to run OO. Like you said in your initial post, the only way to ensure consistency is to use a consistent set of applications, and it seems that running KDE offers you no more help in that respect than Mac OS X does.
We *are* talking about the same Mac OS X? This is the OS where half of the UIs are brushed metal, and half are candy-cane-looking?
Well, yes. Brushed metal windows aren't drastically different from pinstripe windows. They still behave the same, and use the same widgets.
I'm not saying it's perfect; I'm just saying that most Mac OS X applications have a familiar feel the first time I start them up. It's easy to pick on the metal/pinstripe distinction, and I'm not convinced with Apple's reasoning for introducing this second theme. But whatever the reasons, it's been implemented in a way that doesn't damage consistency as much as it could have done.
When I look at the alternatives, this transgression seems reasonably minor.
Apple is even worse, officially supporting OS 9, Carbon, Swing, and Cocoa-based applications on the same desktop, and now also X11; and in addition to all that, toolkits like Gtk+, FLTK, Swing are also being ported to native Quartz backends.
To be fair, Carbon and Cocoa applications use the same standard widgets, and the Aqua look-and-feel for Swing is pretty consistent (bar the per-window menus). X11 windows behave like regular Aqua windows, even if the contents are down to the X toolkit.
In fact, I've found that Mac OS X is the most consistent desktop environment I've used. Obviously programmers will do as they please, but I think Apple has done a good job in making it easy to put together an application that looks and behaves as users are used to.
A user with a Mac, who can't even use Kazaa, and who has never shared music
... and probably will never touch the Internet again for fear of another army of lawyers barging her door down.
Unless you host your own webserver, initially uploading enough of your files to make your site useful to downloaders would take far too long and be far too costly in terms of bandwidth.
With a P2P application you make your entire library of files available to the network with practially no setup.
This makes HTTP sharing pretty useless to anyone who can't/won't run their own webserver (which, I imagine, covers a large proportion of current P2P users).
The Bank of Ireland uses NT on their ATMs - I saw one hanging on the NT splash screen recently.
Certainly won't be using their ATMs again...
That rather depends on what sort of filesystem you use, surely. All the manufacturer needs to state is how many physical bytes their drive can hold. What done with that capacity afterwards is none of their concern, nor should it be.
SGR 1900+14ar flare?