The article is missing this motivation paragraph, taken from the blog index:

> Graphics APIs and shader languages have significantly increased in complexity over the past decade. It’s time to start discussing how to strip down the abstractions to simplify development, improve performance, and prepare for future GPU workloads.

▲

alberth 6 days ago | parent | next [-]

Would this be analogous to NVMe?

Meaning ... SSDs initially reused IDE/SATA interfaces, which had inherent bottlenecks because those standards were designed for spinning disks.

To fully realize SSD performance, a new transport had to be built from the ground up, one that eliminated those legacy assumptions, constraints and complexities.

	▲	rnewme 6 days ago \| parent [-]
		...and introduced new ones.

▲

stevage 6 days ago | parent | prev [-]

Thanks, I had trouble figuring out what the article was about, lost in all the "here's how I used AI and had the article screened by industry insiders".

▲

masspro 6 days ago | parent | next [-]

I read that whole (single) paragraph as “I made really, really, really sure I didn’t violate any NDAs by doing these things to confirm everything had a public source”

	▲	beAbU 5 days ago \| parent [-]
		This is literally the second paragraph in the article. There is no need for interpretation here. Unless the link of the article has changed since your comment?

▲

yuriks 5 days ago | parent | prev | next [-]

I was lost when it suddenly jumped from a long retrospective on GPUs to abruptly talking about "my allocator API" on the next paragraph with no segue or justification.

▲

jama211 5 days ago | parent | prev | next [-]

You only read two paragraphs in then?

▲

doctorpangloss 6 days ago | parent | prev [-]

haha, instead of making them read an AI-coauthored blog post, which obviously, they didn't do, he could have asked them interesting questions like, "Do better graphics make better games?" or "If you could change anything about the platforms' technology, what would it be?"