<sarcasm >
nice to see that you actually read the post I wrote....
< /sarcasm >
The point I was trying to make is, that YES, I would love to see a quad-733 machine with 4gig of ram and two GeForce3 / Radeon 2 cards and two wide-screen 22 inch LCD panels siting on my desk, but it isn't actually necessary....
My G4-400 is not the latest and greatest, but I have yet to find it struggle...the endless chase for more power that is just under-utilised is a waste of time....so what if AMD have 1.3Mhz or more? the x86 architecture sucks...it's a pipe-doubled extension to an update of a 16 bit core cpu....in fact x86 core has not changed since the 486....(or maybe even the 386 with the integrated 387 FPU ...). Silicon Graphics have shown that with an efficient RISC 64bit CPU running at most 450MHz they can make machines absolutely fly....sure a Dell PC will beat it at Quake, but that is because Quake was WRITTEN ON A PC....therefore all the graphics routines, etc are optimised for PC hardware...if you wrote a game to take advantage of the SGI/ G4 style systems a PC would not come close. It's not about hardware, guys, it's about software to support it either a) natively or b) truly independently of platform, so the hardware can actually flex its' muscles.
I should know, I write the stuff..... and all of our clients have chosen to use the SGI/HP-UX builds over the NT versions as they know that while you can build a wall of x86 boxes for the price of one Octane, the SGI will get the job done more efficiently and more reliably over the longer term....
It's a mater of what you want - if you want a machine for Q3Arena or Tribes2, buy yourself a Tiny PC for £900 an expect no reliability or long-term usability, if you want a machine that works, and bridges the gap between home/office pc and the high-end Unix machines, buy a Mac G4, install OSX and fill it full of memory.
I get the impression that a few people on this forum as a rule like to say a lot without actually knowing what they are talking about, it is not MHz, but MFLOPS that count for real-world computing power, you only need more clock cycles if A) your code sucks or B) your architecture can only handle little bits of data at a time....hence the shift to 64-bit cpus.... ( or 128-bit altivec on a 64-bit G4 core...). SGI did it with the MIPS R4k series, apple have done it with the G3/G4 shift and Intel/AMD have done....oh, nothing, except make more ineffiecient cpus that go a bit quicker.....
I don't say this as I hate PCs - I don't, I used to work for a PC manufacturer and I think they have their place, but a Mac G4 is a different animal, the sooner you realise that, the better...as for the future: multi-processing is the best way forward, as it makes better uses of OSX, better use of multitasking and is more efficient...and I think the newly-touted Radeon 2 will be something a bit special.
Oh, and by the way - I have seen posts moaning about the Boot time of OSX - yes it takes a while, but that is becase it is UNIX.....in fact it is better not to shut down at all, merely log out, or go to power-save. UNIX schedules things itself for night-time, etc and any UNIX box can complain if you shut it dwn..and it will boot slower
, as it runs all it's tasks before letting you log on....
Just thought I would pass on the advice
One last thing - a hint, buy the book "Hacking Exposed", as it will give you a good idea of A) how to protect your Mac OSX (read: UNIX) machine and B) give anyone a better understanding of networking, etc
just thought it might be useful
There. Rant over. And a bit of help too. lol