2 ms·
If the GNU folks want to remove the wrapper scripts, they can. It's their software and they write the best practices for it. Distro maintainers can still ship
by jeroenhd 4y ago
If the GNU folks want to remove the wrapper scripts, they can. It's their software and they write the best practices for it.
Distro maintainers can still ship these scripts. They can add aliases to the user profile to do the same thing without having to launch a sh instance. Maybe they'll add a second package, grep-utils, that just contains the wrapper scripts so you can choose between GNU's position and the "I don't like change" position.
Microsoft has deprecated and removed tons of stuff and so did browsers. Vista crashed so often because Microsoft did away with their entire driver model and vendors wrote quick wrappers around their old, crappy drivers and shipped those. Many remaining browser features are reasons why web development sucks so much ("quirks mode" for one) and Java not breaking compatibility has given it many problems that dotnet solved by breaking compat once. Java also has removed several deprecated packages and moved them to libraries instead (like Nashorn).
Deprecated means "if we see a reason to remove this, we may remove this in the future". It's no guarantee for removal but it's no guarantee for being kept around either.
- kentonv 4y ago> If the GNU folks want to remove the wrapper scripts, they can. It's their software and they write the best practices for it. I'm not making any argument about the maintainer's rights. I am making an argument about whether it was a good technical decision. > [people can work around it] That doesn't make it a good idea, though. > Microsoft has deprecated and removed tons of stuff and so did browsers. Only when there was a real benefit deemed greater than the cost. In this case there is essentially no benefit whatsoever to the change, except some abstract notion of cleanliness or pedantic spec compliance.