As discussed on the call, here's who I think are the three audiences for bcc/BPF tracing:

A) Kernel hackers (~100): who would like the language to be easier, better errors, docs, etc.

B) Sysadmins/operators/senior devs (~5k): who will use the existing bcc tools (and edit some).

C) Everyone else (>50k): via dashboards/GUIs.

I'm pretty happy with where the toolset is for audience B. There's a few more tools I'd like to add (TCP internals and buffering, disk I/O internals), but a lot can be done now.

Audience A might be served by something like ply, or partially served by Sasha's multi-tools.