41–49 of 49 posts
It seems really odd to me that GLSL and HLSL never unified into a common language.
HLSL is proprietary, and GLSL is open. It would be more odd if they had somehow unified. We still have plenty of proprietary vs open choices in computer languages - it doesn’t seem odd C++ and C# haven’t unified, does it?
Earlier quoted context omitted.
Safari, made by Apple, was the lone holdout for WebGL2. You’re familiar with Apple’s relationship to Flash. No I won’t be surprised at all if Safari holds out on WebGPU, and it will be precisely because it offers functionality that Metal already has. > Enjoy your pyrrhic victory. I don’t understand why you’re repeatedly spending time on WebGL threads sharing sour grapes about Flash. They don’t compete. At all. WebGL…
As if WebGL and WebAssembly protect anything against abusive content creators. Worse, they can't be be turned off, can be used for tracking analytics as well and it isn't as if shaders can't be used for mining.
https://thebookofshaders.com Still incomplete but browsable online and has its own interactive shader editor (try to click on values like floats or vectors) https://thebookofshaders.com/edit.php?log=161127202429
For anyone looking to pick up shaders for the first time, I recommend not beginning with the book of shaders. It’s an excellent introduction to a particularly heady slice of shader programming that, in my opinion, is a blind alley for folks new to shaders. I think focusing on fragment shaders rendering as full-screen quads makes the process feel more arcane and mind-shattering than it does when you consider the frag…
Earlier quoted context omitted.
As if WebGL and WebAssembly protect anything against abusive content creators. Worse, they can't be be turned off, can be used for tracking analytics as well and it isn't as if shaders can't be used for mining.
Not sure about other browsers but this is incorrect for Chrome and Firefox. They both have flags to disable WebGL and WASM. Please be careful not to spread misinformation, we owe it to ourselves to research our posts well.
Those flags are mostly only known to Webdevs and not directly exposed in the settings panel.
Earlier quoted context omitted.
HLSL is proprietary, and GLSL is open. It would be more odd if they had somehow unified. We still have plenty of proprietary vs open choices in computer languages - it doesn’t seem odd C++ and C# haven’t unified, does it?
Most people are probably working at the Unity or Unreal or Godot level anyway. Interaction with graphics APIs is pretty niche these days.
Earlier quoted context omitted.
And with the latest release of Chrome/Edge you can now tinker with WebGPU stable release.
To note that WSGL still is pretty much WIP, with many semantics up in the air how they will look like in version 1.0.
Earlier quoted context omitted.
Not quite right, the Wii uses a GL based API similar to GL 3.3. Not all Nintendo consoles do so. And the switch has even GL 4.5, Vulkan and NVN to chose from. As anyone with some graphic programming experience in cross platform knows, even among GL variants, being a variant is enough for shaders not to compile the same way and require code rewrites.
What? The Wii uses the GX API from the GameCube [0], which is not similar at all to GL 3.3; it was developed in 1999. It does not have any form of programmable shaders; it uses TexEnv-style combinators. The Wii U has a custom GX2 API, where the official shader language is GLSL (again, see the Mario Kart 8 kiosk demo). The Switch has NVN, GL, Vulkan, where the official shader language for all three is GLSL (based on N…
Secondly, the Cafe SDK documentation clearly refers to OpenGL 3.3, and GX2 is basically OpenGL in spirit while using naming and some utility functions, which fits "GL based API similar to GL 3.3".
I assume you also have access to Cafe documentation.
Earlier quoted context omitted.
Not sure about other browsers but this is incorrect for Chrome and Firefox. They both have flags to disable WebGL and WASM. Please be careful not to spread misinformation, we owe it to ourselves to research our posts well.
We owe to ourselves to make computers better to the regular user. Those flags are mostly only known to Webdevs and not directly exposed in the settings panel.
Earlier quoted context omitted.
We owe to ourselves to make computers better to the regular user. Those flags are mostly only known to Webdevs and not directly exposed in the settings panel.
I don't think the regular user even knows what WebGL and WASM are, they will just wonder why their browser game isn't working and then google the cryptic setting that they have to change to get it to work.