React noob and compose noob here so sorry if this ...
# compose-web
c
React noob and compose noob here so sorry if this comes off as stupid, but am I understand what jake said correctly? Compose for web should be "better" perf wise than react because it doesn't use a virtual dom? Isn't the concept of the virtual dom close to composes tree where it "diffs" things?
j
No, Compose for web is not faster than React.js, at least not in the short term.  Compose is optimized for JVM and React is optimized for web, and I would expect their relative strengths to continue for the foreseeable future.  Long term, it depends on how much effort goes into performance optimization of the Compose-for-Web internals, and the level of investment is largely dictated by how many users are requesting such investment. Right now, the primary reason to use Compose for Web would be that you want to maximize code/knowledge sharing across platforms.
5
s
Compose for web is not faster than React.js
Is this an assumption or something that someone has measured?
a
Right now, the primary reason to use Compose for Web would be that you want to maximize code/knowledge sharing
I played with Compose for Web last weekend, and I find that Compose code sharing is not the case currently. I had to use lots of components like
Div
,
TextArea
, A, P , etc, which obviously are web-specific. So I ended with a completely separate implementation of UI for web. So I would expect component unification as a primary target for now. Just my opinion.
🙏 5
👆 6
u
@spierce7 we do measure such thing in order to not unexpectedly make things worse. However Jim is completely right. As of now the speed is not our main goal. We'll pick all low-hanging fruits and optimize whatever is cheap and fast to optimize. However consistent and mature API is right now is a goal we value more.
👍 8