well I have been using Japanese controllers for about 5-6 months now (the first one was an awesome all white prototype).
In the game industry it is quite easy to get a Japanese Xbox controller. I use mine to play halo on my brothers retail Xbox, no problems.
Of course these are all just pre-release controllers, MS may fuck things up for the retail Japanese controllers.
I also have to say that the Japanese Xbox controllers rock. they are the best controllers I have ever used. (and the US Xbox controllers are the worst controller ever invented, I'll take an original atari 1 button stick over one of them)
Re:Quality controllers?
on
MAME on X-Box
·
· Score: 1
I have to say that I am very very un-impressed with the Xbox controllers (as I too use them every day).
they are truely horrible.
- they are giant, waay to big for normal people's hands.
- the analog triggers are totally uncomfortable to hold down.
- the ABXY buttons are way too close together
- the analog SUCKS on the ABXY Buttons (really sucks)
- the shape of the ABXY buttons suck (bubbley)
- the right analog stick gets hit by your thumb when trying to push the ABXY buttons
- the back and start button are pretty much impossible to hit without moving your hand position
on the positive side:
- they feel well built
- they have 10 ft cords!!!!! (yes)
also the prototype Japanese controller that I tried was amazing. the best controller I have ever tried. it is pretty much a PS2 controller but better. even the analog ABXY on the Japanese controller was perfect. and the analog triggers were so easy to hold and easy to get a specific value.
I can't believe that the same people designed both controllers.
It sounds to me as you have never actually used a machine with high bandwidth memory access and a fast disk subsystem.
Compiling is generally not cpu bound as most compilers preprocess a file to create about a 100000 line file that then gets compiled to a large assembly file that then gets assembled in to an object file. Try compiling on a machine with a fast disk and memory bandwidth, you will see that is where the speed comes from. not raw cpu power.
unified name space starting at "/", almost everything accessable through the file system
unified socket/file/pipe space, they are all files, none of this handle crap
true tty interface, X is not UNIX but to be UNIX you need a real tty, NT definitly fails hard here
true posix signal handling, the ability to send a process a SIGSTOP and have it... stop! try that on NT
stuff is put where it should be, such at the kernel file cache, an application shouldn't have to deal with it
reliable filesystem, under UNIX your file system is trustworthy, under windows you have to be prepared at any time for it to die (such as smb shares do all the time)
real filesystem, true symlinks (not files that end in.lnk for christs sake!), hard linking, link -> inode genericy (ever wonder why windows was so much faster at recursive directory tree spanning? it is because the equivilent to readdir() tells it if it is a directory or not, no stat() needed, sure speed is nice but you loose the power and flexability of a generic link, BeOS handles this problem very nicly but being smart about creating files)
based on C, C is the common language of UNIX, like it or not
I would say that you could live without hard links (like BeOS does) but you need symlinks. I am not saying that BeOS is a UNIX, it isn't but it has some of the criteria (and some other cool stuff that I wish all unicies had) windows NT/2000/10000 is not UNIX and never will be. Angus.
Slashdot Mirror
well I have been using Japanese controllers for about 5-6 months now (the first one was an awesome all white prototype).
In the game industry it is quite easy to get a Japanese Xbox controller. I use mine to play halo on my brothers retail Xbox, no problems.
Of course these are all just pre-release controllers, MS may fuck things up for the retail Japanese controllers.
I also have to say that the Japanese Xbox controllers rock. they are the best controllers I have ever used. (and the US Xbox controllers are the worst controller ever invented, I'll take an original atari 1 button stick over one of them)
I have to say that I am very very un-impressed with the Xbox controllers (as I too use them every day).
they are truely horrible.
- they are giant, waay to big for normal people's hands.
- the analog triggers are totally uncomfortable to hold down.
- the ABXY buttons are way too close together
- the analog SUCKS on the ABXY Buttons (really sucks)
- the shape of the ABXY buttons suck (bubbley)
- the right analog stick gets hit by your thumb when trying to push the ABXY buttons
- the back and start button are pretty much impossible to hit without moving your hand position
on the positive side:
- they feel well built
- they have 10 ft cords!!!!! (yes)
also the prototype Japanese controller that I tried was amazing. the best controller I have ever tried. it is pretty much a PS2 controller but better. even the analog ABXY on the Japanese controller was perfect. and the analog triggers were so easy to hold and easy to get a specific value.
I can't believe that the same people designed both controllers.
oh-well.
this comparison may be on some interest if it was performed on half decent hardware. I mean who whould use a k6 for a server?
It sounds to me as you have never actually used
a machine with high bandwidth memory access and
a fast disk subsystem.
Compiling is generally not cpu bound as most
compilers preprocess a file to create about a
100000 line file that then gets compiled to a
large assembly file that then gets assembled in
to an object file. Try compiling on a machine
with a fast disk and memory bandwidth, you will
see that is where the speed comes from. not raw
cpu power.
- unified name space starting at "/", almost everything accessable through the file system
- unified socket/file/pipe space, they are all files, none of this handle crap
- true tty interface, X is not UNIX but to be UNIX you need a real tty, NT definitly fails hard here
- true posix signal handling, the ability to send a process a SIGSTOP and have it
... stop! try that on NT - stuff is put where it should be, such at the kernel file cache, an application shouldn't have to deal with it
- reliable filesystem, under UNIX your file system is trustworthy, under windows you have to be prepared at any time for it to die (such as smb shares do all the time)
- real filesystem, true symlinks (not files that end in
.lnk for christs sake!), hard linking, link -> inode genericy (ever wonder why windows was so much faster at recursive directory tree spanning? it is because the equivilent to readdir() tells it if it is a directory or not, no stat() needed, sure speed is nice but you loose the power and flexability of a generic link, BeOS handles this problem very nicly but being smart about creating files) - based on C, C is the common language of UNIX, like it or not
I would say that you could live without hard links (like BeOS does) but you need symlinks.I am not saying that BeOS is a UNIX, it isn't but it has some of the criteria (and some other cool stuff that I wish all unicies had)
windows NT/2000/10000 is not UNIX and never will be.
Angus.