The "zone" the control uses is set by the application hosting the control. IE is doing exactly what winamp is telling it to. This problem is all winamp.
That's fine -- nothing says you have to use those settings -- that IS why they're options after all. Doesn't change the fact that your machine is vulnerable until the patch is applied, and that the indication that your machine is potentially vulnerable in that configuration is correct.
Let's say for the sake of arguement you leave your computer on 24x7, but only use it once a week.
A patch comes out on Monday. Windows downloads it and shows you a dialog saying "a patch is ready to install." You don't use the compure until next Sunday. On Thursday, a worm comes out that exploits the flaw that the patch on Monday fixed. Your box just got own3d.
It doesn't matter if they were using it for a public email service or not. Do you think that the 'winner' of the application process defaults to those working on a public email service?
It also doesn't matter what the name means to people you know. It doesn't matter what the name means to what the average person knows either. All that matters is who's first to use it.
The fact that at least one of the applicants further up in the queue deals with "mail" (newsletter sent by snail mail) is sufficient to put them in the same category as google's gmail.
Google has no case. Their only option is to buy the mark from the person who is awarded it.
If your employer doesn't pay for benefits, you have to pay them. And seldom can you find things like health insurance at a better pricepoint than a large company. Comparing the two side by side, the contractor comes out negative.
I suppose you've forgotten the "look and feel" lawsuits, from back in the day? They felt that any operating system which had GUI with the same features as MacOS violated their "look and feel".
They lost their case against Microsoft, but won it against other companies. For example, GEM for the PC had to remove the ability to have overlapping windows on the screen.
Functionality in GEM for the PC was greatly reduced over what was present in the Atari version. Apple sued over the 'look and feel' (and won), which resulted in many bits of crippled functionality (like not allowing windows to overlap). Oddly enough, Apple never sued Atari for the version of GEM they used in TOS...
The ST was an awesome machine. Very fond memories of that machine.
Yes, a raid0 array is slighly slower when accessing small files or randomly seeking across the disk. A raid0 array is also significantly faster when accessing large/sequential files on the disk.
Now, when you're accessing a small file, what are you doing? Typically you're doing something that you expect to take very little time -- such as opening or saving something. Is the few percentage points difference on a 200k file noticable? Not to me. Hell, everything seems to open pretty much instantly these days.
Now, when you're accessing a large file, what are you doing? You're doing something that often warrants a bathroom break or a cup of coffee. You're expecting to wait, and to be bored while doing so. Now, the few percentage points here DO make a difference. And the difference with a raid0 array is more than just a few percentage points.
Overall, you generally don't see the impact with small/random files, and you do notice the impact when dealing with large files. It's a net win.
Anything which generally decreases the amount of time you spend waiting on the computer is a good thing. A raid0 array definately decreases it.
If the pair of 10k rpm drives doesn't see an improvement because the raid controller is shoving bits arsound at it's limit, and a 7.2k rpm drives aren't pushing that controller to the limit, there would be a difference.
Not everyone who puts together a raid array is going for maximum performance. Most people go for best bang for the buck.
Unfortunately, this technique violates Eolas's patents regarding running code in a browser downloaded from an external source with a seamless user experience...
Once upon a time, while I was back in college, I could get a ^H character every time I hit the backspace key when I was telneting into certain machines (as opposed to deleting the previous character). Highly annoying. I suspect this is the 'origin' that you're looking for.
Actually, with all of the UI being rendered on the 3d card, you'll have more cycles for your dnet client, not less. This isn't complicated 3d geometry we're talking about here -- just simple rendering that will go one hell of a lot faster than bitblting and clipping rectangles...
It isn't their fiduciary duty to make the stock price rise - as other people have amplely pointed out, the $3/share divident reduces the stock price of the company. The closest analogy is that their duty is to produce a return on their investor's investment.
I've got an 'el cheapo "free with a contract" Nokia phone. I've dropped it on carpet. I've dropped it on concrete. I've dropped it on gravel. I've sat on it funny in my car. I've yanked it out of my pocket by catching the handfree set on a chair and sent it flying into the fireplace mantle, then on the brick on the floor. The case looks a bit worse for the wear on the corners, but the phone itself works just fine.
Yeah, because there is nothing better than patching a critical vulnerability on your computer and not having it take effect for 2 weeks because you didn't reboot your computer...
...is root@127.0.0.1 (or some variation therein). Alternatively, you can lookup email addresses for the site that demands an email address and use that...
Not to my knowledge. Though, if you think about it, any such worm would be rather unsuccessful -- how many people do you know that use pine, and know people that use pine as well? Any worm which tries to take advantage of the vulnerability is going to need to attack more than just Pine.
Employees are a true operating cost (expense) of a company. Playing bookkeeping games with how you pay them does not change the fact that they are a real operating cost.
Indeed. And when your cost involves the use of options, you only know that cost when the employee exercises the options.
Until that point, the cost is $0. I do believe it is useful information to disclose how many options are outstanding, but it's pointless to say that the 200 options you granted an employee this year cost $800, because 3 years down the road when the employee actually exercises the options it may really cost $2000, or $200. Under the proposed rules, nothing is reported when the employee exercise the options, and all you're left with is the supposed $800 cost of issue.
It is stupid to project the cost to the company before that cost is incurred.
Slashdot Mirror
The "zone" the control uses is set by the application hosting the control. IE is doing exactly what winamp is telling it to. This problem is all winamp.
Rrriggghhhttt...because copying 14gb of content over a USB connection should only take a few minutes ...
That's fine -- nothing says you have to use those settings -- that IS why they're options after all. Doesn't change the fact that your machine is vulnerable until the patch is applied, and that the indication that your machine is potentially vulnerable in that configuration is correct.
Let's say for the sake of arguement you leave your computer on 24x7, but only use it once a week.
A patch comes out on Monday. Windows downloads it and shows you a dialog saying "a patch is ready to install." You don't use the compure until next Sunday. On Thursday, a worm comes out that exploits the flaw that the patch on Monday fixed. Your box just got own3d.
It doesn't matter if they were using it for a public email service or not. Do you think that the 'winner' of the application process defaults to those working on a public email service?
It also doesn't matter what the name means to people you know. It doesn't matter what the name means to what the average person knows either. All that matters is who's first to use it.
The fact that at least one of the applicants further up in the queue deals with "mail" (newsletter sent by snail mail) is sufficient to put them in the same category as google's gmail.
Google has no case. Their only option is to buy the mark from the person who is awarded it.
If your employer doesn't pay for benefits, you have to pay them. And seldom can you find things like health insurance at a better pricepoint than a large company. Comparing the two side by side, the contractor comes out negative.
Timeline's patents cover using third-party software to build reporting databases which summarize data from multiple databases.
So it's somehow Microsoft's fault that Cognos built a system which infringed on Timeline's patents?
Because the Tramiel family couldn't sell water in the middle of a desert.
I suppose you've forgotten the "look and feel" lawsuits, from back in the day? They felt that any operating system which had GUI with the same features as MacOS violated their "look and feel".
They lost their case against Microsoft, but won it against other companies. For example, GEM for the PC had to remove the ability to have overlapping windows on the screen.
Functionality in GEM for the PC was greatly reduced over what was present in the Atari version. Apple sued over the 'look and feel' (and won), which resulted in many bits of crippled functionality (like not allowing windows to overlap). Oddly enough, Apple never sued Atari for the version of GEM they used in TOS ...
The ST was an awesome machine. Very fond memories of that machine.
Yes, a raid0 array is slighly slower when accessing small files or randomly seeking across the disk. A raid0 array is also significantly faster when accessing large/sequential files on the disk.
Now, when you're accessing a small file, what are you doing? Typically you're doing something that you expect to take very little time -- such as opening or saving something. Is the few percentage points difference on a 200k file noticable? Not to me. Hell, everything seems to open pretty much instantly these days.
Now, when you're accessing a large file, what are you doing? You're doing something that often warrants a bathroom break or a cup of coffee. You're expecting to wait, and to be bored while doing so. Now, the few percentage points here DO make a difference. And the difference with a raid0 array is more than just a few percentage points.
Overall, you generally don't see the impact with small/random files, and you do notice the impact when dealing with large files. It's a net win.
Anything which generally decreases the amount of time you spend waiting on the computer is a good thing. A raid0 array definately decreases it.
That would depend on where the bottleneck is at.
If the pair of 10k rpm drives doesn't see an improvement because the raid controller is shoving bits arsound at it's limit, and a 7.2k rpm drives aren't pushing that controller to the limit, there would be a difference.
Not everyone who puts together a raid array is going for maximum performance. Most people go for best bang for the buck.
Unfortunately, this technique violates Eolas's patents regarding running code in a browser downloaded from an external source with a seamless user experience...
104 wpm with 99% accuracy here. Guess that explains why the posting delay on slashdot annoys me so ...
Once upon a time, while I was back in college, I could get a ^H character every time I hit the backspace key when I was telneting into certain machines (as opposed to deleting the previous character). Highly annoying. I suspect this is the 'origin' that you're looking for.
Actually, with all of the UI being rendered on the 3d card, you'll have more cycles for your dnet client, not less. This isn't complicated 3d geometry we're talking about here -- just simple rendering that will go one hell of a lot faster than bitblting and clipping rectangles...
Right, you won't be wasting that $400 video card you just bought to play Doom III while you're surfing the web...
If your cpu utilization isn't at 100%, you aren't wasting anything except electricity.
It isn't their fiduciary duty to make the stock price rise - as other people have amplely pointed out, the $3/share divident reduces the stock price of the company. The closest analogy is that their duty is to produce a return on their investor's investment.
The median age of a Microsoft employee in 2000 was 34.
I've got an 'el cheapo "free with a contract" Nokia phone. I've dropped it on carpet. I've dropped it on concrete. I've dropped it on gravel. I've sat on it funny in my car. I've yanked it out of my pocket by catching the handfree set on a chair and sent it flying into the fireplace mantle, then on the brick on the floor. The case looks a bit worse for the wear on the corners, but the phone itself works just fine.
Yeah, because there is nothing better than patching a critical vulnerability on your computer and not having it take effect for 2 weeks because you didn't reboot your computer ...
SpyGlass received a minimum quarterly payment of $400,000. Their 'interests' in IE were bought out in '98 for $8 million.
That's a far cry from $0.
...is root@127.0.0.1 (or some variation therein). Alternatively, you can lookup email addresses for the site that demands an email address and use that ...
Not to my knowledge. Though, if you think about it, any such worm would be rather unsuccessful -- how many people do you know that use pine, and know people that use pine as well? Any worm which tries to take advantage of the vulnerability is going to need to attack more than just Pine.
Employees are a true operating cost (expense) of a company. Playing bookkeeping games with how you pay them does not change the fact that they are a real operating cost.
Indeed. And when your cost involves the use of options, you only know that cost when the employee exercises the options.
Until that point, the cost is $0. I do believe it is useful information to disclose how many options are outstanding, but it's pointless to say that the 200 options you granted an employee this year cost $800, because 3 years down the road when the employee actually exercises the options it may really cost $2000, or $200. Under the proposed rules, nothing is reported when the employee exercise the options, and all you're left with is the supposed $800 cost of issue.
It is stupid to project the cost to the company before that cost is incurred.