New pole! Instead of just focusing on the physical device name, what if we renamed both of them?:
0 Boosts
0 Likes
@mdiluz Honestly, it’s going pretty well. Device/context seems to be the clear winner.
@mdiluz And we know just how much people like the Vulkan terminology. 🤣
@gfxstrand IDEs should have a rename-by-way-of-internet-poll that does the poll async and comes back to rename 1 hour later
@gfxstrand ohh I think the "Device / Context" moves into the right direction.
I think the former can be something expressing the Device (doesn't even have to be a GPU) and the latter just the logical execution environment. Maybe some would even call it "queue" or so...
but then we have vulkan queues which are more like device subunits, so I guess context is fine.
Yeah.. I think that one is a good scheme in principle from an abstraction pov, but might want to ponder more on the precise terms.
@karolherbst@chaos.social @gfxstrand@treehouse.systems I always thought Context suited well for a thing every other resource is bound up within
@erincandescent @gfxstrand That's a Vulkan device, no?
@karolherbst@chaos.social @gfxstrand@treehouse.systems idk I last did any major GPU programming before Vulkan 1.0 and my most recent true GPU experience is. uh. about 12 years old and in Verilog 
@karolherbst@chaos.social @gfxstrand@treehouse.systems Rare case of OpenGL (/EGL/GLX/...) being right
@gfxstrand this bike-shedding-by-way-of-mastodon is inspiring