It is called CV driven development.
Re:Much ado about iOS app architecture
by amigoingtodie on Thursday November 09, 2017 @08:06AM
(#15662020)
This made me laugh.
Re:Much ado about iOS app architecture
by brendanw on Thursday November 09, 2017 @10:20AM
(#15663090)
+1 Butterknife doesn't reduce lines of code, introduces new syntax to learn, and carries additional risk (eg it has introduced unexpected issues). I believe some of the framework+library bloat is intellectual signaling.
Re:Much ado about iOS app architecture
by on_and_off on Thursday November 09, 2017 @05:03PM
(#15666208)
I have just arrived in a new company where they use BK.
I have always been doubtful of its benefits but after giving it a fair chance, that's still the case :/
It removes a tiny bit of code, that does not seem that helpful to me. I still have to add the id in the java code, and I would have to count to know how many characters I save that way. Not many. And now I need to worry about how the bk magic happens to be sure to do not leak that way.
I am used to databinding, where I initially had the same reaction .. but after some use it allows you to gain a lot of time with two ways binding and binding adapters while staying at a sane level of abstraction IMO (it just writes the boilerplate code for you) .
That is true. Now imagine how bad it can get with React Native apps. I'm struggling to keep everything contained.
Look, not all of those things are bad but jesus fucking christ, what happened to exercising restraint and good judgement with introducing dependencies in to your projects? Dependencies are a LIABILITY and for something to be introduced it has to be worth it, not just provide some minor syntactical convenience (like Butter Knife, etc.)