It won’t ever. It’s been very close for the last 10 years. It won’t ever be 100%.
A great example right now is “How do you see what driver your device is using?”
In Windows that’s going to device manager -> display adapters -> your device-> properties. Easy and can be easily discovered by thinking “I need to know what driver is running what device” and then going to look for a device manager, and following the trail.
In Linux that’s potentially lspci or lsusb or lshw or a combination of each with their own arguments. Linux fails almost instantly because you have to type a command. Windows treat the user with respect for their time and don’t tell you to stare at a man page for 10 minutes trying to figure out the exact arbitrary letters to add as arguments to some archaic command.
This is been a problem for decades. There are third-party GUIs that don’t tell you the driver being used or tie things together like they show the device but not the driver or not allowing you to manage the driver and aren’t included with most distros, so aren’t discoverable.
Waiting for Linux is a fool’s errand at this point.
Windows treat the user with respect for their time and don’t tell you to stare at a man page for 10 minutes
When I run across Error 0x0000011b or whatever, and there’s no official documentation on it, it doesn’t feel much like respect for my time at all. I’d sooner stare at a man page for 10 minutes than dig through every Microsoft support forum post and try every weird arcane fix.
It won’t ever. It’s been very close for the last 10 years. It won’t ever be 100%.
A great example right now is “How do you see what driver your device is using?”
In Windows that’s going to device manager -> display adapters -> your device-> properties. Easy and can be easily discovered by thinking “I need to know what driver is running what device” and then going to look for a device manager, and following the trail.
In Linux that’s potentially lspci or lsusb or lshw or a combination of each with their own arguments. Linux fails almost instantly because you have to type a command. Windows treat the user with respect for their time and don’t tell you to stare at a man page for 10 minutes trying to figure out the exact arbitrary letters to add as arguments to some archaic command.
This is been a problem for decades. There are third-party GUIs that don’t tell you the driver being used or tie things together like they show the device but not the driver or not allowing you to manage the driver and aren’t included with most distros, so aren’t discoverable.
Waiting for Linux is a fool’s errand at this point.
When I run across Error 0x0000011b or whatever, and there’s no official documentation on it, it doesn’t feel much like respect for my time at all. I’d sooner stare at a man page for 10 minutes than dig through every Microsoft support forum post and try every weird arcane fix.