[mmclean]

Regarding Google Cloud Profiler (I'm the PM), this is for a few reasons:

- We have good support for Go, Java, JS, and Python, but are still adding a few features for these languages (MUSL support for Alpine just shipped, still need to add heap profiling for Python)

- C++ isn't as heavily used by our ops tools customers as Go, Java, JS, and Python

- We have several new analysis features in the pipe, and the cost supporting an additional language would slow down the delivery of these

There's no lack of desire to add new languages, but we chose to prioritize completing existing language support and new analytics functionality this year. I'm guessing that the other teams making products in this space face similar constraints and made similar tradeoffs.

[jeffbee]

Thanks for your perspective. When I was at dropbox I wrote a quick tool that would convert perf data files to cloud profiler protobufs and upload them to google. I really appreciate that the API exists allowing people to use whatever language they want. I'm not a huge fan of the datadog model where you need their agent and they don't have a documented API.