They didn't tell more at this one it seemed but ma...
# android
a
They didn't tell more at this one it seemed but maybe you will find something additional. I think you got it. I am not a googler but I talked to Yigit about it at the last IO and he told me that they don't want people to face issues that finidViewById entails but at the same time not everyone wants to go all the way databinding cause it could be an overhead and it seems too complex. And when they looked at how people use databinding they realized that many don't use expressions or custom adapters but just access views and that's how they decided to give people view binding as a type safe and not that complex way to serve that purpose. And also eliminate the need for 3 party libraries like ButterKnife.
👍 1
r
Quick mention, the person who created Butterknife is the person who created viewBinding . The binding king himself @jw 😂
a
Is it like an official job title ? 😅😆😆😆
j
That description makes it sound like there was a lot more forethought than there really was.
It's more like the databinding users and desire to eliminate ButterKnife were confirmation of the feature