"Our purpose is to peacefully disrupt Dorsey’s talk" then do it outside, that is where your Protest belongs and where you actually have a right to protest. Obviously anyone who comes to an event with the goal of disrupting that event needs to be removed or just not let in.
It seems extremely uncontroversial to ban everyone involved in the planned protest from attending.
From https://fosdem.org/2025/faq/#registration
> Q: I plan on visiting FOSDEM, where can I register?
> No registration is required.
> Q: How much does a entry ticket for FOSDEM cost?
> Attendance is free, including access to all talks and facilities.
Sorry if it seems not empathic enough, that was not my intention. I know that the use of such drugs may be medically necessary.
Edit: To serious answers: I was wrong, I stay corrected.
No, you can't, and it's not even close.
You have a header file that's 2000 lines of code, and you have a function which uses type X. You want to see the definition of type X. How do you quickly jump to its definition with your "any old text editor"? You try to grep for it in the header? What if that identifier is used 30 times in that file? Now you have to go through all of other 29 uses and hunt for the definition. What if it's from another header file? What if the type X is from another library altogether? Now you need to manually grep through a bunch of other header files and potentially other libraries, and due to C's include system you often can't even be sure where you need to grep on the filesystem.
Anyway, take a look at the docs for one of the most popular Rust crates:
https://docs.rs/regex/1.11.1/regex/struct.Regex.html
The experience going through these docs (once you get used to it) is night and day compared to just reading header files. Everything is cross linked so you can easily cross-reference types. You can easily hide the docs if you just want to see the prototypes (click on the "Summary" button). You can easily see the implementation of a given function (click on "source" next to the prototype). You can search through the whole public API. If you click on a type from another library it will automatically show you docs for that library. You have usage examples (*which are automatically unit tested so they're guaranteed to be correct*!). You can find non-obvious relationships between types that you wouldn't get just by reading the source code where the thing is defined (e.g. all implementations of a given trait are listed, which are usually scattered across the codebase).
> I don't know if rust doc suffers the same issues, but the tooling you are mentioning just seems to add an extra step (depending on how you count steps I suppose, you could perhaps say it is the same number of steps...) and provide no obvious benefit to me (and it does provide the obvious downside that it is harder to edit documentation when you are reading it in the form you are suggesting).
Why would I want to edit the documentation of an external library I'm consuming when I'm reading it? And even if I do then the effort to make a PR changing those docs pales in comparison to the effort it takes to open the original source code with the docs and edit it.
Or did you mean editing the docs for my code? In that case I can also easily do it, because docs are part of my source files and are maintained alongside the implementation. If I change the implementation I have docs right there in the same file and I can easily edit them. Having to open the header file and hunt for the declaration to edit the docs "just seems to add an extra step" and "and provide no obvious benefit to me", if I may use your words. (:
^struct whateverAh, the benefit of having a Chinese CEO, they tend to want less public attention to themselves. "Man don't want to be famous, like pig don't want to grow big" as people say.
That, plus the fact BYD's founder/CEO (same guy) was not as flashy (reads "Unhinged") as Elon Musk.
The reason that I'd never use YT Music is that I never trust anything from Google: their interfaces are ugly, everything's user-unfriendly, and they have the habit of discontinuing a service at any time. Also it has the impression of not really being well-thought as a product: why name a music service after a video service? I know it's not the case but it always reminds me of those low quality music playlists where people collected low quality unofficial music videos back then in YT just for the music: simply not the right tool for the job.
It may seem stupid or counter productive, but it is easy and good enough. YT Music is a clear upgrade for those users.
I think YT Music makes more sense than many of the Google initiatives and it will continue to make sense as long as they will have deals with music labels.