Hackers solve challenging problems whose solutions are not clear. This is not a challenging problem, and the solution was obvious. This is not an example of curiosity being explored.
Hey man I read your profile and you sound wise (according to my pre-existing biases). Just curious, what API/platform do you use for your trading bots?
Saying Silicon Valley is dead is like saying the earth is dead. Saying Silicon Valley is in trouble is like saying the earth is in trouble.
It's just irrational agenda-oriented FUD. The earth is not at any serious risk of death and neither is Silicon Valley.
What is at risk is his culture. Unfortunate? Yes, but apocalyptic? No. What is happening in SV is part of a cycle. Change is normal and is due to economic and population dynamics. After the boom it will bust and then it will boom again and so on and so on.
People who are afraid of change and long for the "old days" are irrational and not living in reality, have not accepted it. Out here in reality, things change.
Sure but how common is that case? How common are multi-tenant Linux systems with untrusted users that give those specific permissions? Do you want untrusted users sniffing the packets of others?
I'm not sure this argument makes sense. Avoiding accidentally crashing the kernel doesn't require a BPF layer.
For instance, you could just write your kernel module in a sufficiently safe language, like Rust, and have the same benefits. You could even pre-compile eBPF for the exact same level of safety. Still no need for the bpf() system call or the eBPF VM or JIT in the kernel.
I'm confused why BPF exists in the first place. Can't we just compile kernel modules that hook into the tracing infrastructure?
It seems like a webassembly for the kernel but local software has the benefits of knowing the platform it is running on. I.e. Why compile C code to eBPF, when I can just compile to native code directly?
I can potentially see it solving a permissions problem, where you want to give unprivileged users in a multi-tenant setup the ability to run hooks in the kernel. Is that actually a common use case? I don't think it is.