That doesn't sound like an argument or a joke. Could you elaborate why some choices are better than other?
08/20/2017, 6:25 AM
Mostly meant a joke, but it is also tragically real. A vast majority choose things such as DB abstractions based on how easy things like the minimum viable integration is. And that's easy. Making things that require no code and solve contrived examples in almost no lines of code seduces you in. Then inevitably the complexity grows at a rate much higher than if you had picked something less sexy but better designed to scale. I'm sure it's true everywhere, but it feels like and especially bad problem for Android libs.
08/20/2017, 10:20 AM
It was pretty obvious it was a joke 😀
08/20/2017, 2:31 PM
Thanks Jake 🙂 The problem in my opinion is that “Use our DB, see how it is easy” what you are against is pretty much the same as you saying “people have bad taste” over their DB, especially given who was saying that. But explanation makes sense, if only it could be a little bit more specific. I’m not against opinions, no, but I believe when saying “don’t use X, use Y” adding “because A and B” is much much better.
08/22/2017, 1:04 PM
Jokes apart, what is the solution that covers Jake’s requirements best?
[BTW, I’m sure there are bad libraries out there, but most of the Android API itself is horrible.]