>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.