Show HN: Write your BPF programs in Go, not C
1–10 of 58 posts
Re: Show HN: Write your BPF programs in Go, not C
#2Re: Show HN: Write your BPF programs in Go, not C
#3Re: Show HN: Write your BPF programs in Go, not C
#4Re: Show HN: Write your BPF programs in Go, not C
#5I'm not really sure why you'd want to use this. If you're writing eBPF, you already need to know how to read C kernel source.
Re: Show HN: Write your BPF programs in Go, not C
#6What is BPF?
Re: Show HN: Write your BPF programs in Go, not C
#7What is BPF?
Here you go: https://github.com/pratyushanand/learn-bpf
Re: Show HN: Write your BPF programs in Go, not C
#8What is BPF?
This is why National Aeronautics & Space Administration (NASA) guidance is the following:
> Acronyms often confuse readers. Avoid them whenever possible. If an acronym is necessary for future reference, spell the full word and follow with the acronym in parentheses on the first reference. For example, The General Services Administration (GSA).
https://nasa.github.io/content-guide/abbreviations-and-acron...
There is also this longer memo on the NASA Technical Reports Server: https://ntrs.nasa.gov/citations/19950025292
Re: Show HN: Write your BPF programs in Go, not C
#9What is BPF?
I'm guessing Berkeley Packet Filter: https://en.wikipedia.org/wiki/Berkeley_Packet_Filter This is why National Aeronautics & Space Administration (NASA) guidance is the following: > Acronyms often confuse readers. Avoid them whenever possible. If an acronym is necessary for future reference, spell the full word and follow with the acronym in parentheses on the first reference. For example, The General Services Admini…
Not quite as much as Radar or Laser, but halfway there.
Re: Show HN: Write your BPF programs in Go, not C
#10Sorry, why wouldn’t I write in the native language?