It does, but only for HTTP auth passwords, not passwords you enter into a CGI form.
doesn't show the link when mouseover
Turn on the status bar. (Hint: cool stuff can be found under the View menu.)
the metalic look is no good, but it's more of a personal perference and it's minor.
You can turn it off if it really means that much to you. See other posts for the NIB trick.
auto complete of url is not as convinent as chimera. typing www.apple goes nowhere.
Use the same number of keystrokes and type "apple.com."
all downloads goes to the download folder, saving to other places is not even an option
Yes, but dragging-and-dropping from your downloads folder is. Quicker and easier, too.
so what should i do with all these files in the download folder? clean them up from time to time?
Not to put it bluntly, but yes. Keeping your own folders clean is still something you have to do manually.
snapback? give me a break. it's just one of the tiny feature on the google toolbar.
SnapBack works any time you type a URL into the address bar. You can also invoke it at any time by using the "Mark page for SnapBack" item under the History menu, or typing command-option-M.
Command-tilde works in any application that uses AppKit, I believe. I think it's yet another free feature that comes with using the Cocoa API. I'm not sure if Carbon apps get it for free, or if they have to implement it themselves.
To test this, I fired up Project Builder and created a new Cocoa document application. I didn't do anything, I just built and ran the new app. I opened a couple of windows, and command-tilde switched between them. So it's a feature that you get for free when you use Cocoa and AppKit.
Are you kidding? I've used IE on both Mac and Windows, and have to say that the Mac version is much better
Then IE for Windows must suck. IE for OS 9 was pretty darned good, but IE for OS X is chiseled spam. It frequently fails to load pages correctly-- or at all-- and spins off into never-never land for no apparent reason. Not to mention being slow, slow, even on a fast dual-processor machine.
IE for OS 9 was the best browser of its day. IE for OS X is an unqualified disaster.
I'm pretty sure the charts used in the keynote address included comparisons to OmniWeb as well (Safari was faster). And they didn't include Opera because, well, only about six people use it.
Omniweb has GREAT window handling, superb bookmarks and - apparently - better Slashdot compatibility that Safari...
I've been using Safari on Slashdot all day now. Before this morning, I was using OmniWeb full time. Apart from speed and the fact that "check spelling as you type" is on by default in OmniWeb, I can't tell the difference. What are you referring to?
With tabs, closing a window can in fact remove the contents of many windows.
Finally! Somebody who gets it! Tabbed browsing rubs me the wrong way for this very reason. No other application uses the multiple-data-sources-in-one-window approach; having your browser do it makes for frustration and confusion.
I would guess that the license came into it at some point as well. KHTML uses the relatively benign LGPL, while Gecko is licensed under the more entangling NPL.
Since all nodes have to communicate over the NUMA link anyway I expect the performance difference isn't that great between memory from one system image and memory from different system images.
The difference is huge. NUMAlink 3 runs at 3.2 GB/s. NUMAlink 4 (used in the 3300 today, and the 3700 soon) runs at 6.4 GB/s. There's no cluster interconnect that can even remotely approach those raw speeds. And latency is... well, I forget the figures, but it's incredibly small.
Look up MPI or OpenMP. These systems do not share memory like you would in your dual proccessor workstation.
Actually, these systems do share memory, just like you would in your dual processor workstation. You can configure an Altix system with up to 64 processors (today) in a single system image, not as a cluster. (Why SGI decided to call the 3700 a "supercluster" is beyond me. It's not a cluster at all, super or otherwise.) You can run as many threads on as many processors as you like within a single virtual address space.
Just to be clear, you do not have to use MPI or any other message-passing technology on this system.
How much of it are you familiar with? Do you know the stories of Adam and Eve, Moses, Abraham and Isaac, Noah, Job, the birth and death of Jesus, the life of St. Paul? For a book that we're only exposed to for "trivial amounts of time," it sure is universally known, huh?
It's invalid to criticise this aspect of life because it's an aspect of life.
Not exactly, but close. I'm saying that it's invalid to criticize television on grounds that it is not a legitimate part of our culture.
Maintaining a sharp and healthy mind is a proactive task. Television is like eating twinkies.
Bah. Television is what you make of it. You can sit and watch passively, or you can consider and reflect and discuss just as with any other medium. And, of course, the occasional twinkie never hurt anybody. All things in moderation.
you WOULD have a point, excepting that EVERy Tv post environment is based on SIF, and dual link SIF for HD.
First of all, dual-link is only necessary for 4:4:4, like from a telecine. SMPTE 292 specifies full-bandwidth 4:2:2 HD over a single coaxial connection. That's what people who do HD over SDI use.
But it's not exactly true that every TV environment is built on SDI. You'd be absolutely amazed how many component analog houses are still going strong.
And converters that go from SMPTE 259M or SMPTE 292M to FireWire are trivial and inexpensive, and require no real logic whatsoever, unlike PCI video I/O boards. The net result is better software compatibility (because your application only has to talk to FireWire over IOKit, instead of a PCI card with its own driver) and better picture quality (because you're not processing the signal in any way).
When using both on my Powerbook they don't interfere at all
The interference problems between Bluetooth and AirPort are well document (try Macintouch) although I haven't experienced them myself either. Putting the electronics on the same PCB would certainly exacerbate the problem.
Personally I would prefer the bluetooth trinket to be integrated to the computer and not stick out if possible, especially as the back cover is so fragile.
Sure, integrate away. Just don't put it on the AirPort card.
Of course the same folks who are doing HDTV styled video feeds are also the ones who need a lot more processing power than the G4 offers.
Nope. The G4 is a great machine to do either off-lining, or finishing of HD material. All you need is video I/O, and FireWire 800 will (hopefully!) provide that in spades.
Yup. Those three links all refer to fonts displayed on computers running Windows or Mac OS 9. Neither Windows nor OS 9 could antialias fonts worth a damn.
And it's not like computer components can be and are reduced in size over time... what was I thinking.
Well, actually, yeah. What were you thinking?
Miniaturization is not the important detail here; it's significant, but not discussion-ending. Bluetooth is neat. AirPort is neat. They don't depend on each other, at all, so there's no reason to build them into the same card. And most importantly, they actually interfere, to a very serious degree, with each other. So putting them together in the same device would be, in a word, dumb.
Beg to differ. If you find a sans-serif font to be easier to read than a serif font, it may be because the serif font is poorly designed, your font renderer isn't doing its job properly, or your antialiasing algorithm is fundamentally broken. (Note that most antialiasing algorithms are fundamentally broken because they use integer math instead of floating-point math.)
In other words, if you don't think serif fonts are easier to read, then something's broken in your software.
Well, you kinda hit the nail right on the head already. FireWire was designed in part to carry standard-definition video in DV format with the DV, DVCPRO, or DVCAM codecs. These codecs compress the video from 270 Mbps down to 25 Mbps, which can easily fit inside FireWire's 400 Mbps bandwidth.
Panasonic has a DVCPRO-HD codec that compressed HD from more than 1.3 Gbps down to 100 Mbps. While you could, in theory, do 100 Mbps isochronously over FireWire 400, it'd be a lot easier over FireWire 800.
People who use FireWire exclusively to talk to external storage devices and iPods (like most of us, including myself) don't need FireWire 800 right now. But people who do video with it most certainly do, and the trickle-down effect will benefit the rest of us, I think.
Really, what is so "dumb" about integrating two, currently separate technologies, into one simple card?
Lots of things. First and most importantly, Apple doesn't make AirPort cards. They buy them from (I think) Lucent. Second, pop open an AirPort card and tell me how much space you see. Third, even if you could squeeze the electronics into the PC card form factor, you'd have massive EM interference problems, because AirPort and Bluetooth broadcast in the same frequency band. Fourth, AirPort cards are buried deep inside the computer, so there would have to be some kind of Bluetooth antenna built into the computer anyway, just like the AirPort antenna.
I could go on, but I imagine that you're getting the idea here.
Second. I'm using Georgia as my regular font-- serifs beat the pants off of sans-serifs any day, plus I love old style figures-- and Courier as my monospaced font. They look great.
Then again, I'm also using OmniWeb on OS X, so your mileage may end up sucking because X11's antialiasing looks like chiseled spam.
a small thumb sticking out of the back of a Powerbook G4, that wont fit in cases unless you take it out, and has a high chance of being broken off.
First, if you're whacking your laptop around so much that you're afraid the Bluetooth adapter would be broken off, then you've got serious lifestyle issues. Pull the damn thing out and stick it in your pocket!
But the point was that Bluetooth + AirPort is a dumb idea. Integrating Bluetooth into laptops is a good idea. Integrating Bluetooth into monitors is a good idea. (Dumb to integrate it into G4 towers; they're rarely anywhere near the monitor and keyboard anyway.) Integrating Bluetooth into an AirPort card? Dumb.
Slashdot Mirror
has no keychain support
It does, but only for HTTP auth passwords, not passwords you enter into a CGI form.
doesn't show the link when mouseover
Turn on the status bar. (Hint: cool stuff can be found under the View menu.)
the metalic look is no good, but it's more of a personal perference and it's minor.
You can turn it off if it really means that much to you. See other posts for the NIB trick.
auto complete of url is not as convinent as chimera. typing www.apple goes nowhere.
Use the same number of keystrokes and type "apple.com."
all downloads goes to the download folder, saving to other places is not even an option
Yes, but dragging-and-dropping from your downloads folder is. Quicker and easier, too.
so what should i do with all these files in the download folder? clean them up from time to time?
Not to put it bluntly, but yes. Keeping your own folders clean is still something you have to do manually.
snapback? give me a break. it's just one of the tiny feature on the google toolbar.
SnapBack works any time you type a URL into the address bar. You can also invoke it at any time by using the "Mark page for SnapBack" item under the History menu, or typing command-option-M.
Command-tilde works in any application that uses AppKit, I believe. I think it's yet another free feature that comes with using the Cocoa API. I'm not sure if Carbon apps get it for free, or if they have to implement it themselves.
To test this, I fired up Project Builder and created a new Cocoa document application. I didn't do anything, I just built and ran the new app. I opened a couple of windows, and command-tilde switched between them. So it's a feature that you get for free when you use Cocoa and AppKit.
Are you kidding? I've used IE on both Mac and Windows, and have to say that the Mac version is much better
Then IE for Windows must suck. IE for OS 9 was pretty darned good, but IE for OS X is chiseled spam. It frequently fails to load pages correctly-- or at all-- and spins off into never-never land for no apparent reason. Not to mention being slow, slow, even on a fast dual-processor machine.
IE for OS 9 was the best browser of its day. IE for OS X is an unqualified disaster.
I'm pretty sure the charts used in the keynote address included comparisons to OmniWeb as well (Safari was faster). And they didn't include Opera because, well, only about six people use it.
Omniweb has GREAT window handling, superb bookmarks and - apparently - better Slashdot compatibility that Safari...
I've been using Safari on Slashdot all day now. Before this morning, I was using OmniWeb full time. Apart from speed and the fact that "check spelling as you type" is on by default in OmniWeb, I can't tell the difference. What are you referring to?
With tabs, closing a window can in fact remove the contents of many windows.
Finally! Somebody who gets it! Tabbed browsing rubs me the wrong way for this very reason. No other application uses the multiple-data-sources-in-one-window approach; having your browser do it makes for frustration and confusion.
Note well that only Webcore is open source. Safari, which is the browser application itself, is most definitely not.
I would guess that the license came into it at some point as well. KHTML uses the relatively benign LGPL, while Gecko is licensed under the more entangling NPL.
Since all nodes have to communicate over the NUMA link anyway I expect the performance difference isn't that great between memory from one system image and memory from different system images.
The difference is huge. NUMAlink 3 runs at 3.2 GB/s. NUMAlink 4 (used in the 3300 today, and the 3700 soon) runs at 6.4 GB/s. There's no cluster interconnect that can even remotely approach those raw speeds. And latency is... well, I forget the figures, but it's incredibly small.
Look up MPI or OpenMP. These systems do not share memory like you would in your dual proccessor workstation.
Actually, these systems do share memory, just like you would in your dual processor workstation. You can configure an Altix system with up to 64 processors (today) in a single system image, not as a cluster. (Why SGI decided to call the 3700 a "supercluster" is beyond me. It's not a cluster at all, super or otherwise.) You can run as many threads on as many processors as you like within a single virtual address space.
Just to be clear, you do not have to use MPI or any other message-passing technology on this system.
How often do you read the bible?
How much of it are you familiar with? Do you know the stories of Adam and Eve, Moses, Abraham and Isaac, Noah, Job, the birth and death of Jesus, the life of St. Paul? For a book that we're only exposed to for "trivial amounts of time," it sure is universally known, huh?
It's invalid to criticise this aspect of life because it's an aspect of life.
Not exactly, but close. I'm saying that it's invalid to criticize television on grounds that it is not a legitimate part of our culture.
Maintaining a sharp and healthy mind is a proactive task. Television is like eating twinkies.
Bah. Television is what you make of it. You can sit and watch passively, or you can consider and reflect and discuss just as with any other medium. And, of course, the occasional twinkie never hurt anybody. All things in moderation.
you WOULD have a point, excepting that EVERy Tv post environment is based on SIF, and dual link SIF for HD.
First of all, dual-link is only necessary for 4:4:4, like from a telecine. SMPTE 292 specifies full-bandwidth 4:2:2 HD over a single coaxial connection. That's what people who do HD over SDI use.
But it's not exactly true that every TV environment is built on SDI. You'd be absolutely amazed how many component analog houses are still going strong.
And converters that go from SMPTE 259M or SMPTE 292M to FireWire are trivial and inexpensive, and require no real logic whatsoever, unlike PCI video I/O boards. The net result is better software compatibility (because your application only has to talk to FireWire over IOKit, instead of a PCI card with its own driver) and better picture quality (because you're not processing the signal in any way).
When using both on my Powerbook they don't interfere at all
The interference problems between Bluetooth and AirPort are well document (try Macintouch) although I haven't experienced them myself either. Putting the electronics on the same PCB would certainly exacerbate the problem.
Personally I would prefer the bluetooth trinket to be integrated to the computer and not stick out if possible, especially as the back cover is so fragile.
Sure, integrate away. Just don't put it on the AirPort card.
Why do they price them so that "the rest of us" can't afford them?
;-)
Wrong "rest of us."
They don't do such a good job of turning that want into sales, though.
Really? $143 million in sales in six months seems to indicate otherwise. (Apple's 10-K is always a fascinating read.)
Of course the same folks who are doing HDTV styled video feeds are also the ones who need a lot more processing power than the G4 offers.
Nope. The G4 is a great machine to do either off-lining, or finishing of HD material. All you need is video I/O, and FireWire 800 will (hopefully!) provide that in spades.
Yup. Those three links all refer to fonts displayed on computers running Windows or Mac OS 9. Neither Windows nor OS 9 could antialias fonts worth a damn.
And it's not like computer components can be and are reduced in size over time... what was I thinking.
Well, actually, yeah. What were you thinking?
Miniaturization is not the important detail here; it's significant, but not discussion-ending. Bluetooth is neat. AirPort is neat. They don't depend on each other, at all, so there's no reason to build them into the same card. And most importantly, they actually interfere, to a very serious degree, with each other. So putting them together in the same device would be, in a word, dumb.
Beg to differ. If you find a sans-serif font to be easier to read than a serif font, it may be because the serif font is poorly designed, your font renderer isn't doing its job properly, or your antialiasing algorithm is fundamentally broken. (Note that most antialiasing algorithms are fundamentally broken because they use integer math instead of floating-point math.)
In other words, if you don't think serif fonts are easier to read, then something's broken in your software.
For practical purposes Firewire is good enough.
Well, you kinda hit the nail right on the head already. FireWire was designed in part to carry standard-definition video in DV format with the DV, DVCPRO, or DVCAM codecs. These codecs compress the video from 270 Mbps down to 25 Mbps, which can easily fit inside FireWire's 400 Mbps bandwidth.
Panasonic has a DVCPRO-HD codec that compressed HD from more than 1.3 Gbps down to 100 Mbps. While you could, in theory, do 100 Mbps isochronously over FireWire 400, it'd be a lot easier over FireWire 800.
People who use FireWire exclusively to talk to external storage devices and iPods (like most of us, including myself) don't need FireWire 800 right now. But people who do video with it most certainly do, and the trickle-down effect will benefit the rest of us, I think.
Really, what is so "dumb" about integrating two, currently separate technologies, into one simple card?
Lots of things. First and most importantly, Apple doesn't make AirPort cards. They buy them from (I think) Lucent. Second, pop open an AirPort card and tell me how much space you see. Third, even if you could squeeze the electronics into the PC card form factor, you'd have massive EM interference problems, because AirPort and Bluetooth broadcast in the same frequency band. Fourth, AirPort cards are buried deep inside the computer, so there would have to be some kind of Bluetooth antenna built into the computer anyway, just like the AirPort antenna.
I could go on, but I imagine that you're getting the idea here.
Dongles suck dirty goat balls.
You should be ashamed of yourself.
Default fonts are usually serif, which have readability problems at small size
You have that backwards. Serif fonts are far more readable at small sizes than sans serif fonts.
Second. I'm using Georgia as my regular font-- serifs beat the pants off of sans-serifs any day, plus I love old style figures-- and Courier as my monospaced font. They look great.
Then again, I'm also using OmniWeb on OS X, so your mileage may end up sucking because X11's antialiasing looks like chiseled spam.
Hee hee. Good one, Rocky.
a small thumb sticking out of the back of a Powerbook G4, that wont fit in cases unless you take it out, and has a high chance of being broken off.
First, if you're whacking your laptop around so much that you're afraid the Bluetooth adapter would be broken off, then you've got serious lifestyle issues. Pull the damn thing out and stick it in your pocket!
But the point was that Bluetooth + AirPort is a dumb idea. Integrating Bluetooth into laptops is a good idea. Integrating Bluetooth into monitors is a good idea. (Dumb to integrate it into G4 towers; they're rarely anywhere near the monitor and keyboard anyway.) Integrating Bluetooth into an AirPort card? Dumb.