It's a feature.

At least to me anyway.
Modify the terms of the open source license models to prohibit this fuckery.

They've been stealing tech and infiltrating universities to steal research for decades.
Our government in the US has finally wised up - almost under under duress it seems.
Spy balloons floating freely over the US didn't help public perception either.

Russia reliant on US tech?
Not so much anymore. They just march to a different beat.
For example - Russians still use tubes. Not because they're backwards - rather that tubes are immune to EMP.
Ponder on the implications of that. A couple of good EMP's detonated at strategic points - bwahahaha our nukes still work.

His was the original observations on perception and reality.
Oh wait, that's Western thought...

Company develops tech that Apple thinks would be nifty in its watches.
Billions in liquid cash reserves yet they steal it (probably convinced themselves it passed the "obvious test".
Little guy is so pissed he stakes his personal fortune on standing up for himself and the courts agree - Apple was naughty and should not profit off their banditry.
Apple cries in beer "it ain't fair" and rather than come to an agreement with the little guy, they throw a tantrum and throw out the tech.
Apple is so fucking cheap and every bit as bad as Microsoft about stealing tech and ideas while mowing down the legit innovators with lawyers.

When I was in college earning my BSCS, I programmed FORTRAN, LISP and Pascal on a CP/M Ferguson Big Board based computer for classwork.
Then I got an Apple II+ and used Apple Pascal which was a huge leap forward with graphics (which annoyed hell out of the TAs when I used those in my projects for some reason). Then it was out into the real world and several machine control projects written on a PC with Turbo Pascal.
Later I went to work for a company that wrote software for commercial loan servicing that used Turbo Pascal and later Turbo C++, then a major insurance company that used Delphi to write software for field enrollment using laptops. Delphi was very good for me in my career up to 10 years ago. I still get job offers for Delphi coding - maybe when I retire ;) So most of my career was spent in Pascal land with one excursion into Modula 2, COBOL, and quite a bit of .NET.

I was with a company in the very early 2000's that built industrial machines for test and assembly.
One project was Condor - a battery pack that could start a V8 Dodge RAM 5 or 6 times and could be recharged in 15 minutes.
They actually had potential buyers lined up for power tools.
Given technology at the time we couldn't make it work. A very simplified 50,000 meter explanation; the anode and cathode were ultra thin sheets of a proprietary alloy and used a proprietary paste. Thickness of the metallic sheets and the paste were critical parameters. The machines simply couldn't provide sufficient tension to get the thickness without tearing the membranes. They shelved the project and I often wondered if the patents were sold or languishing in a drawer somewhere.

Kinda like when a politician starts to believe his own bullshit?

Except they are all lifetime licenses.

There is a widespread culture on Stack Overflow that live for the moment they can pounce on someone for some minor infraction or not phrasing a question just so.
It can be a real PITA trying to get past some of these guardians of the correct posting protocols.
Damned shame those dicks are losing their venue... ;)
ChatGPT doesn't judge.

Legacy systems can be fun as they hearken to a simpler time.
That's also a weakness in that a legacy system in my experience involves folks reluctant to move on and can be somewhat hidebound and resistant to change.
You end up being a maintenance programmer which is a job with a very low level of respect and flexibility. By the time you get tired of *that* crap, you've probably fallen behind the curve with current tools and are less desirable in the job market.
So IMHO be careful as it can be a one-way street. You need to have full awareness of what's at the end of that path.

I have one as well. I designed a WonderWare SCADA system for a new generation of orange juice processing plants in southern Florida. We were pulling wires and coding simultaneously while they were bolting the hardware together. Very often they would cut a control wire and we were dead and didn't actually know it.
So I coded a little radar sweep animation on the screens to tell us we still had a signa.
Come production my engineering manager with zero sense of humor told me to "take that stupid radar off".
So I did and then the uproar from the folks that we'd trained to use the SCADA system because they *liked* the little radar screen.
Sidenote: Alan Cooper wrote a book "The Inmates Are Running the Asylum" where he makes the case programmers should have no part in designing a UI because we do shit like this :)

As an engineering student I was required to take an advanced calculus class.
The professor saw himself as a math purist and did his level best to flunk all non-math majors.
His first statement; "The prerequisite for this class, is this class".

AI lawyer - meet AI Judge.
It could be argued this is a good thing.