It hasn't caught up yet, but it's getting pretty close. Although I'd think about it in terms of three dimensions: - technical capability: we should pass it thi

It hasn't caught up yet, but it's getting pretty close. Although I'd think about it in terms of three dimensions: - technical capability: we should pass it this year. We'll be technical capable of solving pretty much the same issues and then some. - ease of use for script developers: bcc is currently ~10x more verbose to program. ply is much easier, but that project is in its early stages. This won't matter that much for Netflix, since much of the time staff will use this from a GUI (eg, Vector). It also won't matter that much for people who use the many provided tools, like opensnoop, tcpconnect, ext4slower, etc. It matters most for whoever codes the GUI and those tools (eg, me). - marketing, awareness, brand: Sun marketing, sales, trainers, and evangelists, did an awesome job - everyone knows about DTrace, even if they've never used it. In comparison, bcc/BPF (and many other Linux kernel technologies, like ftrace) have virtually zero marketing budget or professional marketing staff promoting them. Awareness will take the longest to catch up. I also summarized the current state of bcc/BPF in http://www.brendangregg.com/blog/2016-03-28/linux-bpf-bcc-road-ahead-2016.html http://www.brendangregg.com/blog/2016-03-28/linux-bpf-bcc-ro...