I downloaded it, unfortunately it uses some unspecified DiVX codec which I don't have installed. (And I have about 5 of 'em.) Unfortuantely the readme doesn't specify which codec they've used.
While id isn't planning on giving away the entire plot of the game anytime soon, here's what we know so far: DOOM III is basically a "retelling" of the original DOOM, with many of the same characters and themes, and even some returning weapons.
And while the basic story might have been a bit worn out by now it doesn't really matter as far as I'm concerned. It wasn't really much of a story to begin with. But the new engines makes it possible to take the story to new levels.
Just as with Q3A I bet other companies will use the Doom3 engine to create truly new games. Like Alice, Jedi Knight 2 and so on has been done with the Quake3 engine.
Yeah, at first I was confused and thought that the new engine didn't run faster on current hardware. Then they demoed Doom1 and 2 and they were just as slow...
If you're gonna make a huge file you might as well make it high FPS as well. It wouldn't have mattered much if they'd tacked on another 50 MB on it. (As far as download time goes at any rate.)
Not really, KaZaA and similar generally just download the file from different sources, but start the download at different places.
Swarmcast use FEC coding of the file so it's more efficient when multiple people download the same file. (The people downloading can share the file as well.) It's/not/ as trivial as downloading a file with different offsets.
An undergrad course I'm taking right now use 68k8. (A slightly cheaper version of the 68k; it has fewer interrupt levels for instance.) I can certify that it's a really nice CPU to work with. (Not that I've tried all that many others.;-)
To get a simple computer board going you only need a 68k8, some ROM and RAM and some programmable logic circuits. (To control the signals to ROM/RAM circuits.) When we started on the project it seemed rather hard, after only a few weeks now I'm confident that we could have done a lot more fun stuff. (Given the time to do so naturally.)
We're creating a MOD player btw, this involves some slightly more hardcore circuits, mainly a medium sized Lattice (FPGA).
Re:Everything you know is wrong
on
Review: U-571
·
· Score: 3, Informative
I think that what the Polish team did was extremely important for moral. They called in teams from France and England only a few weeks before the Germans invaded Poland and demostrated what they had done.
At that time everyone else was convinced that Enigma was uncrackable. Ironically it was actually a german who gave the specifications of the Enigma to a Polish diplomat. (The Enigma was used before the war as a crypto device for the industry and for diplomats.)
"The Code Book" by Simon Singh has a few chapters dedicated to it and Bletchley Park. Very interesting reading. Truly the unsung heroes of the war. (Because what they did was classified, so no-one knew about their great accomplishments.)
Well, as long as you can hit the particular spots where the eye is sensitive it shouldn't matter much. (It will matter some, but it's engineering, so it's just a matter of getting "close enough".;-)
A lot of the problems involved in hardware design are logarithmically more diffucult than with software.
Concurrency tend to bite you? On a chip everything happens at the same time.
Is debugging a bitch? Try doing it with a hardware design where results happen concurrently and you have to run long simulations in order to even find potential bugs.
I've tried both, while software is a fun past time (At the level I do it.) I get head-aches from hardware design.;-)
But if you have a computer/robot which is not capable of being thought then why on earth would you want it to drive your car? (If you are the person whom I responded to originally.)
And even before you have magical computers it could be useful. You just have to add enough information for the computer to appear intelligent. That it would be unable to discuss philosophy is a given; but that's not really the goal at hand.
Here is one way of putting his fundamental objection. Would you rather have: a) A surgeon working on your heart with his/her own hands? or b) A surgeon using a microphone to direct a robotic knife with only auditory feedback?
I haven't actually read these objections of his, so I can't comment on all of them, but I will comment on this one. IMHO it's even more bollox than the "we can't talk and think at the same time" argument. Naturally I wouldn't want a surgon to do it all by voice, but that doesn't say it's a bad way of communicating. (It seems to be working for quite a few people in the world.) I can for instance use the same argument that a computer mouse is a terrible interface. (Would you want a surgon to control a robotic arm with a mouse?)
The solution to that problem could be to have a surgon using a force feedback scalpel dummy to operate, using VR glasses or some such technology. Then he could perform operations from a different part of the country in case of emergencies. And the robotic arm could also serve as a safety buffer, so if he slipped the arm wouldn't. Kind of like "fly by wire" but with operating equipment.
(Naturally this isn't my idea, people are already working on this.)
The first time you are told to do something you also require being told what to do. (Or learning by observing others, or experimenting, or a minnion other ways.) You are not born with the knowledge of driving away with a car, but it may seem so natural that you assume the computer/robot is stupid for not knowing how to.
Naturally it is the programmer who chould have forseen this eventuality and added it to the computer/robots memory.
Most computers have had that capacity for 5-10 years. They just all tend to suck at it. Particularly if you're not speaking directly into the microphone.
So there's still a need for good voice control systems.
Because you tie the voice command "next" to the "next" button in Winamp? Or perhaps because you say "winamp" or "song" first?
My keyboard has "next", "previous" and such buttons on it. When I press them they magically chose the correct program, because I started it with the same keyboard. (Or because it's the only program open for which it's a relevant command.)
With a little bit of planning from the programmer you can make the computer seem to do magical tricks.
Seems like that movie "At first sight" is actually based on a book by Sacks. Naturally that most likely mean that they have completely trashed the story of the book.;-)
Re:Mistranslation (Re:gibberish)
on
Sony PCG-U1
·
· Score: 1
This site has some: J-List. I did think that they had more shirt than I could find now however. Most likely it's on the site somewhere, it's just not very organized. (But there are a lot of crazy stuff there, so it's fun to browse around.)
If that doesn't help you might be able to find more places from Japan referense altough that is more of a link site to a lot of Japan oriented sites.
Also places like MegaTokyo has some fun shirts as well. (Like the b4k4^2 in kanji shirt.)
Because general purpose processors are more expensive, not as fast and use more power. That's three reasons, and then you can add multi-processing issues to device drivers. Then it'd take decades for stable drivers to materialize.;-)
The specific part about IP stacks on ethernet cards is interesting though. For it to be practical you would need standardized stuff though, it's annoying as it is to get specific drivers for a card. If I'd had to get a special IP stack as well it would be very confusing for the average user.
Plextor, the long standing champion of CDR's, don't even make SCSI versions of their latest models. And I can tell you that I got a lot more coasters from my old x4 SCSI burner than from my rather new x24 IDE burner. Mainly due to 'Burnproof' naturally.
They are not bad programmers, they are just bad team-workers. If you have people that are unable to see their own folly then it's not going to help if you let them work on their own. Most likely they'll end up with prima-donna code which is useless. (And noone else will understand it.)
If you use pair programming you get a discussion on the topic and hopefully the bad coder can learn the error of his ways. Otherwise you will at least have other people which know his/her code when the bad coder is fired.
And XP recommends that you swap code often. The aim is that you shouldn't get to attached to "your code" becuase that's a common way to get bugs. (Because it's never my code that's buggy.) And it get's more eyeballs on the code. (And the prima-donna thing is remedied.)
As a fellow Swede who's liven in the states for a year I can tell you that most places there don't have sidewalks at all. Most people just drive cars so it's not really an issue. In cities there are sidwwalks however, but not many people bike in any case, so it's still not much of an issue.
Compare this with Sweden where there are abundant sidewalks and often separate lanes for biking and the situation is very different. Naturally that means that it would be alot easier to include Segways here. Just drive them where you'd bike otherwise. (Or rollerblade.)
Probably? At least last year you could have put a dead guy as a goalie and he would have won. (Because at least he didn't score against himself. Robotic players sometimes get confused and aim for their own goal.)
Slashdot Mirror
I downloaded it, unfortunately it uses some unspecified DiVX codec which I don't have installed. (And I have about 5 of 'em.) Unfortuantely the readme doesn't specify which codec they've used.
If anyone knows please post.
And while the basic story might have been a bit worn out by now it doesn't really matter as far as I'm concerned. It wasn't really much of a story to begin with. But the new engines makes it possible to take the story to new levels.
Just as with Q3A I bet other companies will use the Doom3 engine to create truly new games. Like Alice, Jedi Knight 2 and so on has been done with the Quake3 engine.
But it seems like D3 will be well worth playing.
Yeah, at first I was confused and thought that the new engine didn't run faster on current hardware. Then they demoed Doom1 and 2 and they were just as slow...
If you're gonna make a huge file you might as well make it high FPS as well. It wouldn't have mattered much if they'd tacked on another 50 MB on it. (As far as download time goes at any rate.)
Not really, KaZaA and similar generally just download the file from different sources, but start the download at different places.
/not/ as trivial as downloading a file with different offsets.
Swarmcast use FEC coding of the file so it's more efficient when multiple people download the same file. (The people downloading can share the file as well.) It's
Well that can be said of at least 50% of good SF. (Or at least it's generally critizising something the author feels might happen.)
An undergrad course I'm taking right now use 68k8. (A slightly cheaper version of the 68k; it has fewer interrupt levels for instance.) I can certify that it's a really nice CPU to work with. (Not that I've tried all that many others. ;-)
To get a simple computer board going you only need a 68k8, some ROM and RAM and some programmable logic circuits. (To control the signals to ROM/RAM circuits.) When we started on the project it seemed rather hard, after only a few weeks now I'm confident that we could have done a lot more fun stuff. (Given the time to do so naturally.)
We're creating a MOD player btw, this involves some slightly more hardcore circuits, mainly a medium sized Lattice (FPGA).
I think that what the Polish team did was extremely important for moral. They called in teams from France and England only a few weeks before the Germans invaded Poland and demostrated what they had done.
At that time everyone else was convinced that Enigma was uncrackable. Ironically it was actually a german who gave the specifications of the Enigma to a Polish diplomat. (The Enigma was used before the war as a crypto device for the industry and for diplomats.)
"The Code Book" by Simon Singh has a few chapters dedicated to it and Bletchley Park. Very interesting reading. Truly the unsung heroes of the war. (Because what they did was classified, so no-one knew about their great accomplishments.)
It's a quick and secure way of separating parked cars from moving cars. (In case they have just slowed down, or are temporarily stopped.)
Well, as long as you can hit the particular spots where the eye is sensitive it shouldn't matter much. (It will matter some, but it's engineering, so it's just a matter of getting "close enough". ;-)
A lot of the problems involved in hardware design are logarithmically more diffucult than with software.
;-)
Concurrency tend to bite you? On a chip everything happens at the same time.
Is debugging a bitch? Try doing it with a hardware design where results happen concurrently and you have to run long simulations in order to even find potential bugs.
I've tried both, while software is a fun past time (At the level I do it.) I get head-aches from hardware design.
But if you have a computer/robot which is not capable of being thought then why on earth would you want it to drive your car? (If you are the person whom I responded to originally.)
And even before you have magical computers it could be useful. You just have to add enough information for the computer to appear intelligent. That it would be unable to discuss philosophy is a given; but that's not really the goal at hand.
I haven't actually read these objections of his, so I can't comment on all of them, but I will comment on this one. IMHO it's even more bollox than the "we can't talk and think at the same time" argument. Naturally I wouldn't want a surgon to do it all by voice, but that doesn't say it's a bad way of communicating. (It seems to be working for quite a few people in the world.) I can for instance use the same argument that a computer mouse is a terrible interface. (Would you want a surgon to control a robotic arm with a mouse?)
The solution to that problem could be to have a surgon using a force feedback scalpel dummy to operate, using VR glasses or some such technology. Then he could perform operations from a different part of the country in case of emergencies. And the robotic arm could also serve as a safety buffer, so if he slipped the arm wouldn't. Kind of like "fly by wire" but with operating equipment.
(Naturally this isn't my idea, people are already working on this.)
The first time you are told to do something you also require being told what to do. (Or learning by observing others, or experimenting, or a minnion other ways.) You are not born with the knowledge of driving away with a car, but it may seem so natural that you assume the computer/robot is stupid for not knowing how to.
Naturally it is the programmer who chould have forseen this eventuality and added it to the computer/robots memory.
Most computers have had that capacity for 5-10 years. They just all tend to suck at it. Particularly if you're not speaking directly into the microphone.
So there's still a need for good voice control systems.
Because you tie the voice command "next" to the "next" button in Winamp? Or perhaps because you say "winamp" or "song" first?
My keyboard has "next", "previous" and such buttons on it. When I press them they magically chose the correct program, because I started it with the same keyboard. (Or because it's the only program open for which it's a relevant command.)
With a little bit of planning from the programmer you can make the computer seem to do magical tricks.
Seems like that movie "At first sight" is actually based on a book by Sacks. Naturally that most likely mean that they have completely trashed the story of the book. ;-)
This site has some: J-List. I did think that they had more shirt than I could find now however. Most likely it's on the site somewhere, it's just not very organized. (But there are a lot of crazy stuff there, so it's fun to browse around.)
If that doesn't help you might be able to find more places from Japan referense altough that is more of a link site to a lot of Japan oriented sites.
Also places like MegaTokyo has some fun shirts as well. (Like the b4k4^2 in kanji shirt.)
Because general purpose processors are more expensive, not as fast and use more power. That's three reasons, and then you can add multi-processing issues to device drivers. Then it'd take decades for stable drivers to materialize. ;-)
The specific part about IP stacks on ethernet cards is interesting though. For it to be practical you would need standardized stuff though, it's annoying as it is to get specific drivers for a card. If I'd had to get a special IP stack as well it would be very confusing for the average user.
Yeah. Serves me right for having fifteen open browser windows of the same discussion but different threads. ;-)
You know, x1 burning isn't exactly considered "top of the line" any longer. ;-)
Plextor, the long standing champion of CDR's, don't even make SCSI versions of their latest models. And I can tell you that I got a lot more coasters from my old x4 SCSI burner than from my rather new x24 IDE burner. Mainly due to 'Burnproof' naturally.
And the IDE cost half as much as well.
I don't like the idea of finger print based ID. Basically I want the ID to be based on something I can put down on the ground and step away from.
They are not bad programmers, they are just bad team-workers. If you have people that are unable to see their own folly then it's not going to help if you let them work on their own. Most likely they'll end up with prima-donna code which is useless. (And noone else will understand it.)
If you use pair programming you get a discussion on the topic and hopefully the bad coder can learn the error of his ways. Otherwise you will at least have other people which know his/her code when the bad coder is fired.
And XP recommends that you swap code often. The aim is that you shouldn't get to attached to "your code" becuase that's a common way to get bugs. (Because it's never my code that's buggy.) And it get's more eyeballs on the code. (And the prima-donna thing is remedied.)
As a fellow Swede who's liven in the states for a year I can tell you that most places there don't have sidewalks at all. Most people just drive cars so it's not really an issue. In cities there are sidwwalks however, but not many people bike in any case, so it's still not much of an issue.
Compare this with Sweden where there are abundant sidewalks and often separate lanes for biking and the situation is very different. Naturally that means that it would be alot easier to include Segways here. Just drive them where you'd bike otherwise. (Or rollerblade.)
Probably? At least last year you could have put a dead guy as a goalie and he would have won. (Because at least he didn't score against himself. Robotic players sometimes get confused and aim for their own goal.)