6 ms·
> it taking quite a lot of CPU Yes that is fixed. The reason for slow performance + high cpu usage on electron/webkit apps was just the sheer amount of mach
by dexterleng 6y ago
> it taking quite a lot of CPU
Yes that is fixed.
The reason for slow performance + high cpu usage on electron/webkit apps was just the sheer amount of mach ipc calls (from the many many <div> layers) needed to be made to fetch the entire UI element tree.
This has been fixed two days ago Heres the solution for those interested: https://github.com/dexterleng/vimac/pull/190 https://github.com/dexterleng/vimac/pull/190
I was also using a bunch of async queues instead of just a single NSThread which likely contributed to high cpu usage, and that has also been fixed.
> warning that I am using a screen reader.
Nope, you should get this warning, although it was a one time prompt for me. This is because Accessibility is opt-in for electron apps for performance reasons, and I have to ask for it through setting the AXManualAccessibility attribute (see https://electronjs.org/docs/tutorial/accessibility#assistive-technology https://electronjs.org/docs/tutorial/accessibility#assistive...), which I guess triggers the prompt.
- fny 6y agoWhy did you choose to use electron for something so specific to MacOS? Awesome project by the way. This will save my wrists from a lot of pain.
- hibiscus4156 6y ago> Why did you choose to use electron for something so specific to MacOS? I think you're mistaken. OP is referring to Discord as the webkit/electron app.
- messe 6y agoI don’t think they did. They’re just talking about the high cpu usage when trying to navigate an electron app while using vimac.
- dexterleng 6y agoThe app is written in Swift, not Electron. Vimac had major performance issues previously when traversing the UI Element tree of Electron/Webkit apps.