I really hope it continues to be possible for this art form to exist.
Hopefully AI doesn't one day ruin the demoscene as well. Seems like a Pandora's box for cheating and/or asymmetric resource advantages.
I don't think they'll be much ruining going on. The people who make these demos use everything they can get their hands on, as long as it helps with cool visuals, a great soundtrack, and sandal executable size. In terms of how they get there everything seems to be allowed and even expected. And if one of those things is a trained network, so be it. Many groups have their own custom tools or even one-offs for only one demo.
I feel like I have a high level understanding of most parts of the stack, but graphics programming has eluded me thus far.
Would writing a ray tracer be a good starter project? I know I've seen it recommended by several people before.
https://threejs.org/examples/#webgl_geometry_terrain_raycast
The Book of Shaders looks quite interesting however, thank you for the link!
Using these tools doesn't mean your final project has to be JS-based as well. It just happens to be a convenient way to focus on specific aspects of the project.
Beginner. https://youtu.be/0ifChJ0nJfM
Advanced. https://youtu.be/BFld4EBO2RE
Website. https://iquilezles.org/
Raytracing in a weekend is also useful: https://raytracing.github.io/
Yes!
https://web.archive.org/web/20120119015415if_/http://www.iqu...
https://www.youtube.com/watch?v=1dcrV_7JpXQ
Pouet link if you want the binary: https://www.pouet.net/prod.php?which=1221
It blew my mind when I first came across it in 2003, and it's still highly impressive even now.
For whatever reason I became obsessed with this lesser known demo called g-cube and watched it a lot in 2011.
Just wanted to share(anyone remember it?): https://www.youtube.com/watch?v=fc0gh5wnItw
That path brought me to HPC, efficient and high performance programming and showed me how thinking about writing efficient code made a difference.
Yes, you can't arrive to demoscene level wizardy in every application/tool you write, but optimizing the obvious and then some changes things a lot.
Thinking about it again, possibly coming from C64 and early x86 hardware already primed me to "do more with less" mindset already, but '.the .product' get the things rolling.