morkintosh said:
it's not my personal workload that I am using as a reference point, but every system that I've ever studied or taught courses on (yes I am old enough to teach). Software systems are RARELY (but sometimes possible I admit) so complex that they need the kind of horse power that we are talking about yet are simple enough that a single developer can work on them.
Since I teach as well I will let the teacher in me give some advice: pick up a few books on software engineering and/or complex software engagements; The Mythical Man Month is a good starting point.
Since you are a teacher, you of all people should have the ability to listen, understand and read. Read my posts, please. I, of all people here in this thread, has been very understanding of the requirements of a computer in one's own field.
This is just for you in layman's terms since you may have been too caught up in programming language - people are different. Yes, they are. Really. They have different computer requirements. Others for word processing and email, others for gaming, others who make the games, others who create software applications, etc. You get the point. If they are satisfied with the amount of processing power, then good. Others who need more to do more, then good. Do I have to ridicule either one of them?
So what about "The Mythical Man Month" by Brooks should I read about that I haven't already read in 1998? So I can understand a work of a software engineer? As a former programmer in high school, I read stuff. What else would you attempt to recommend to me? "Rapid Development", "The Pragmatic Programmer" or perhaps "Software Project Survival Guide".
So what about it? You wanted me to understand YOUR kind of work, which I don't refute. That the book discusses about software engineers and how they can come to realize about managing the projects, the people and the respective environment/scenario. This book is for software engineers who have been "promoted" to be software architects - the manager of the project. This book is for you alright as it talks about the humanity in management of software projects. Re-read it as I think YOU haven't absorbed it.
So once again, your reasoning is flawed and futile to the thread. We are NOT talking about your work. No one is rebutting that software systems are not complex. No one is rebutting that your line of work could be a little bit more complex. But we are not talking about you. We are talking about OTHER people's line of work that could use a little more processing power. Not yours. So until you can get out of your reasoning around YOURSELF, try to imagine other kinds of work.
Instead of recommending a book to read, try this on your computer so you will understand my line of work. Obtain an uncompressed 8-bit video file sourced from SD and just play around with it. Apply effects, some titles. Lets see how much render time it takes in a G5 2.0 before you can view a few seconds of the clip. Try FCP4HD. Toss it in Shake or, heck, even AE6.5 and apply a few more filters. Try even viewing the file in AE without waiting for RAM preview. I'm not talking about your home user's DV codec. I'm not even talking about HDV or DVCPro HD. Those are for consumers/prosumers. I'm talking about a file size of 160GB of space is worth 2 hours, when that same file space could fit 12 hours of your average DV. And I'm not talking about editing in iMovie or Final Cut Express, because they don't have the capability to input, output or play those kinds of files.
Once again, I totally respect every person's work and if they are happy with what their current CPU can give then that's great. But if that's the only basis of comparison for this argument, then the argument is pointless. So please, before you go on teaching us. Teach yourself that there are other works outside besides yours.