the library needs a better name #798
danwinship
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
I've been referring to the project as 'ebpf-go' for a while, would that fit the bill? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It is hard to refer to this library in a discussion... You obviously can't just call it "ebpf". The string "
cilium/ebpf
" is theoretically unambiguous, but in actual usage it's quite ambiguous (and tends to imply "the eBPF code that is part of Cilium" rather than "the eBPF library that is produced by the Cilium project separately from Cilium". You end up having to say something like "Cilium's golang eBPF loader implementation" which is way too long...So anyway, a more codename-y name would be cool...
Beta Was this translation helpful? Give feedback.
All reactions