GPL-3 is an attempt to keep businesses out of the open source ecosystem.
As far as using libraries that are GPL, a company can if they want. If the application isn't distributed outside of the company, GPL is technically fine. But there is so much fear around the legal implications of GPL that most companies choose to avoid it entirely. A lot of VC/angel investors even explicitly forbid it for startups they invest in. The company I work for has CI licence checks and we've had to remove or rewrite some components because they missed a transient GPL library.
As far as releasing code as GPL, I think a lot of companies would have benefited from AGPL. AGPL code can't be added to your internal tool without you also open-sourcing the internal tool, even if it's never intended to be released or distributed outside of the company. Instead of going for AGPL, companies like Elastic and Redis created their own licenses, that were condemned as not actually open source and will never be OSI approved. It really comes down to revenue. Google/GCP and MS/Azure were paying the enterprise fees for Elastic, but Amazon wasn't. AGPL would mean no one would need to pay the fees so long as they released all their modifications/patches. It didn't work of course. Amazon just forked it and made OpenSearch, and now that's the one being included in most Linux distros.
So I guess you're right that GPL-3 has kept business out of that sphere of open source, but I'm not sure if that was at all the
intent.
It's funny how "master" as a name for an SVC branch is such a problem while "scrum master", a title given to an actual person, is all OK. It's almost like these cowards lack the spine to cause issues with their employers in real life.
I haven't heard anyone being called a "scrum master" in nearly a decade. I don't think anyone cares because it's an outdated term. If it wasn't, you could be sure someone would open their bitching hole about it.
Given the lengths Oracle went to claim the copyright over APIs, and the lengths SCO was going until its case imploded (they claimed the linux headers were their copyright code), it's a good thing the exception was made, because otherwise the interface problem would have been used to kill Linux. It would also heave wrought havoc in the industry at large if syscalls could be claimed as copyright. The legal status of every piece of software in existence would be called into question.
Even though Kiwistan (New Zealand) is an authoritarian hellhole where the government is legally allowed to spy on all citizens (see: Kim Dotcom) and has no freedom of speech, one of the things they got right was banning software patents. I know patents are different than the copyright issues in the Oracle/Java case, but I do think things would get better in the software world if globally a company couldn't have exclusive ownership to the design around clicking on a button.