e.g.
https://github.com/react-ga/react-ga
Why do you need framework specific libraries on top of that?
If someone set up a Scroogle Analoytics which had a simple code snippet, was free, and had near-identical looking dashboard, I'd use it.
(Disclosure: I work for Google, and have run Google Analytics on my site since before I joined)
With GA, I can do none of that; it's just a massive unreadable blob I can only load from the GA servers. I just have to trust Google doesn't do anything I don't want (including XSS, but also other issues). It's not even easy to figure out what information exactly it collects last time. It's very untransparent and un-auditable and the website equivalent of loading binary kernel blobs.
How true is this? There's popularity, and there's significance in the face of Photoshop's market hold. I'd love to believe there's some significant dent being made in Adobe's market share here, but I doubt it.
If your boss asks you for some analytics about site usage the first thing searching the web will turn up is GA and you can have it set up on a test env in less than half an hour including acquiring an API key and reading enough docs to configure it.
Nobody would pay for Photoshop if it didn't provide value.
For photo retouching, I prefer Affinity Photo. One thing I especially appreciate about it is how efficient it is at handling large, 16-bit-per-channel images with many layers.
Photoshop is useful to have around mainly because it makes it somewhat easier to work with certain kinds of PSD files that I get from other people.
My mate worked at Yahoo, and they used Yahoo Analytics, and he said it was great, but that when you ran into any issues at all, good luck working out what to do!
The reality of an analytics product is that a non-techy marketing person needs to be able to solve their own issues without wasting tech time (which is the only reason why TagManager exists), and that's a REALLY hard problem to solve.
Tbh, I disagree. While a lot of the above is true, it's largely popular because it's a recognisable brand, and because the majority of frontend devs are already familiar with it and haven't felt the need to explore an alternative (network effect).
While an alternative does really need to be free and easy to implement, it also needs to address the above two hurdles, which is a tough ask.