Who buckles first likely depends on the parties involved. Linux maintainers can be pretty insistent with their interface design (cf. the recent Rust drama), so

Who buckles first likely depends on the parties involved. Linux maintainers can be pretty insistent with their interface design (cf. the recent Rust drama), so I could just as easily see a status quo where these eBPF hooks continue to be available, but almost everyone steers clear of them due to their instability, except for ad-hoc things like SystemTap scripts. (The social contract in these sorts of projects goes both ways: maintainers usually get a lot of leeway to force devs to adapt to changing APIs or requirements, but the devs will start running off if it's done too frequently and drastically. Unless the maintainer has a monopoly on end-users, like Apple, or enough of a cult of personality to cast everything as the devs' fault for not keeping up.) (There's also sometimes a third option, where the project has become so entrenched that devs keep using it but stop updating it, like Java 8 or Python 2. This often causes much consternation among maintainers, occasionally to the point of inserting active mechanisms to punish devs who don't update.)