We are stuck with egrep and fgrep (unless you like beating people)
There seems to be a lot of confusion in this discussion about what the change is and how egrep and fgrep work. These are not symlinks like some have suggested but rather shell scripts. You can see the exact commit diff here:<p><a href="https:&#x2F;&#x2F;git.savannah.gnu.org&#x2F;gitweb&#x2F;?p=grep.git;a=blobdiff;f=src&#x2F;egrep.sh;h=a0d1694eccb00943322fc561f4f26dbf979a22ad;hp=6d6c15a84cfea465055bf258afe88404350162fd;hb=a9515624709865d480e3142fd959bccd1c9372d1;hpb=e87ccc7038d4f44f4601b3e8775fef09b1420dff" rel="nofollow">https:&#x2F;&#x2F;git.savannah.gnu.org&#x2F;gitweb&#x2F;?p=grep.git;a=blobdiff;f...</a><p>I remember around ~10 years ago being told &quot;you should never use `egrep` because it is slower than `grep -E`.&quot; precisely because the former requires extra forks() compared to the latter. However I&#x27;d counter that advice saying &quot;if you&#x27;re concerned about the performance of forks() then why are you running your code as a shell script to begin with?&quot;... and I stand by that assessment now. In fact it would probably take me longer to type `-E` than it would for any modern system to run fork() (and I&#x27;m sure as hell not planning on using `grep` inside any hot loops!)<p>I think what will likely happen here is that distro maintainers will either remove that warning themselves or take ownership of the `egrep` and `fgrep` shell scripts. I&#x27;d be surprised if that warning made its way to the mainstream distros. I also wouldn&#x27;t be surprised if the GNU grep maintainers did a u-turn on this change -- though it has already been committed to git for more than a year now and this is the first I&#x27;ve heard people complain about the change.