Email or username:

Password:

Forgot your password?
Top-level
Stylianos Gakis

@billjings I browsed the code and I must say that I don't know why someone would put themselves through doing all that. Is it all about feeling morally or intellectually "superior" to everyone else since they don't take "the easy way" of using even the most staple androidx libraries? I really am not sure.

8 comments
Adi 🐾

@gakisstylianos @billjings I have serious issues with his behaviour, but not with his choice of languages and libraries. Android allows for diversity of approaches, and (for me) is better for it. The same diversity that allows things like circuit, also allows his "unique" approach. I feel this diversity of approaches makes the platform different from Apple's stricter approach.

Adi 🐾

@gakisstylianos @billjings What's abhorrent is his behaviour - choice of language, dumping on SkyDove's post, and behaviour on Mastodon Android repo.
In contrast, I remember the lead dev on Signal's Android repo refusing to adopt Kotlin a few years ago. He was curt, made it clear that it wasn't up for discussion, but never rude to contributors.
It's possible to stand up for unpopular choices without being a jerk.

Adi 🐾

@gakisstylianos @billjings though the general rule of thumb increasingly seems like single contributor/decision-maker codebases suffer from this. People who were ahead of curve, but with no one to constructively challenge them, get stuck in their success.

I get this smell from a bunch of other places, like whenever I look up issues or PRs on ktlint.

Christophe B. :android:

@gakisstylianos @billjings Challenges aside, how do you expect anyone to want to contribute to this code if you have to constantly reinvent everything from scratch?
I hope Mastodon is aware that their Android app is dead the second this maintainer leaves.

Stylianos Gakis

@bladecoder @billjings oh yeah it'd be a pain for sure. I've seen an extremely similar situation for another company play out exactly this way after the original author left. Many years later, maintaining the Android app is a story of cycling through many Android devs who burn out and leave as soon as they are able to. While the app is obviously struggling to keep up with the product changes.

Gregory

@gakisstylianos @billjings whenever I browse the code of any "modern" Android app, I also ask myself the question why would someone put themselves through doing all that. You know, all those 6 abstraction layers to handle a click on a button. Those codebases remind me of this: github.com/EnterpriseQualityCo

Stylianos Gakis

@grishka @billjings it's absolutely possible to build an unreadable monstrosity going the other direction too, I do not deny that.
Still doesn't make me change my mind about your pokedex code being something I would absolutely not want to work with.
Despite what you may think, there is room for something balanced and readable between your extreme and those "samples" extreme

Bill Phillips

@grishka @gakisstylianos This is my most common complaint about sample apps we receive from candidates: they believe that "architecture" is what makes a good app. Totally ass backwards IMO

And so they include a whole DI framework and all these repositories for a simple list->detail application.

Go Up