Sure because Error Code 0x8007057 tells you immediately how to solve the problem.
Linux error messages like error: kex_exchange_identification: client sent invalid protocol identifier "GET /robots.txt HTTP/1.1"
are completely arcane tough.
I support both systems. And Linux support is so much easier. Mostly in runs out of the box. If it runs I continues to do so and If you have an error you get a specific message like above.
With such a message you either:
See right away how to solve the problem
Search it online and get a specific solution for exactly you problem
Or you can ask Experts for a solution for your specific problem.
With Windows:
No systems runs out of the box, I always have to install additional software (7zip, sane browser, …) and also for anybody remotely privacy concerned have to adjust many settings (for which tools exist thankfully)
If an error occurs under Windows and I get a code like above:
I can sometimes guess by my experience what the reason is and solve it.
If not I search the error code and circumstances which lead to it online, then apply the 20 solutions presented one by one in hope one works
Ask experts which ask me to run a bunch of diagnostic utilities because the error message does not tell you anything. (Yes by now I can also guess which utility could provide relevant information, but not because Windows told me)
In a noticeable amount of cases the solution is: We can not determine the reason for the error, please reset everything (First a restart, then run this cleanup tool and if this doesn’t help just reinstall!)
I agree those kinds of arcane windows errors suck worse than they do in Linux. But I get those errors so rarely on either system.
In Windows, I’ll have something happen like my windows won’t remember their last position when I unlock.
In Ubuntu I’ll have to restart my Bluetooth service every week or so. Or sometimes the update-software modal will not take focus or accept mouse/keyboard input until I reboot. Most recently I had an app from the official app store fill up my entire partition because it spammed syslog, which broke my credentials cache, and I couldn’t even log in until I made a temporary sudo user and emptied syslog.
None of these are super difficult, but they also don’t provide error messages.
My experience is summed up as:
-If it is broken in Linux, I will have to fix it, but with knowledge the errors are diagnosable and reparable
-If it is broken in Windows, it has a decent chance that it will fix itself. However once it fails to fix itself, then it’s maddening to figure out how to repair it leading to the “screw it, just reinstall”
So if neither one breaks, congratulations, they both seem pretty solid.
If a fairly common breakage occurs, Windows looks weird but it fixes itself, Linux meanwhile bleats what is an arcane error to a non-tech person, maybe refusing to boot.
If a really stubborn breakage occurs, advantage back to Linux as at least a skilled person has a chance of repairing it.
Sure because
Error Code 0x8007057tells you immediately how to solve the problem.Linux error messages like
error: kex_exchange_identification: client sent invalid protocol identifier "GET /robots.txt HTTP/1.1"are completely arcane tough.I support both systems. And Linux support is so much easier. Mostly in runs out of the box. If it runs I continues to do so and If you have an error you get a specific message like above.
With such a message you either:
With Windows: No systems runs out of the box, I always have to install additional software (7zip, sane browser, …) and also for anybody remotely privacy concerned have to adjust many settings (for which tools exist thankfully)
If an error occurs under Windows and I get a code like above:
I agree those kinds of arcane windows errors suck worse than they do in Linux. But I get those errors so rarely on either system.
In Windows, I’ll have something happen like my windows won’t remember their last position when I unlock.
In Ubuntu I’ll have to restart my Bluetooth service every week or so. Or sometimes the update-software modal will not take focus or accept mouse/keyboard input until I reboot. Most recently I had an app from the official app store fill up my entire partition because it spammed syslog, which broke my credentials cache, and I couldn’t even log in until I made a temporary sudo user and emptied syslog.
None of these are super difficult, but they also don’t provide error messages.
7zip built in now, and edge is decent
My experience is summed up as: -If it is broken in Linux, I will have to fix it, but with knowledge the errors are diagnosable and reparable -If it is broken in Windows, it has a decent chance that it will fix itself. However once it fails to fix itself, then it’s maddening to figure out how to repair it leading to the “screw it, just reinstall”
So if neither one breaks, congratulations, they both seem pretty solid.
If a fairly common breakage occurs, Windows looks weird but it fixes itself, Linux meanwhile bleats what is an arcane error to a non-tech person, maybe refusing to boot.
If a really stubborn breakage occurs, advantage back to Linux as at least a skilled person has a chance of repairing it.