This message was deleted.
# compose
s
This message was deleted.
s
One issue that I see (my own opinion) with SwiftUI is that everything seems to be declared on
View
. Like
padding()
,
clipped()
,
frame()
, … So many things that are not necessarily needed to be shared across different views. I don't know how maintainable that is. Just look at
android.view.View
now, it's a beast, and I fear something similar will happen to SwiftUI's
View
protocol. But I haven't looked too much into it yet, I might be wrong.
I'd rather have a separate thing that does padding or clipping or framing than to have everything just being declared on
View
, if you see what I mean?
f
There's discussion about that two messages above
g
You're right I don't know how I missed it