4 ms·
You've betrayed your own point by admitting that though: WinForms and WPF aren't native - (well, WinForms is a a thin abstraction layer, but still not truly nat
by DaiPlusPlus 6y ago
You've betrayed your own point by admitting that though: WinForms and WPF aren't native - (well, WinForms is a a thin abstraction layer, but still not truly native). If you're using WPF today you can probably switch to Electron without your users noticing anything (besides a 10x increase in memory usage...)
- pjmlp 6y agoThey are native UIs of the Windows platform, built on top of Win32, GDI+ and DirectX. There is so much that the Web still fails short of WPF.
- Const-me 6y ago> you can probably switch to Electron without your users noticing anything GPU support is not good enough in the browsers. Even 12 years old Direct3D 11.0 is way better than the current WebGL. In WPF, it’s relatively easy to render a dynamic texture with Direct3D 11 or 12, then pass it to WPF to compose it into the GUI, without ever downloading pixels from VRAM. Similar for compute shaders. You don’t need WPF to integrate DirectCompute, but you do need convenient native interop. These C structures, typed arrays and unmanaged pointers are all over the API surface. Not sure JavaScript is good enough for the job, the language and VM were designed for very different requirements.
- jmnicolas 6y ago> If you're using WPF today you can probably switch to Electron without your users noticing anything A WPF app will load much faster and feel more integrated (more Windows like) than an electron app. I have a C# / WPF app that I optimized to the best of my capacity but that still needs about 1 minute to compute data. I shudder to think how long JS would take to do the same job.