If you read the article you would know this is a regression, not an improvement. Stuff breaking silently is never good. If you change config options error when you read the config file that no longer works.

▲ jeroenhd 3 days ago | parent [-]

It's not a regression, it's a documented, deliberate decision to change the behaviour of the program.

    The sudo-rs 'sudoers' manual page suggests that this is a deliberate decision, which makes the Rust version of sudo very definitely not a compatible implementation. The manual page has a nice full section and description of 'Wildcards', and then at the end casually says:
    
    > Wildcards in command line arguments are not supported—using these in original versions of sudo was usually a sign of mis-configuration and consequently sudo-rs simply forbids using them. The only supported use is ‘*’ as the final argument to indicate “zero or more subsequent arguments as noted above.

The manual should probably drop the wildcards section it's not implementing anyway, though.

	▲	throw0101d 2 days ago \| parent \| next [-]
		> It's not a regression, it's a documented, deliberate decision to change the behaviour of the program. If I install and setup and run "sudo" I expect it to work like sudo. If you want your program to not work like sudo do not call it "sudo". This is what the OpenBSD folks did with doas. POLA. (It's fine if they want it to work differently than sudo; not fine that they called it "sudo".)
	▲	graemep 2 days ago \| parent \| prev \| next [-]
		Maybe a deliberate decision in sudo-rs but its a silent failure when Ubuntu is upgraded so its a regression in Ubuntu.
	▲	dmitrygr 3 days ago \| parent \| prev [-]
		And when one upgrades and OS and something that worked since 1980 stops working, what do we call that, class? That’s right. “A regression” Whether it was accidental or purposeful changes nothing.