ShaderPad: A Lightweight Library for Web Shaders

ShaderPad is a new, lightweight library designed to help developers easily integrate shaders into websites without repetitive boilerplate. It is significantly smaller than Three.js and optimized for GPU performance, making it ideal for interactive web graphics. The project balances human-led API design with AI-assisted documentation to provide a streamlined experience for creative coders.

Key Points

• ShaderPad eliminates the need for repetitive graphics scaffolding when adding shaders to websites.
• It is highly optimized for size, being 30x smaller than Three.js at only 5.8kb gzipped.
• The library is designed for performance, keeping computations on the GPU and minimizing expensive CPU trips.
• It includes features like history buffers and MediaPipe integrations for advanced interactive effects.
• AI was utilized to build the documentation and act as a creative collaborator, though the core library remains lean through human design.

Sentiment

Overall positive. The community appreciates ShaderPad's focused approach to reducing shader boilerplate and its tiny bundle size. The WebGL vs WebGPU debate is substantive but not hostile, and the author's responsiveness to feedback (fixing bugs, adding examples, committing to a web component wrapper) generates additional goodwill.

In Agreement

• Shader boilerplate for web projects is genuinely painful, making a focused library like ShaderPad valuable for occasional dabblers and small web use cases
• WebGL/GLSL remains an easier shader language for beginners compared to WebGPU/WGSL, making it the right choice for a lightweight creative coding tool
• The small bundle size (5.8kb) is a major advantage over pulling in full 3D engines like Three.js for simple shader effects
• A web component wrapper would make the library even more accessible by enabling declarative, drop-in HTML usage

Opposed

• WebGL2 may be a dead evolutionary branch since browser vendors are focusing future graphics features on the WebGPU path
• WebGPU's performance issues are not inherent to the API but stem from developers incorrectly applying WebGL patterns to a fundamentally different architecture
• Building on WebGL locks users into a platform that may not receive future improvements, regardless of its current ease of use