Jonathan Blow on LLVM Documentation

Jonathan Blow on LLVM Documentation

Clip from Jonathan Blow

#jonathanblow #gamedev #webdevelopment #programming #llvm

[davidboeger]

I used to be an OS kernel developer, and a coworker of mine was once tasked with generating a graph to help visualize the complexity of dependencies in our codebase. Management assumed it would look something like this. It ended up spitting out a completely solid blob. You had to zoom in just to see any space between the line segments, and even then, you couldn't make out any links. The guy who generated the graph was like, "Yeah, there's nothing we can do with this."

[CianMcsweeney]

Love when my "documentation" is a cyclical treasure map graph 😂

[georgehelyar]

Not the worst graphviz diagram I've ever seen. You can read some of the words and follow some of the lines

[____uncompetative]

It is unreasonable to expect anyone who is working on something as low-level as a Virtual Machine to know about what the optimum presentation of high-level website site maps should be.

[selfselected]

I'm laughing my ass off in the first 30 seconds. His voice even cracks when trying to talk about this lmao

[jesusmgw]

"How is this not The Onion?" has become part of my lingo since the first time I saw this. And it applies to like 10-15 things daily at least.

[RogerValor]

feels like docs that were generated to have docs

[supernewuser]

yep, I just checked the clock and it is indeed drawing time

[Evilanious]

The frustration is flowing well today. With some humor sprinkled in.

[warrenhenning]

Please post a call/dependency graph of Braid and The Witness's code for comparison. Most large software systems of any kind are a giant clusterfuck

[rebus_x]

What's more frustrating is I (and many people also) know exactly which software created this, and tried to use it for my own diagrams/flowcharts.

[toomuchzelda]

he should've shown LSP documentation to compare

[scotthinton]

Not sure I've ever seen Doxygen "documentation" that was useful. Usually just crap like '// @brief Constructor' or '// @brief GetMember' when the function is literally called 'GetMember'. People don't want to explain why code exists, their IDE just generates garbage Doxygen comments that I ignore 90% of the time because they add 0 value beyond what the source already says. Drives me nuts.

[kruel]

At least the graph is mostly flowing one way...

[dupdrop]

Clearly a skill issue on JB's part. You can clearly see from this cloud diagram that soaking this cloud in LLVM IR will make it wet and heavy, which will make it then spit out optimized assembly raindrops. This is part of the reason why LLVM is somewhat slow btw, since you have to get the cloud soaked enough before any output can be produced.

[SpookySkeleton]

if he just used LSP he wouldn't need documentation

[leaderkey]

Someone was a bit overzealous with their graphviz

[FaizKTG]

Went in looking for llvm went out with graph theory trauma

[FINALLYQQQQAVAILABLE]

Generated graphs are often useless. Even when the software in question is well designed. Graph generators are not yet intelligent enough to leave less important pieces of information out of the graph.

[steveoc]

LLVM is deprecated now in favour of HTMX