3 ms·
A few hot takes: - Library is under the GPL 3, vastly more restrictive than most existing GUI toolkits - WebAssembly rendering in Firefox most certainly not l
by cookguyruffles 5y ago
A few hot takes:
- Library is under the GPL 3, vastly more restrictive than most existing GUI toolkits
- WebAssembly rendering in Firefox most certainly not living up to the name. I think the slide animations on the print example are managing around 5-10 fps
- Keyboard input / control focus seems absent in the demos. This would also suggest the much more important detail of accessibility also missing
- Compiles layouts to code. Is this really necessary? Visual cortex places severe restraint on how much complexity can go into a UI. Code generation on the other hand says a lot about how painful the dev-build-debug cycle is likely to be.
- Zolomon 5y agoThere is more to read about the commercial license: https://github.com/sixtyfpsui/sixtyfps/blob/master/FAQ.md#licensing https://github.com/sixtyfpsui/sixtyfps/blob/master/FAQ.md#li...
- tronical 5y agoSad to hear that it’s not fluent for you :( We went for dual licensing (GPL / commercial) in hope of creating a sustainable project. We do have basic focus handling but the demos don’t really try to show that off - that’s more tailored towards touch based input at the moment. But we’d love to have a17y, full desktop like tab focused etc. Regarding the compilation: the ability to live preview individual components or the entire design and seeing changes being applied on the fly (we have an interpreter for that) speeds the ui dev cycle a lot. Give it a try :)
- tormeh 5y ago25-54FPS here. Firefox Nightly 84.0a1 (2020-10-23) (64-bit) on Linux Wayland with AMD GPU. EDIT: Profiler says CPU-wise the page is 95% idle.