the problem with telemetry in open-source applications is that the majority of people who use them don't tell anybody about their workflow, so whenever you change something, you have to be prepared for a sudden and unexpected inflow of angry complaints about you breaking something
you could do polls, but that selects for people who would complete a poll, again excluding many who would be touchy about their workflow
cursed solution: opt-in telemetry but bug reports are only accepted from people who've had telemetry enabled for a while before the bug was reported, therefore encouraging opting in
@whitequark remember when Brave canned a privacy feature because their statistics said people weren't using it -- the statistics that privacy people disable?
for most of my life when i did play games i'd play shooters simply because it was something that i found that distracted me from overwhelming chronic pain, and i didn't think about it much if at all
so now that i've recently realized that you can, and should, outsmart and outplan the enemy, the experience completely changed for me
@whitequark fair. I play rts strategy RPGs etc etc for that 😆
TBF the REAL reason I play shooters is for the story, hence why I only play single player ones with decent stories like halo or the old voyager elite force games xD
the most important thing to remember while compiling Clang is that you're probably going to be still alive a week from now and so you don't really need to rush anywhere
@whitequark signal() is probably the most famous C function signature of all time, many Unix coders know what it does even if they don't really know C pointer syntax because of its appearance in Unix folklore... sighandler_t is a GNU extension so the "proper" conforming code is the raw definition.
@ankitpati@whitequarkcdecl is one of the tell-tales that shows K&R is a reference book instead of an introductory textbook. Instead of teaching readers about useful guidelines of reading C declarations, it just gives you the raw algorithm.