…what?
I’m always aboard the Microsoft hate train, but I don’t see how them adding sudo fits within EEE. Here’s an excerpt from microsoft/sudo on Github:
Obviously, everything about permissions and the command line experience is different between Windows and Linux. This project is not a fork of the Linux sudo project, nor is it a port of the Linux sudo project. Instead, Sudo for Windows is a Windows-specific implementation of the sudo concept.
As the two are entirely different applications, you’ll find that certain elements of the Linux sudo experience are not present in Sudo for Windows, and vice versa.
Despite sharing a name and features, they’re for two completely separate platforms and offer no interoperability. If MS decided to release their version of sudo for Linux, maybe we could talk about EEE. For now, all they’ve done is implement a useful tool from another platform into theirs, and that’s a (rare) positive for MS, even if this feature should have existed like 30 years ago.
mondoman712@lemmy.ml 9 months ago
Will this not dilute search results related to sudo? It’s minor but I think could be considered EEE.
BaldProphet@kbin.social 9 months ago
Sounds like a bit of a desperate reach to attach the EER label to this.
tabular@lemmy.world 9 months ago
Desperation is when there is no reason to think something can be done. I’m way past the stage of assuming honest intentions from M$. If this comes to bite us like EEE then shame on us.
BaldProphet@kbin.social 9 months ago
To be honest, it just sounds like you have an unnecessary chip on your shoulder.
Evkob@lemmy.ca 9 months ago
I can definitely see this argument, but I strongly suspect the inverse will be true; finding results for MS sudo which aren’t about Linux might be difficult.
After all, sudo has existed for a long time. Also, I assume over 90% of people who use Linux uses or has used sudo, whereas a tiny fraction of Windows users will ever use MS sudo.
bamboo@lemm.ee 9 months ago
Microsoft has done this already for tons of windows applications. For example, open up powershell and run “curl”. It’s a http downloader program, but not the one you think of, and the args are completely different. This has been the case for years, yet you can still find answers for curl problems by searching. I don’t see this being any different.