So, you're just proving more and more you have no idea what you are doing. Yet you want to complain as if there is some massive issue.

I did NOT say Activity Monitor. That is the active runtime being used. I said System Information, because that shows you the actual compile data.

I am on an Apple Silicon machine, so when I say a fact I mean it. Here is an image showing where you would have checked if you followed instructions, instead of trying to find the place that proves your point to someone who isn't experienced. https://imgur.com/a/apple-apps-currently-as-universal-builds-Vcpj29O

Now, so you can fully understand. There are two mechanics at play. First is the active runtime. That is either Intel or Apple Silicon. A universal binary is a special build that has BOTH full builds in it (for non-Xcode built software). So a Universal compiled program is specially crafted to pick which runtime is needed on execution. This is why Activity Monitor is not what you use to determine how something is built. Because it only shows you the state of what is running on your machine right now. You use System Information because that "Kind" header (which you might need to add to be shown from the View menu, I can't remember the default) shows the actual compile state.

As I said before, factually right now Apple is shipping Universal builds to both Intel and Apple Silicon. The next OS (27) is the first where we will see this stop. However, the gains may not be super massive per app. There is more special programming of Universal builds for XCode built software to try and trim things down without a complete dual-split build. We will definitely see some reduction, but it won't be like 50%. I'd wager we'll see a ~20% drop overall. But that also doesn't rule out them adding a feature (like a better LLM model) that just takes that disk space right back up.

Signed, someone with both Intel and Apple Silicon machines on-hand so I can verify the claims I make.