Earlier quoted context omitted.
and not really anybody else, because the rest haven't really figured it out yet. I beg to differ there. ;) I work on Skylight ( https://www.skylight.io ) which is definitely doing some interesting stuff in the APM space. By focusing on just Rails, we are able to provide features that other services that try to be a jack-of-all-trades frequently miss. For example, we just rolled out a feature that helps you monitor me…
Conversely by focusing on just rails, you effectively eliminate large swaths of the enterprise market. There's a huge opportunity there for someone who can integrate across platforms and technologies, particularly if you can ship a behind-the-firewall solution.
Focusing on Rails lets us build a really awesome end-to-end solution that works out of the box. Building an intuitive, explorable interface means constantly considering the application's context, and I can attest to the fact that every time we do UI, nitty-gritty details about how our customers build their applications can often become the dominant consideration. When I use general-purpose solutions that are designed for "all languages and platforms", I am often very frustrated by the resulting lowest-common-denominator APIs and UIs.
We may eventually build versions of Skylight for other platforms, but if we do, we will apply the same level of care and design for other platforms as we have done for Rails. Among other things, that will mean having team members who have written large applications in those platforms, and letting those team members drive the APIs and design for those platforms.