Somehow, I just *knew* this was coming. ;)

Just like they couldn't anticipate the Slashdotting they were about to receive...

The anticipation is killing me .

If only kerneltrap.org were running the new schedu... oh, never mind.

Seems to be slashdotted already... Wonder if it saw that coming.

Man, they should've just anticipated the coming Slashdotting and used it as a real-life benchmark for the scheduler...

In some cases, the new Anticipatory Scheduler performs several times better than the others, doing a task in a few seconds instead minutes like the others.

The task in question was anticipating things, so the test might not be all that fair.

> Mac OS X: because making Unix user-friendly is easier than debugging Windows.

Heh. More like "because making user-friendly Unix is easier than making unix-sturdy MacOS".

It reminds of the old song and Heinz Ketchup commercial:
"Anticipation is making me wait"...

"with the 2.4's scheduler as a reference poin."

I'm still anticipating the "t" in "point" myself...

Too many connections

Too many connections

You know, you can ALMOST feel an admin over there just itching to type in "Fuck you Taco! And your site!" instead of the connection stuff...

Me: Computer, I would like to open Netscape
Computer: I have anticipated you would like to open IE and have already opened it for you.
Me: Ok, then I would like to go to the game review site to see what I want to buy.
Computer: I have already begun the download of the new Age of Empires game, your account has been charged.
Me: Can I at least go to the bathroom?
Computer: No.

It's a trap! We've got to give this website more time. Concentrate all firepower on the next article below!
/ackbar

... the Mozilla developers added a special "Slashdotted" plugin you know. So you could launch a special tab that would keep hammering away at a site in the background until it did bloodywell load ;-)

Somehow, I just *knew* this was coming. ;)

Ah, grasshopper, but did you know it will be coming to Slashdot yet again in a day or so? Anyone can predict the future; it takes a sage to predict a Slashdot duplicate.

Quoeth the driver:

* These chips are basically fucked by design, and getting this driver
* to work on every motherboard design that uses this screwed chip seems
* bloody well impossible. However, we're still trying.

Me: I would like to upda...
Computer: I have already run auto update. all your warez are belong to us.

which would fit into one two categories: 1. solution for already solved problem, 2. killer feature.

yea no shit.

that's definitely +5 MOC

(moderator on crack)

I see you shiver with antici - - - - (Say it!) - - - (Consti!) - - - pation!

;-)

For sure this is also a bit due to the new VM code.

Fer sure.

It should anticipate the slashdot effect and teleport 3 new servers into the room, and mirror the website onto them and install a load balencer.

Or maybe it should just say "There have been 2000 slashdot whores here in the last 10 seconds, I anticipate your one too, so LEAVE NOW!"

Don't you think mozilla is bloated enough already? If they added that, then they might as well just go ahead and include a kitchen si... wait... err... nevermind.

I totally agree, but do find it sad that Apple spent all the time and effort only to find that creating an OS was beyond them, so they chucked it all out and went for Unix. And Unix had been there for them all along.

C'mon, try grounding your trolling in reality next time. Scheduling on OSX is handled by Mach [apple.com], which was developed at CMU by Avi Tevanian [apple.com], developed at NeXT and brought up to 3.0 at Apple.

Apple uses BSD for its UNIX compatibilty layer, but that doesn't handle scheduling, which is what this article is about.

Now, if you want to say Apple was dumb for chucking A/UX [faqs.org] in the early nineties, then that'd make a much better troll.

While I have seen some voices of dissent that the test isn't fair, I'm afriad I don't understand what you mean here. Could you please explain further?

Actually I was making a joke (that the benchmarking task itself was what the act of anticipating things, which this tool would obviously have a one up on... ). But someone modded me up insightful, so maybe I'm on to something.

It'd be like testing rice painted white in a glass of milk during a snowstorm in a whiteness contest.

Funny though... on my screen the first thing my brain interpreted that to: 'reference porn'

I think i need help...

How about a game where each little unit runs its own thread? 400 tanks crawling all over the battlefield would be 400 threads.

iptables: "Httpd, we've lost our port 80 packet deflectors"
httpd: "Intensify the firewall, I don't want anything to get through."
iptables: "Httpd, look!"
httpd: "INTENSIFY THE FIREWALL!"
iptables: "Too late!"

Is this a new virus or clever marketing scheme?

Either way... (loading double-barreled shotgun)

(credit to Dilbert/Scott Adams)

Heh, an anticipatory CPU scheduler! "Yup, gcc wanted more time."

A viscous circle, no?