That is why the FSF invented just one GPL, and said everyone should use this one or later. Then when they invented another one, it was automatically compatible. This way, the license is compatible, and you don't have to give up any freedoms.

GPL and LGPL works for a lot of people, but becomes a persistent issue when porting to other OS. They both still become a contaminating license if you have to static link something, embed 3rd party blobs, or even use icons for a consistent user interface experience.

Having a less restrictive FOSS compatible license that doesn't obligate people to modify the general purpose libraries for their edge case has proven important.

GPL only truly makes sense if targeting an OS supporting shared-object library paradigms. This is part of the reason why 95% of commercial Applications are running in an emulated/wrapper on the nix platforms.

The year of the Linux Desktop is still a ways off, and the foundational library structures are under constant upgrade or permutation. Snap/Flatpak/AppImage and Docker/RancherVM were all designed to try and mitigate the compatibility chaos of perpetual nix Beta release cultures.

It has some advantages, but also a lot of disadvantages similar to the Butterfly Effect bugs when something with the same name slightly changes behavior. =3