You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
If you were to launch a DDOS attack on programmers' ability to get things done, this is what it might look like.
Before, it was already crazy, because you could be running on the same CPU and GPU, but you were forced to use a different shading language per OS. Now you need *two* shading languages for one OS, because maybe you are running in the browser.
I’m sure from the working groups perspective you should just do everything in the browser, and I hate it.
Not to get in the way of a good rant, but you *can* run WebGPU natively: there's a API at https://github.com/gfx-rs/wgpu-native … that uses the same backend. I've used it for a raytracer (https://www.mattkeeter.com/projects/rayray/ …) and a Vim GUI / shader editor (https://www.mattkeeter.com/projects/futureproof/ …), no web apps in sight.
The reason for this mess is because Apple has an ongoing legal dispute with Khronos and absolutely refused to accept SPIR-V as part of this API. Nobody else wanted to invent a new shading language. But Apple left us no choice.
Any shading language at all was the wrong choice.
It is not that difficult to use one shader source and compile it for different target or intermediate representation, in the end this is all the same. And we're already doing that.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
