[Isthatablackgsd]

Opening a terminal in admin window which means any commands you put in that windows will always have admin privilege, no matter what.

What does Sudo is to only provide the root/admin privileges for specific inputted command. Once it is done, it goes back to user privileges. This way, the terminal window didn't need to end the session to go back to user privileges.

[ikekkdcjkfke]

Why is admin privilidge even a thing? Ask for the god damn specific resource you want access to and I'll answer yes or no!

[dwattttt]

"Admin"'s identity is the resource you're asking permissions to use. If don't want identities, are you going to manually authorize every file that needs to be interacted with? For a recursive delete of thousands of files?

[LudwigNagasena]

You would authorize deletion in a specific directory.

[eviks]

Is that the shiny new capabilities based future that never arrives?

[gwervc]

That's a very slim proposition value, especially when multiple commands in a row require admin privileges.

[MattPalmer1086]

Sudo also allows you to control which commands can be elevated to admin.

It also lets you elevate to admin without knowing the admin password, you elevate with your normal account password. Effectively, some commands can execute as admin, but the user generally cannot.

So you can allow limited administration without giving everything away.

[whywhywhywhy]

Good thing they're keeping the admin terminal too so you can just keep using that.

Personally I think it's way more likely the admin command is the one off like installing something, changing a setting and then everything else before and between it are user commands that don't need to be in admin space most of the time.

[bigstrat2003]

That's like saying (in a Linux context) "sudo is dumb because you can just use su". The two tools have different use cases.