@NullCipher_@mitchellhynes Then you can rotate through those handles per frame and render them inside of WebGPU in the renderer process for example. I'm using wgpu's DirectX backend but any D3D12 renderer that allows you to render or copy to shared textures should work fine. Happy to answer any questions!
@NullCipher_@mitchellhynes It needs a bit of work to share a D3D12 handle but it's not too bad. Basically create a shared D3D12 texture, duplicate the texture handle into the renderer process (DuplicateHandle etc.), then pass the handle to `importSharedTexture`/`sendSharedTexture`
@nimblephatty Completely agree, so many operators have been burned by software implementations gone sideways. Trying to sell a replacement into that can be brutal. It's taken a huge amount of effort to build trust as a vendor.
Really excited about shared textures in Electron (as video frames for WebGL or WebGPU).
https://t.co/QcPYnPLJ4B
This opens up all kinds of use cases for mixing external renderers with the DOM.
@TheGingerBill@sampavlovic@SebAaltonen Yeah WGSL came afterwards. WebGPU implementations wgpu (Firefox) and Dawn (Chrome) both used SPIR-V for years until WebGPU agreed on WGSL
@ryanzslin@batmansmk@DaKangz@WebGPU@rikarends naga is used instead of spirv_cross now, so the incremental binary size should be pretty small now. I haven't checked the size lately though
I get asked all the time why our real-time, highly interactive desktop application isn't a web application.
This is why: no amount of optimization or tuning will remove the extra cloud interaction latency. The architecture needs to fit the application - not the other way around.
Premature optimization quote is badly misunderstood. Back in the day it meant micro-optimizing. Programs were simple C programs and pretty fast by default.
If your architecture is not built for performance, no amount of micro-optimization will make it acceptable...
PSA: if you use @GoDaddy's Microsoft365 email and custom DNS nameservers then your email will be broken the next time any user renews because of the new @proofpoint integration that can't be disabled (mandatory at the end of this year)
@DrFreelance@Craig__Bowling@GoDaddy@proofpoint Yeah absolutely. I’m still using the regular 365 mx record which skips all of the Proofpoint inbound handling for now. Planning to move off GoDaddy soon.
@Craig__Bowling@GoDaddy@proofpoint It sounds like they're raising prices, so this could be their excuse to do that (apparently Proofpoint will become mandatory on all subscriptions).
Support said it was to help with security, but Defender's quarantine already handles this pretty well for smaller companies
@skystracloud Domain registration with the "Email & Office" add-on.
I normally subscribe to M365 directly but this one was set up through GoDaddy - planning to defederate (e.g., https://t.co/XrO0yncPPR)