1 Dec
2013
1 Dec
'13
11:29 p.m.
On 02.12.2013 3:02, Colin Finck wrote:
I have to ask, considering all the complications and
disadvantages such
a system would bring and all the work that has been put into our own
drivers over the years: Why is it absolutely necessary to replace our
existing drivers by MS example code wherever possible?
We would just drop a bunch of unknown code into our OS then, which may
or may not work properly depending on the current state of ReactOS.
It's not
"unknown code". It's a code which is proven to work, and which
works in millions of computers. Developing same driver as, say, fastfat
would require so much wasted man power that I don't even want to think
about that, when there is a ready piece of code waiting to be used.
And the whole point is to make ReactOS around the good working apps and
drivers, not vice versa.
To conclude, our existing fastfast totally sucks. cdfs does too. Fixing
them is a waste of time. Rewriting them - good project, but noone will
use that driver. You won't get any testing. Everyone uses NTFS nowadays,
and when it comes to FAT, noone in their sane mind would use our driver.
Microsoft's one is just good enough, fast, native, whatever.
Regards,
Aleksey Bragin