I gotta call BS on this one. I work on the development team for many of these servers. (No, I'm not allowed to tell you when they'll ship, so don't ask). There are NO chipset issues I am aware of, and the units are not crippled. I'd be interested in finding out why you think this is the case.
Case in point:
ahref=http://www.tpc.org/tpcc/results/tpcc_result_ detail.asp?id=106071802rel=url2html-4549http://www .tpc.org/tpcc/results/tpcc_result_detail.asp?id=10 6071802>
While x64 may be better-suited for web serving, part of the reason x64 seems to be better than ia64 on most other workloads is that you may not have the OS and software optimized for the ia64 architecture - you're still writing and compiling in a x86-centric view and I don't think compiler technologies have evolved to the point where they can fully utilize ia64 ILP.
Good luck getting XP to boot if the firmware is a true EFI (legacy-free) implementation. If it has a BIOS-compatibility layer (I forget exactly what it's called) - which is basically just a BIOS plunked into the firmware so it can support the legacy BIOS interrupts, you may be in luck. Otherwise you'll have to do some pretty major hacking of the firmware OS interface.
... or call me ignorant. I've got my fire-proof suit on, so I'll ask this question (I suppose its been posed and answered several hundred times.
How do software engineers/programmers/companies expect to pay their bills in an open-source environment where there is no IP or licensing?
What do I have to gain if I/we write a bit of code or develop an algorithm and then give it to the world for free? Why did I spend all those hours thinking and creating?
Also, what is the purpose of writing software to decrypt copyrighted information? To take something you have not paid for? To show the creators of said copyrighted information that their encryption scheme is not strong enough? Why then distribute the decryption software/algorithm to the world?
I've been a student, and I could probably have afforded one. But I still couldn't justify getting either a Palm or PocketPC. Even now, when I have a job.
When I was debating myself on whether to drop the (then) $500 on a PocketPC, someone asked me to ask myself if there was really a need for it. Would it allow me to do anything that I can't do now? Sure, it would be nice to have, but it wouldn't really solve any problems for me....
Can you actually hear/notice the difference between a $100,000 system and a $10,000 system? Between a $10,000 system and a $1,000 system?
A lot of times, the more you pay, the more features you get. What features besides being able to provide good, clean sound for your music and movies do you need? Will is wash my dishes?
I was a CompE major, and I'm writing software.
As a CompE at my school (University of Illinois at Urbana-Champaign) I took courses that spanned from very EE to very CS - Circuits, E&M, Analog Circuits, DSP, Data Structures, and OS - as well as CompE courses like architecture and digital design. Granted I didn't get ALL the theory behind the CS topics, I came out with a broad base of knowledge.
In short, I think taking the CompE route will help you gain a deeper knowledge of what your software is doing with the transistors below it. This hopefully makes you a better programmer.
This has some pretty useful points in high availability situations. Instead of having the system barf when it encounters a bad page, it can mark it bad and the OS avoids using it. Then, during some 'scheduled' down-time, technicians can replace the bad DIMM(s).
Something even nicer would be runtime deallocation of bad memory...
Slashdot Mirror
Actually, she's running for Senate
Heck yeah! We've been CrossFit'ing for a while now, in a friend's garage. I feel great and in better shape than I've been in a long time.
Watch "The Office" and do pretty much the opposite of what Michael Scott does.
I gotta call BS on this one. I work on the development team for many of these servers. (No, I'm not allowed to tell you when they'll ship, so don't ask). There are NO chipset issues I am aware of, and the units are not crippled. I'd be interested in finding out why you think this is the case. Case in point: ahref=http://www.tpc.org/tpcc/results/tpcc_result_ detail.asp?id=106071802rel=url2html-4549http://www .tpc.org/tpcc/results/tpcc_result_detail.asp?id=10 6071802>
While x64 may be better-suited for web serving, part of the reason x64 seems to be better than ia64 on most other workloads is that you may not have the OS and software optimized for the ia64 architecture - you're still writing and compiling in a x86-centric view and I don't think compiler technologies have evolved to the point where they can fully utilize ia64 ILP.
Good luck getting XP to boot if the firmware is a true EFI (legacy-free) implementation. If it has a BIOS-compatibility layer (I forget exactly what it's called) - which is basically just a BIOS plunked into the firmware so it can support the legacy BIOS interrupts, you may be in luck. Otherwise you'll have to do some pretty major hacking of the firmware OS interface.
Oh, so that's the other thing you can do with a history degree.
Apparently, all you need is a history degree to run a major corporation (...into the ground)
That is true. We develop these Itanium systems, and all of my boxes are multi-boot Windows, Linux, and HP-UX.
... or call me ignorant. I've got my fire-proof suit on, so I'll ask this question (I suppose its been posed and answered several hundred times. How do software engineers/programmers/companies expect to pay their bills in an open-source environment where there is no IP or licensing? What do I have to gain if I/we write a bit of code or develop an algorithm and then give it to the world for free? Why did I spend all those hours thinking and creating? Also, what is the purpose of writing software to decrypt copyrighted information? To take something you have not paid for? To show the creators of said copyrighted information that their encryption scheme is not strong enough? Why then distribute the decryption software/algorithm to the world?
I've been a student, and I could probably have afforded one. But I still couldn't justify getting either a Palm or PocketPC. Even now, when I have a job. When I was debating myself on whether to drop the (then) $500 on a PocketPC, someone asked me to ask myself if there was really a need for it. Would it allow me to do anything that I can't do now? Sure, it would be nice to have, but it wouldn't really solve any problems for me....
Can you actually hear/notice the difference between a $100,000 system and a $10,000 system? Between a $10,000 system and a $1,000 system? A lot of times, the more you pay, the more features you get. What features besides being able to provide good, clean sound for your music and movies do you need? Will is wash my dishes?
I was a CompE major, and I'm writing software. As a CompE at my school (University of Illinois at Urbana-Champaign) I took courses that spanned from very EE to very CS - Circuits, E&M, Analog Circuits, DSP, Data Structures, and OS - as well as CompE courses like architecture and digital design. Granted I didn't get ALL the theory behind the CS topics, I came out with a broad base of knowledge. In short, I think taking the CompE route will help you gain a deeper knowledge of what your software is doing with the transistors below it. This hopefully makes you a better programmer.
Ah, that is a good idea. However, I don't know too many employers that hire history majors to write software.
This has some pretty useful points in high availability situations. Instead of having the system barf when it encounters a bad page, it can mark it bad and the OS avoids using it. Then, during some 'scheduled' down-time, technicians can replace the bad DIMM(s). Something even nicer would be runtime deallocation of bad memory...