Introducing: ShaderPad

2 comments

• rgbrgb1 hour ago
  looks great, congrats. quick note, the examples are really cool, but the link in your blogpost is broken.<p>working link: <a href="https:&#x2F;&#x2F;misery.co&#x2F;shaderpad&#x2F;docs&#x2F;getting-started&#x2F;examples&#x2F;" rel="nofollow">https:&#x2F;&#x2F;misery.co&#x2F;shaderpad&#x2F;docs&#x2F;getting-started&#x2F;examples&#x2F;</a>
  • fudged711 hour ago
    Also one or more examples in this blog post would have been great to see
• avaer1 hour ago
  GLSL. Makes sense as the breezy path, but it seems WebGL2 is a dead evolutionary branch, even if it can be transpiled over.<p>What are your thoughts on supporting other languages? Or did I miss that in the docs?
  • koolala1 hour ago
    It isn&#x27;t a dead end when WebGPU failed at all their graphics performance promises for being better than it in every way.
    • avaer1 hour ago
      I was speaking more to the willingness of vendors to support. It&#x27;s debatable how well WebGL(2)&#x2F;WebGPU are designed and especially implemented. But it does seem like most evolutionary features, if they make it to browsers at all, would come from the WebGPU path. Not saying the reasons for that are good.
      • busterarm30 minutes ago
        Underrated comment. Our industry is littered with business choices made over technical ones that crippled or otherwise enshittified products.