Hot questions for Using Butter Knife in android databinding
we're just starting a new project
And it seems like both butterknife and databinding are awesome tools to reduce boilerplate code.
We started with butterkife and added databinding later, the idea is to not have viewmodel classes in java instead express them in xml.
Is there any reason to keep butterkife around ?
The same situation happened in my current project. We used
DataBinding alongside. We decided to get rid of one of those as we used
ButterKnife version 7.X (converting to 8.X would be quite painful in such a big app). We got much cleaner code with
DataBinding and removing the other library reduced build time :)
BUT notice that
DataBinding still won't work with enabled
Jack&Jill compiler, which will change soon hopefully. Using
Retrolambda is still OK.
Get rid of ButterKnife.