Well, distribution is the killer feature. More, it's inherent property of the platform (web).
Web devs are in full control of their whole stack (excluding the browser where you occasionally need to account for incompatibilities), have to maintain only one version of the app (no upgrade needed on client-side), are not constrained by the platform owner's policies (app store tax).
Yes, it's more limited than native technologies in other ways, so it's not an answer for every problem.
I'd argue that the risk of your own instance being inaccessible for whatever reason is significantly higher than GitHub or GitLab having a full outage.
All good, but without being actionable they're just vanity metrics that only get discussed during performance reviews. They don't provide any meaningful insights on how to improve actual performance in day-to-day work.
I wrote Elasticsearch CLI just to scratch my own itch, as for certain tasks I just prefer to stay in the terminal. It's written in bash, uses curl under the hood and provides zsh completions for index and alias names.
Web devs are in full control of their whole stack (excluding the browser where you occasionally need to account for incompatibilities), have to maintain only one version of the app (no upgrade needed on client-side), are not constrained by the platform owner's policies (app store tax).
Yes, it's more limited than native technologies in other ways, so it's not an answer for every problem.