Tweet
Programmer considerations
Here we go.
I believe that OOP is somehow a poor performance generator, so I think that writing driver code for a video card is not done with objects having in mind to reuse code.
But I believe, too, that programming drivers, utilities, and so on for over a year is not a work that should be thrown away.
And I believe, last(uhmm..not sure this word goes here, please, correct me), that Matrox is not so stupid...
Er...it's not too clear my tought, uhu?
Well, in other words, I have started asking myself why, with upcoming new videocards, the Matrox programmers should loose their time writing driver and utilities for an old videocard.
For example, the new utility that enable switching between AGP mode. Haig said that the techies are going to implement a lot of new feature in that utility.
Why this?
Well, simply because G800 will be a dual G400...
Sorry for the long delirium...
------------------
Italian Guy, Bad English
D'ya want an Italian version?
I believe that OOP is somehow a poor performance generator, so I think that writing driver code for a video card is not done with objects having in mind to reuse code.
But I believe, too, that programming drivers, utilities, and so on for over a year is not a work that should be thrown away.
And I believe, last(uhmm..not sure this word goes here, please, correct me), that Matrox is not so stupid...
Er...it's not too clear my tought, uhu?
Well, in other words, I have started asking myself why, with upcoming new videocards, the Matrox programmers should loose their time writing driver and utilities for an old videocard.
For example, the new utility that enable switching between AGP mode. Haig said that the techies are going to implement a lot of new feature in that utility.
Why this?
Well, simply because G800 will be a dual G400...
Sorry for the long delirium...
------------------
Italian Guy, Bad English
D'ya want an Italian version?