One problem that the third umpire had at the moment is that he can't use multiple angles at once. If the video feeds were timestamped (or even better synchronised) and they could be viewed concurrently, a lot of run-out decisions would be made easier. (ie one angle shows the bales, while another shows the crease.)
It would be cool, though, to see a diving Mark Waugh catch in bullet time, although the focal point in cricket moves around faster than in NFL so the robotics would need to be quicker.
And while we're getting completely tangential, I've sometimes though about the possibilities of having an spatial array of microphones recording, so that a DSP directional mike effect could be extracted later... might have solved the "can't bowl, can't throw" problem sooner.
Good to see cricket discussion on./, my two biggest time wasters, together at last:)
They dropped CS307? I must have been in the last bunch through. IIRC, it used Minix for the final two assignments, on top of which we had to implement some syscalls, and write a shell. It was a pretty good subject.
I just finished an embedded systems subject that used uCOS/ii, a little RTOS, to make a network "phone".
I bought a Saitek P2000 Tilt Pad three weeks ago. One day later, I bought another one.
I was very impressed. It has an analog stick very like the Playstation pad, 2-axis tilt (okay, I don't use it much but feels damn cool in GP3), throttle, d-pad, 4 shoulder buttons, 4 regular buttons and some funky software.
The buttons don't quite have the same satisfying "push me" quality as those on a N64 or PSX pad, but they're close.
All this for AU$65.
Game pads are a must-have for multi-player sports games. A keyboard is pretty cramped even with one player:)
IGN has some nive piccys that convey the size of the controller, console, and the mini-DVDs.
I trust Nintendo / Miyamoto when it comes to controller design. Now if only they made PC peripherals... Maybe I should invest in a N64 pad to USB converter...
As a casual gamer, I'm hanging out for the cube much more than X-box or PS2. Gimme another Mario Kart, and watch me waste another year or two of my life:)
IPP is built on top of HTTP, which in turn runs over TCP/IP. IPP traffic is sent as a Multi-purpose Internet Mail Extensions-type using HTTP's feature for posting information. End users submit a print request using a command in the browser address line that starts with "ipp:\\" rather than "http:\\."
Oops, hope the backslashes don't make there way into the protocol:)
A lot of good ideas for this are impractical because of server load, and the logistics involved with tinkering with slashdot too much.
I wonder if a client side filter might be appropriate? If you have sufficient bandwidth to download the autoposts, and enough cycles to burn, a little extra javascript could conditionally block posts.
The simplest way to start would be to implement a kill-list for certain users. Won't help the AC posts, but that's okay if you don't mind browsing at +1 (which doesn't sit that well with me.)
Maybe a more advanced model would be third-party moderation. Submit the useless cids to a repository, and filter based on that. It seems that a one-size fits all./ ends up fitting nobody.
Of course, a 3rd party mod system could filter for you, but if its done client side, it might not be as legally prickly.
Go back to the page (you have glanced at it, haven't you?) and do your own eye-tracking experiment. Looks like a fair bit of thought has gone into the frameset (although it has been critisised below.
The content loads first, and its unusual positioning grabs your eye. I read a paragraph or two, until I headed to the innocuous grey caption -- before I noticed the picture with the cyborg style eye tracker. The TOC doesn't load until clicked, presumably to lead you into the introduction without distractions. Oh, there was a logo up in the corner.
While their results were about news sites, the principles are pretty well demonstrated on there site. Like the site or not, it seems to re-enforce their findings (coincidence? I think not.)
Of course, given a particular browser choice, bandwith, and individual makeup, YMMV.
Well as well as fattening the pipes (and, hence, the "valves"), we can always lay down more of them.
If the world travels down a purely client/server model (read: dot net... well, not quite) the bandwitdth requirements grow _very_ quickly. Go down a distributed path, and local traffic stays local, and the network grows strong:)
Seems like the latter path is more sustainable, and more elegant.
What does this spell out for the power struggles between Tom and Jerry, Itchy and Scratchy, Mighty Mouse and assorted bad guys, Danger Mouse and Baron Greenback (not a cat, but probably in the same union)?
Please add to the list. Those damn cartoon mice get away with murder.
Convergence is one buzzword that seems to always hang around, but never deliver. Convergence for convergence's sake isn't necessarily what the market wants. Its kinda cool from an engineering standpoint, but Joe Average needs to understand a product before he will buy it. He understands a VCR. It plays videos, and alllows him to record his own. Does he understand a Tivo/Dreamcast/Email/can opener?
(Granted, console makers can get him to buy one with a loss-leader price point, but that's not really my point)
This is what I like about Nintendo's next-gen strategy. They're making a games machine. To play games on. Period.
The panacea, to my mind, is multiple dedicated devices that can spontaneously network. (think Jini, or Universal Plug'n'P[lr]ay.. shudder). Once these standards mature, the all-in-wunderbox might seem a little "early nineties".
The new 7200 rpm drives are still physically read slower that 33 MB/s......but ATA/66 will speed up data that is fetched from the hard drives cache. There was a good article on anandtech recently on ATA 33 vs ATA 66 zaugg (.sig to be released "when it's done!")
It seems that every UI that I "U" with, is a matter of compromise. This is, as I see it, due to the incredibly limited feedback that the UI processes. When I use a new command line tool, I curse the learning curve. But once I've invested the time to learn the switches, I relish the power. So how can the UI know my level of knowledge, my goals, and what I'm thinking about? ((un)intellisense is a half-assed attempt to solve this. I believe that once that UI might be the next computer revolution: our 3d cards can render more polygons than most users could possibly care about every second, and we are networking with fatter pipes? UIs that intelligently process user feedback are next. just my 2c, zaugg.
Slashdot Mirror
It would be cool, though, to see a diving Mark Waugh catch in bullet time, although the focal point in cricket moves around faster than in NFL so the robotics would need to be quicker.
And while we're getting completely tangential, I've sometimes though about the possibilities of having an spatial array of microphones recording, so that a DSP directional mike effect could be extracted later... might have solved the "can't bowl, can't throw" problem sooner.
Good to see cricket discussion on ./, my two biggest time wasters, together at last :)
--zaugg
I just finished an embedded systems subject that used uCOS/ii, a little RTOS, to make a network "phone".
--zaugg
I was very impressed. It has an analog stick very like the Playstation pad, 2-axis tilt (okay, I don't use it much but feels damn cool in GP3), throttle, d-pad, 4 shoulder buttons, 4 regular buttons and some funky software.
The buttons don't quite have the same satisfying "push me" quality as those on a N64 or PSX pad, but they're close.
All this for AU$65.
Game pads are a must-have for multi-player sports games. A keyboard is pretty cramped even with one player :)
--zaugg
I trust Nintendo / Miyamoto when it comes to controller design. Now if only they made PC peripherals... Maybe I should invest in a N64 pad to USB converter...
As a casual gamer, I'm hanging out for the cube much more than X-box or PS2. Gimme another Mario Kart, and watch me waste another year or two of my life :)
--zaugg
These kinda shortcuts make life a little more bearable.
C:\Documents and Settings
cd doc*set*
C:\Temporary Interenet Files
cd temp*int*
C:\System Volume Information
cd sys*inf
C:\Downloaded Program Files
cd down*file
--zaugg
Then you get a running total of credit / debt among the house (it makes for an interesting graph.)
DISCLAIMER: probably won't work if someone is an arsehole.
--zaugg
Oops, hope the backslashes don't make there way into the protocol :)
zaugg
I wonder if a client side filter might be appropriate? If you have sufficient bandwidth to download the autoposts, and enough cycles to burn, a little extra javascript could conditionally block posts.
The simplest way to start would be to implement a kill-list for certain users. Won't help the AC posts, but that's okay if you don't mind browsing at +1 (which doesn't sit that well with me.)
Maybe a more advanced model would be third-party moderation. Submit the useless cids to a repository, and filter based on that. It seems that a one-size fits all ./ ends up fitting nobody.
Of course, a 3rd party mod system could filter for you, but if its done client side, it might not be as legally prickly.
Just some thoughts.
zaugg
The content loads first, and its unusual positioning grabs your eye. I read a paragraph or two, until I headed to the innocuous grey caption -- before I noticed the picture with the cyborg style eye tracker. The TOC doesn't load until clicked, presumably to lead you into the introduction without distractions. Oh, there was a logo up in the corner.
While their results were about news sites, the principles are pretty well demonstrated on there site. Like the site or not, it seems to re-enforce their findings (coincidence? I think not.)
Of course, given a particular browser choice, bandwith, and individual makeup, YMMV.
zaugg
If the world travels down a purely client/server model (read: dot net... well, not quite) the bandwitdth requirements grow _very_ quickly. Go down a distributed path, and local traffic stays local, and the network grows strong :)
Seems like the latter path is more sustainable, and more elegant.
zaugg
:)
zaugg
It doesn't guarantee the comments are his, of course.
I'm going to turn off my cynicism filter for a while and wish the guy luck (he's going to need it!)
zaugg
What does this spell out for the power struggles between Tom and Jerry, Itchy and Scratchy, Mighty Mouse and assorted bad guys, Danger Mouse and Baron Greenback (not a cat, but probably in the same union)?
Please add to the list. Those damn cartoon mice get away with murder.
zaugg
zaugg
(Granted, console makers can get him to buy one with a loss-leader price point, but that's not really my point)
This is what I like about Nintendo's next-gen strategy. They're making a games machine. To play games on. Period.
The panacea, to my mind, is multiple dedicated devices that can spontaneously network. (think Jini, or Universal Plug'n'P[lr]ay.. shudder). Once these standards mature, the all-in-wunderbox might seem a little "early nineties".
Zaugg.
The new 7200 rpm drives are still physically read slower that 33 MB/s... ...but ATA/66 will speed up data that is fetched from the hard drives cache. There was a good article on anandtech recently on ATA 33 vs ATA 66 zaugg (.sig to be released "when it's done!")
It seems that every UI that I "U" with, is a matter of compromise. This is, as I see it, due to the incredibly limited feedback that the UI processes. When I use a new command line tool, I curse the learning curve. But once I've invested the time to learn the switches, I relish the power. So how can the UI know my level of knowledge, my goals, and what I'm thinking about? ((un)intellisense is a half-assed attempt to solve this. I believe that once that UI might be the next computer revolution: our 3d cards can render more polygons than most users could possibly care about every second, and we are networking with fatter pipes? UIs that intelligently process user feedback are next. just my 2c, zaugg.