pffft, most things on cars don't wear that quickly.
My 25 year old truck can attest to that. Sure, I've replaced the brakes, tires, fluids, clutch, maybe an electric doohicky here or there (pvc valve; choke) but other than that it's all original. They wear out, yes, but not as fast as you seem to think and they are not that hard to maintain.
Another drive is no substitute for something like a CDROM or DVD.
The drive is a complex piece of equipment with many delicate parts. A DVD/CDROM/Tape is simple, no moving parts, and easy to replicate on multiple discs.
I don't backup my whole damn system though. Most stuff can be reinstalled. Only my data needs to be backed up.
The only advantage you get with +RW at the moment is that OTHER packet writing methods (like Nero InCD) also benefit from the exact laser positioning.
That's not the only benefit. I use +RW discs just like a hard-drive right now. Using FAT or flash memory type filesystems. I have yet to have one "wear-out" as it were.
You don't have to use Mount Rainier to use them. Hell, you can put ext2 on one and use it (not recommended though since ext2 tends to overwrite the same spot many time).
While I can use a normal keyboard for some length of time (like my laptop), I couldn't do it all the time.
I like my MS Natural Elite keyboards.
For me, the most kick-ass keyboard would have the feel of an Apple Pro Keyboard and it would be bent and shaped more ergonomically like the MS Natural. It wouldn't even need to be as pronounced a bend like the Natural, just a little something to keep my hands happy.
And no "Internet" or "Cut/Copy" or other stupid buttons. Ugh, I hate that crap. CTRL-C/V/X is fine. I don't even use the F-keys except to get into my BIOS. Take 'em off too!
This is coming from a former experienced (actually had a full time job for many years) C programmer that switched to Java programming (for many more years of full time employment) and would never go back to C (unless, of course, I had to to feed my family).
Similar to me. I've been programming in C for nearly 20 years and Java for nearly 10 (back when it was in beta). I've done huge projects in both languages.
What good is a program that can manage 1000 transactions a second when you only need to manage 10 a second. And besides, current archs require clustering of applications (for robustness) which also provides load balancing which in turn increases the throughput further. Java is more than fast enough.
It's that kind of thinking that creates the bloatware crap we have today. Stuff that performs worse than older software despite the fact that the hardware is 10 times faster.
This is EXACTLY what Java tries to be. The benefits of compiled languages (type checking, link checking) with the ease of use of a scripting language.
Hmm, some people would say "The disadvantages of compiled languages and not nearly as useful as a real scripting language".
Sun has been an inept manager of Java, but that shouldn't taint the language itself. If you don't like Sun's JVM, use IBM's. You have a choice
Nope. Didn't work; won't work. Java is dead because of what they did.
Who said "Extremism in the cause of object-orientedness is no vice"? Just kidding. Actually Java is not on the extreme end of "object-orientedness". More so the C++ (this is a good thing) but less so than Smalltalk. As a matter of fact, the C-ness of Java makes it quite easy to understand.
Any time I have to instantiate a "Point" class just to put in X/Y coordinates, that's going too far. Java is tedious like a low-level language but you don't get any of the power (no pointers, etc).
Java is better on the server but not just because of the available API's (no question those are nice too). A program that follows the Java naming conventions and good OO design philosophy is just easier to maintain.
The same could be said of any language. The disadvantages of Java take it out of the picture as a viable option.
Huh? Java was nothing if not new. Try explaining the benefits of garbage collections to a C programmer. He probably won't say "we were doing that with C in '83"
We were. And at least in C/C++ I have a choice. Plus I have more control. If you want complete ease of use, use a scripting language, if you want speed/power use a low level language. Java is the worst of both.
- Java is slow. Yes, it's faster than it used to be but it's still slower than other languages.
- Continuing the previous thought. Other high-level (scripting) languages offer an ease of use that Java doesn't have but Java tries to be one of these languages. It fails. And it's not fast enough to be a low level language. Where does that leave Java? Suck-land is where.
- Java has always had all kinds of miniature bugs deep inside it. These are not big enough to get Sun to do anything about them but are like a thorn in your foot. Witness how long it took Sun to add poll/select support.
- Extreme object-orientedness is extremely annoying. You have to instantiate all sorts of tiny little useless classes to get anything done. Massive overhead and tedious.
- It requires too much crap to be installed. Going from a blank system to something that can run non-trivial Java apps requires too much crap to be done. There are settings, tiny little packages, and all sorts of stuff and crap that must be done (try to get end-users to do all that! pffft, they won't use your app).
- The GUI sucks. Sure, SWT is a step in the right direction, but it's too late and the API sucks.
- It's not open enough. Sun took an Apple-like stance on not allowing outsiders control and Java has suffered for it. It's too late to be fixed, it should have been open from the start.
- On the server people say Java is good, but they're really only talking about all the API's that are available. Nothing special there and nothing that can't be done better in another, better language (either scripting like Perl/Pythong or fast like C/C++).
- Java doesn't offer anything new. Byte-code never took off.
And there's more stuff I don't care to spend more time writing about.
I've noticed something strange in that I could've even compile the nVidia driver with 2.6.6-rc3-mm2.
It doesn't compile with 2.6.6-mm1 either.
I'm using gcc 3.4 and the driver compiles fine with 2.6.5.
It looks like it's complaining about some of the function prototypes (conflicting types because the source files are missing the NV_API_CALL declaration on the return type). If I fix them it compiles OK but it doesn't work right. X works fine until I try to quit, then the whole system locks up tight (no log or anything).
Slashdot Mirror
Did you go with AMD or Intel for your IBM system?
pffft, most things on cars don't wear that quickly.
My 25 year old truck can attest to that. Sure, I've replaced the brakes, tires, fluids, clutch, maybe an electric doohicky here or there (pvc valve; choke) but other than that it's all original. They wear out, yes, but not as fast as you seem to think and they are not that hard to maintain.
Damn, how often do your disks fail?
You might want to think about buying better hardware.
Another drive is no substitute for something like a CDROM or DVD.
The drive is a complex piece of equipment with many delicate parts. A DVD/CDROM/Tape is simple, no moving parts, and easy to replicate on multiple discs.
I don't backup my whole damn system though. Most stuff can be reinstalled. Only my data needs to be backed up.
That's what I was thinking. At that price, you're looking at around 11 Opteron 250 processors or 13 Xeon 3.2 Ghz EMT64 chips.
Or, for the price consious that 21 Opteron 246's.
How do these Transmeta chips compare to an Opteron 250?
Or course, there are more components than just the CPU's. Like multiple motherboards. But still...
Dude, that Apple was out of date when you bought it. Compared to say, a much cheaper dual Opteron 250 setup.
Sheesh.. Who wants only 20/40 GB or even less space? (iPod, CF, etc.)
Use a Firewire/USB2 to a small 3.5" combo enclosure (some are barely larger than the drive, which is damn small).
250+ GB... works on USB1 (ie. everything), USB2, and Firewire systems. No worries.
The only advantage you get with +RW at the moment is that OTHER packet writing methods (like Nero InCD) also benefit from the exact laser positioning.
That's not the only benefit. I use +RW discs just like a hard-drive right now. Using FAT or flash memory type filesystems. I have yet to have one "wear-out" as it were.
You don't have to use Mount Rainier to use them. Hell, you can put ext2 on one and use it (not recommended though since ext2 tends to overwrite the same spot many time).
While I can use a normal keyboard for some length of time (like my laptop), I couldn't do it all the time.
I like my MS Natural Elite keyboards.
For me, the most kick-ass keyboard would have the feel of an Apple Pro Keyboard and it would be bent and shaped more ergonomically like the MS Natural. It wouldn't even need to be as pronounced a bend like the Natural, just a little something to keep my hands happy.
And no "Internet" or "Cut/Copy" or other stupid buttons. Ugh, I hate that crap. CTRL-C/V/X is fine. I don't even use the F-keys except to get into my BIOS. Take 'em off too!
This is coming from a former experienced (actually had a full time job for many years) C programmer that switched to Java programming (for many more years of full time employment) and would never go back to C (unless, of course, I had to to feed my family).
Similar to me. I've been programming in C for nearly 20 years and Java for nearly 10 (back when it was in beta). I've done huge projects in both languages.
What good is a program that can manage 1000 transactions a second when you only need to manage 10 a second. And besides, current archs require clustering of applications (for robustness) which also provides load balancing which in turn increases the throughput further. Java is more than fast enough.
It's that kind of thinking that creates the bloatware crap we have today. Stuff that performs worse than older software despite the fact that the hardware is 10 times faster.
This is EXACTLY what Java tries to be. The benefits of compiled languages (type checking, link checking) with the ease of use of a scripting language.
Hmm, some people would say "The disadvantages of compiled languages and not nearly as useful as a real scripting language".
Sun has been an inept manager of Java, but that shouldn't taint the language itself. If you don't like Sun's JVM, use IBM's. You have a choice
Nope. Didn't work; won't work. Java is dead because of what they did.
Who said "Extremism in the cause of object-orientedness is no vice"? Just kidding. Actually Java is not on the extreme end of "object-orientedness". More so the C++ (this is a good thing) but less so than Smalltalk. As a matter of fact, the C-ness of Java makes it quite easy to understand.
Any time I have to instantiate a "Point" class just to put in X/Y coordinates, that's going too far. Java is tedious like a low-level language but you don't get any of the power (no pointers, etc).
Java is better on the server but not just because of the available API's (no question those are nice too). A program that follows the Java naming conventions and good OO design philosophy is just easier to maintain.
The same could be said of any language. The disadvantages of Java take it out of the picture as a viable option.
Huh? Java was nothing if not new. Try explaining the benefits of garbage collections to a C programmer. He probably won't say "we were doing that with C in '83"
We were. And at least in C/C++ I have a choice. Plus I have more control. If you want complete ease of use, use a scripting language, if you want speed/power use a low level language. Java is the worst of both.
No, I didn't RTFA (why waste time on Java crap).
- Java is slow. Yes, it's faster than it used to be but it's still slower than other languages.
- Continuing the previous thought. Other high-level (scripting) languages offer an ease of use that Java doesn't have but Java tries to be one of these languages. It fails. And it's not fast enough to be a low level language. Where does that leave Java? Suck-land is where.
- Java has always had all kinds of miniature bugs deep inside it. These are not big enough to get Sun to do anything about them but are like a thorn in your foot. Witness how long it took Sun to add poll/select support.
- Extreme object-orientedness is extremely annoying. You have to instantiate all sorts of tiny little useless classes to get anything done. Massive overhead and tedious.
- It requires too much crap to be installed. Going from a blank system to something that can run non-trivial Java apps requires too much crap to be done. There are settings, tiny little packages, and all sorts of stuff and crap that must be done (try to get end-users to do all that! pffft, they won't use your app).
- The GUI sucks. Sure, SWT is a step in the right direction, but it's too late and the API sucks.
- It's not open enough. Sun took an Apple-like stance on not allowing outsiders control and Java has suffered for it. It's too late to be fixed, it should have been open from the start.
- On the server people say Java is good, but they're really only talking about all the API's that are available. Nothing special there and nothing that can't be done better in another, better language (either scripting like Perl/Pythong or fast like C/C++).
- Java doesn't offer anything new. Byte-code never took off.
And there's more stuff I don't care to spend more time writing about.
Java was stillborn.
Is their language limiting their intelligence or could it just be that their intelligence is limiting their language?
Heh, I've noticed a large number of low UID users are incredibly unintelligent so don't let that fool you.
I've noticed something strange in that I could've even compile the nVidia driver with 2.6.6-rc3-mm2. It doesn't compile with 2.6.6-mm1 either. I'm using gcc 3.4 and the driver compiles fine with 2.6.5. It looks like it's complaining about some of the function prototypes (conflicting types because the source files are missing the NV_API_CALL declaration on the return type). If I fix them it compiles OK but it doesn't work right. X works fine until I try to quit, then the whole system locks up tight (no log or anything).