the current practice of programming for newest hardware, rather than for os minimums?
why develop an application that will force prospective customers to have the increased expense of upgrading thier hardware to use it? why not code the application to run on the lowest level of hardware that the target os will operate on?
This conversation is currently closed to new comments.
I don't think it's a case of software being written to fit the current hardware spec. I suspect it's more a case of efficient coding coming second place to functionality.
Many of the programmers of today want to use graphical tools to help them do whatever they want to do. Look at the mess frontpage makes of something as simple as an HTML page.
All programmers today owe Micro$oft big time for lowering expectations from software.
I remember a time when if your computer crashed, you had a hardware problem, not just a normal part of your day.
People aren't taught to be effecient in the processes, or in file storage.
That is part because the people that are teaching programming today are not programmers. They sit down and push out whatever crap the book tells them to, without ever questioning why.
My last "programming class" I had to take as part of my BA set was program design. We were given a problem, and when I gave my answer, it was half the code as what the book offered as the "correct" answer and then I had to explain it to the instructor and prove it would work. After that the response was what you would expect out of a TV series dumb blond of "oh, that would work".
More important to crank something/anything out on a schedule than to have a quality program.
I agree. The further removed from assembly code, the less likely code is to be efficient. With ease of use comes loss of efficiency. As you are aware, there is no "correct" programming solution to any problem. As long as the objective is met, there are varying degrees of efficiency. Also, being efficient in your use of code, is not the same as writing an efficient program.
Was just trying to show just how big it has gotten in less than ten years (barely).
I do not believe that it should be as huge as it is now, but when you stress timelines over quality you get Micro$oft products. Not always the best, just first (and if not first we will buy you out or run you out).
With modular programming to reuse code over and over, it is crazy that they let it get away like this.
We blindly accept that they are that bloated just because that is what it takes.
Anyone remember when programs and OS's came on floppies? I just found a box of win95 floppies the other day. Try that with XP? Won't be long and they will have to put them on DVD's.
Software that runs on the latest and greatest hardware has a marketing advantage over software that will run on less. (Even if the lesser software will run on the newer hardware.)
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
what do you think about
why develop an application that will force prospective customers to have the increased expense of upgrading thier hardware to use it?
why not code the application to run on the lowest level of hardware that the target os will operate on?