Since we're keeping the different parts here under one proposal for now, I'm thinking of renaming the overall spec to wasi-graphics
.
Thoughts anyone?
What do y'all think of renaming wasi-canvas
to wasi-surface
? I think canvas is only used on the web, and we're not really emulating the web's canvas, so we should probably use a different name.
graphics are part of it, certainly, but a TON of people are into gpu usage for the model/inferencing as well. How do you see this?
Yeah that's right, webgpu can be used for compute as well.
Don't have a name that captures graphics and gpu-compute, would love to hear if others can come up with something.
wasi-gpu? May be too generic, and also not cover CPU surface/canvas use cases if those aren't split off
Has anyone had a chance to look at the windowing API prototype that was recently posted?
I took a quick look last week. Figured I'll reach out to the author, if I see continued progress, to see how we can work together.
Do you think I should reach out already?
Yeah, if you're interested and able to, reaching out now makes sense.
Sounds good.
Is the author here on zulip?
Not to my knowledge
@Tarek Sander Hello and welcome! This is where we've been hanging out and discussing wasi-webgpu.
I'm here now. Considering the high-level graphics API stays under this proposal for now, I think the windowing aspect should also just go here.
I think "Window" or "Surface" would be fitting names for mini-canvas
instead if I add proper window system support. I think I'll make an issue for the discussion.
(continuing the discussion from updates)
@Jorge Prendes the name won't be wasi-gfx/wasi-webgpu
, it'll be wasi:webgpu
. The wasi-gfx only refers the the group working on multiple proposals, including but not limited to wasi:webgpu
. And doesn't refer to any actual spec.
Makes sense?
Last updated: Dec 23 2024 at 12:05 UTC