This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments. https://github.com/PowerShell/PowerShell/pull/1901
OpenBSD's team has already reacted and added Word to OpenBSD
Sudo for Windows
291–300 of 439 posts
Re: Sudo for Windows
#292How do you wax lyrical for an entire article about the excellently engaging ergonomics of sudo and not mention Linux/Unix family of OSes
Re: Sudo for Windows
#293I've tried several times to code on Windows. It's nearly impossible for a person used to Unix based systems. Seems it's getting slightly better. Nice.
Re: Sudo for Windows
#294Windows tries to improve the developer experience… why not call it wudo or something funny since devex on windows is obviously a joke.
I agree. Can pretty much generalize to Windows and not just Windows devex at this point. The OS is like a parody of itself.
Re: Sudo for Windows
#295Earlier quoted context omitted.
I think they should've named it something else to avoid confusion, especially if it doesn't have the same behavior as unix sudo. If it has different arguments and features, imagine the confusion of unsuspecting users searching how to use sudo in the future.
> especially if it doesn't have the same behavior as unix sudo... imagine the confusion of unsuspecting users searching how to use sudo in the future. It's hard to imagine a company that size would name it so deliberately without realizing it would cause confusion in search engine results and such. A good faith assumption would be they wanted to make Windows more familiar to users of both but it also means that Windo…
So it's just some black hat SEO to seem more relevant to Linux users?
Re: Sudo for Windows
#296Considering the way PowerShell commands go, I assume this will be: RunWithAllTheElevatedPermissionsPossible --YesEvenThose .\inthisfolder.folder\. grep : The term 'grep' is not recognized....
It's evident that you haven't used PowerShell. Almost all commands in PowerShell have short aliases. For instance, instead of typing 'Get-ChildItem', you can simply use 'gci', which stands for the first letters of each word. Unlike Bash and other shells, where you must learn various Domain-Specific Languages (DSLs) to handle XML, JSON, YAML, etc., PowerShell allows you to use its native language to work with any data…
lol
Re: Sudo for Windows
#297Here's hoping that "Windows 12" will be just a Window manager + Desktop running on Linux, with all existing bugs meticulously replicated to maintain backwards compatibility with Windows 95/7/8/10/11.
To be fair that would still make windows instantly so much better if you could actually run a less weird desktop environment AND run all the vendor locked software.
Re: Sudo for Windows
#298Earlier quoted context omitted.
> the least painful way to develop for Windows on Windows is to just use Linux Eh? Even as a joke, I don't get it. 1. Download Visual Studio 2022 Community Edition 2. Select and install the workloads you need 3. Fire up any boilerplate from the Welcome menu 4. Press the green play button Sure, it's no `pacman -S base-devel && g++ main.cpp && ./a.out`, but it's not as bad as everyone puts it. It is a GUI-first operati…
Replying to > All MS is trying to do [with WSL] is make it easier for developers to develop on Windows for Windows, which it has ample incentive to do both internally and externally. > if you want to write a fast, HiDPI-aware Win32 application today that supports everything from Windows XP to Windows 11 that's I said "least painful", not impossible. The scenario you describe here would be very painful.
> The scenario you describe here would be very painful
On the contrary, it couldn't be easier. Visual Studio comes with a Windows XP platform toolset[1] that is a one-click install.
Compare, on the other hand, how ridiculously hard it is to develop targeting older glibc on a newer glibc host. There's no way around it except to use a Docker container (which IMO is equivalent to using a sledgehammer on a tiny nail).
[1]: https://learn.microsoft.com/en-us/cpp/build/configuring-prog...
Re: Sudo for Windows
#299One day they'll replace the kernel with Linux and nobody notices
Unlikely. Windows is all about compatibility and that includes all the weird things accumulated in windows over the decades. There is not a real incentive to change this. Think of all the gamers, custom hardware like ATMs and commercial terminals that run on Windows. That’s a huge market.
Old windows software often runs better or only with Wine instead of recent windows versions. So if they want to keep their 'compatibility' long term, they have no choice but to to include (or worse, fork) wine.
Re: Sudo for Windows
#300Yep, it's really happening. Sudo is coming to Windows. It's obviously not just a fork of the linux sudo - there's enough that's different about the permissions structure between OS's that just a straight port wouldn't make sense. But the dream of being able to run commands as admin, in the same terminal window - that's the experience we're finally bringing to users. I've been working on this for the last few months n…
didn't runas exist for ages?