JSON has nothing to do with Java. It's only coincidence that the implementation of JSON-RPC mentioned in the post happened to be a Java implementation. You could just as easily implement JSON/JSON-RPC in whatever language you want.
I've got a Dell 2001FP and it's friggen' amazing. The best monitor I've ever owned. During the day I develop on it and at night I play games on it (yes, FPS). I've never had a single problem with this monitor having mouse or any other kind of lag. Double check your video card/drivers.
Okay, I don't want to hear any more about SETI@Home not releasing the source code. Here is the real deal on all of this. Do any of you wonder why SGI is blowing the doors off of everybody else? Do you wonder why they crank blocks in under 3 hours? It's not because they have superior hardware, it's because they have the all-powerful SETI@Home client source code. They've gone in and tweaked it so that the FFT (fast fourier transforms) routines use the optimized math libraries (they didn't previously). Bam, instant boost for SGI. Sun has done the same thing, you just can't notice since their average block rate hasn't dropped down yet (they've only been using the optimized client for about 2 weeks now). Both the SGI and the Sun clients had to pass certain SETI@Home tests to be allowed by SETI@Home (they had to crank a block and return results within a certain amount of precision and accuracy).
Both Sun and SGI have offered the optimized clients to SETI@Home to distribute on their home page, but SETI@Home doesn't want them (they don't want forks in the code base or something like that).
Slashdot Mirror
JSON has nothing to do with Java. It's only coincidence that the implementation of JSON-RPC mentioned in the post happened to be a Java implementation. You could just as easily implement JSON/JSON-RPC in whatever language you want.
I've got a Dell 2001FP and it's friggen' amazing. The best monitor I've ever owned. During the day I develop on it and at night I play games on it (yes, FPS). I've never had a single problem with this monitor having mouse or any other kind of lag. Double check your video card/drivers.
Okay, I don't want to hear any more about SETI@Home not releasing the source code. Here is the real deal on all of this. Do any of you wonder why SGI is blowing the doors off of everybody else? Do you wonder why they crank blocks in under 3 hours? It's not because they have superior hardware, it's because they have the all-powerful SETI@Home client source code. They've gone in and tweaked it so that the FFT (fast fourier transforms) routines use the optimized math libraries (they didn't previously). Bam, instant boost for SGI. Sun has done the same thing, you just can't notice since their average block rate hasn't dropped down yet (they've only been using the optimized client for about 2 weeks now). Both the SGI and the Sun clients had to pass certain SETI@Home tests to be allowed by SETI@Home (they had to crank a block and return results within a certain amount of precision and accuracy).
Both Sun and SGI have offered the optimized clients to SETI@Home to distribute on their home page, but SETI@Home doesn't want them (they don't want forks in the code base or something like that).