3 ms·

I really like this. The box/row/column UI generality is exactly what I have in my head and have not found anywhere, that alone will have me playing with it. I

I really like this. The box/row/column UI generality is exactly what I have in my head and have not found anywhere, that alone will have me playing with it. I'll also want to see how I can get it plugged into my Postgres database. What are your goals for client-side performance in the browser? Do you make any claims to be better than React or Angular?

hypendev 2mo ago
Glad you're liking it! If you ever encounter problems or have feedback, feel free to reach out (email in profile). >What are your goals for client-side performance in the browser? To have as minimal and efficient patches as possible - while there are some limits due to WASM serialization boundary, I believe nearly native TS/native TS speeds are achievable. >Do you make any claims to be better than React or Angular? Not yet - while the architecture is designed with that in mind, there is a loooot of low-hanging performance fruit lying around, so current perf is somewhere around 10x slower than React. A part of that is on purpose, to make debugging across engine and SDK's as easy as possible during development, and part of that is just simple bugs in internals/unimplemented changes. With some really minor fixes, it can get to about 2-3x of React. I want to lock in the API's completely and achieve proper platform parity before going towards performance optimizations, as its only then that I feel the optimizations would be worth it. From 0.8-1.0 release, I'll be focusing more on performance itself and trimming it down.
- hypendev 2mo ago
  Just to update - did some minor perf ops yesterday to cover some silly bugs in perf (like a late return causing O(n) iterations) and benchmarked on 1k item and 10k item lists. Currently it stands around 2-3x react, swapping rows in a list is faster than react and mutation is pretty much the same, will release that update today as a patch.

hypendev 2mo ago

Glad you're liking it! If you ever encounter problems or have feedback, feel free to reach out (email in profile). >What are your goals for client-side performance in the browser? To have as minimal and efficient patches as possible - while there are some limits due to WASM serialization boundary, I believe nearly native TS/native TS speeds are achievable. >Do you make any claims to be better than React or Angular? Not yet - while the architecture is designed with that in mind, there is a loooot of low-hanging performance fruit lying around, so current perf is somewhere around 10x slower than React. A part of that is on purpose, to make debugging across engine and SDK's as easy as possible during development, and part of that is just simple bugs in internals/unimplemented changes. With some really minor fixes, it can get to about 2-3x of React. I want to lock in the API's completely and achieve proper platform parity before going towards performance optimizations, as its only then that I feel the optimizations would be worth it. From 0.8-1.0 release, I'll be focusing more on performance itself and trimming it down.

hypendev 2mo ago
Just to update - did some minor perf ops yesterday to cover some silly bugs in perf (like a late return causing O(n) iterations) and benchmarked on 1k item and 10k item lists. Currently it stands around 2-3x react, swapping rows in a list is faster than react and mutation is pretty much the same, will release that update today as a patch.