Hello HN! SixtyFPS founders here. We're two engineers who started this project ~6 months ago because we love good APIs and good toolkits that boost overall productivity. We'll be around here to answer questions.
At this point, the product is still in a very early alpha stage, but we are eagerly looking forward to your feedback on technical features as well as on a scalable business model.
Our short term goal is to get involved in a paid project that would require a GUI frontend and where we could make use of this project. If you have any recommendations, or if you know of any such project, we would be happy to hear from you.
Didn't look at it running or the code (yet), just the language page for the .60-syntax - and damn, that impressive;
I know Qt/Quick/QML since Qt4.7 and I must say:
They avoid the quite some problematic stuff in QML:
- no dynamic scoping (YES!!)
- dedicated syntax for binding (which means it's much easier to distinguish between value assignment and an actual binding that will/can be reevaluated)
This looks really nice and the online demo is quite slick also on Firefox.
I saw that there is either a Qt or GL backend, which made me wonder how this is used then in the online demo or is the browser backend a third, undocumented one?
Also how is input (pointer, key) supported across the already apparently supported platforms?
Everything is currently rendered using OpenGL ES 2.0 (WebGL 1). What's currently called a "Qt Backend" uses QStyle to produce textures of the individual controls.
We use the excellent winit crate at the moment for input handling, so that abstracts it away for us.
At this point, the product is still in a very early alpha stage, but we are eagerly looking forward to your feedback on technical features as well as on a scalable business model.
Our short term goal is to get involved in a paid project that would require a GUI frontend and where we could make use of this project. If you have any recommendations, or if you know of any such project, we would be happy to hear from you.