Тsфdiиg is more right than he could possibly imagine.

Big API is at it again!

A little more thought, a little more effort, a little more care. If there’s a better, more sustainable way to make a shingle, we intend to find it. #AnythingButStandard #Innovate #EcoFriendlyRoofing #Greener #SustainableInnovation #SustainableRoofing #SustainableShingles @Holcim

@tsoding I love when he goes off

@tsoding I think the main reason why these specs are so bad is because no one person could read all of it.

@tsoding One shouldn't fall to the temptation of thinking to a plot when stupidity could also be an explanation. I agree that looking at Vulkan this is kind of hard. My guess is the size of the committee plays a role. Best comes from 1-person committees :-D... worst too however (JSON).

@tsoding He's exactly over the target. I would love to take him on a tour through the comic insanity that is in the BIP repo. There was a point in the mid 2010's when everything was made retarded, all at once, and it was definitely deliberate.

@tsoding Such a solid take!

@tsoding

@tsoding the funny part is that frameworks don't solve the problem anyway

@tsoding This is unironically true about CUDA

@tsoding Don’t think he’s right, but it’s fun. Most specs are written before the given domain was fully explored. Also, if they’re too specific, they aren’t universally relevant and aren’t widely adopted. If they’re too open, they may as well not exist. Good universal specs are hard.