ppenenko

26 ms·

1.
by ppenenko 1y ago
I commiserate with your frustration with developers writing things suboptimally all too often. However, I disagree with the assumption that it's a JS/Python vs C issue. Example: when VS Code came out, it was much, much faster, mor
2.
Khronos Announces Slang Initiative from Open-Source Nvidia Code(phoronix.com)
3 points by ppenenko 2y ago|0 comments
3.
Show HN: Metashade GPU EDSL at ASWF Open Source Days(youtube.com)
1 points by ppenenko 2y ago|1 comments
4.
by ppenenko 2y ago
I got to speak about my Python-based GPU EDSL https://github.com/ppenenko/metashade at the Academy Software Foundation Open Source Days 2024 ( https://opensourcedays2024.sched.com/event/1e2Gx ), and
5.
by ppenenko 2y ago
Thanks! Multiple targets is definitely the plan, and GLSL is my next priority. Metashade can currently generate HLSL for the DX12 version of https://github.com/ppenenko/glTFSample/tree/metashade_demo , and the
6.
by ppenenko 2y ago
Agreed that the ability to just run on the CPU is valuable. Metashade doesn't support that yet and its codegen syntax doesn't look like regular Python code (everything codegen-related is prefixed with `sh.` etc.) but it's cer
7.
by ppenenko 2y ago
No, I don't believe Jinja would suffice. For starters, how would you abstract out the syntax differences between, say, HLSL and WGSL? Jinja's approach seems to be taking the syntax of the target language and embedding templating i
8.
by ppenenko 2y ago
Cheers Thomas!
9.
Show HN: Metashade – a Pythonic GPU shading/compute EDSL(github.com)
47 points by ppenenko 2y ago|8 comments