If you don't want this to happen, release software under a different licensing model.
In my view, if you believe it is unethical for someone to re-license your Apache code with their own proprietary license, then it shouldn't have an Apache license.
Taking a proprietary fork of an Apache licensed code base and creating an Enterprise product around it seems like a valid business move to me. My guess is that the "uproar" is not coming from the original project creators, but from outside community members who consider such things "anti-social" or whatnot, but I could be wrong.
I find the constantly closing down and shifting of services to be a slight annoyance but not really too impactful in my personal usage. For example, moving Google podcasts and YouTube music into YouTube has been a pretty sad degradation. But not really a deal breaker for me.
What I would never ever do is build a business on top of Google. They seem so cavalier about pulling the rug out from under you. I can only imagine if you have for example services running in Google cloud, how they would treat you if you were counting on a service that they thought wasn't worth it to maintain anymore. Shutting down apis that people were using like this just seems very on-brand for them to me.
We (SUSE) have extensive testing and quality control, if you are looking for something very stable. Leap is the version built out of the same bits as the enterprise version. The "Micro" part means it is smaller, transactional, and immutable. It's built for containerized and virtualized applications. You can install the nvidia OS bits in the OS, and then build a container with libraries.
So now that I picked Metabase, Superset is topping HN for no apparent reason. Why?
I don't think it's semi-abandoned. I had a brief interaction with the project in my previous job, and I found the community and the company to be reasonably engaged and responsive.
However, it has not alleviated any responsibility from me to be a good coder because I have question literally everything little dang thing suggests. If I am learning a new API, it can write code that works, but I need to go read the reference documentation to make sure that it is using the API with current best practices, for example. A lot of code I have to flat out ask it why it did things in a certain way because they look buggy inefficient, and half the time it apologizes and fixes the code.
So, I use the code in my (personal) projects copiously, but I don't use a single line of code that it generates that I don't understand, or it always leads to problems because it did something completely wrong.
Note that, at work, for good reasons, we don't use AI generated code in our products, but I don't write production code in my day job anyway.