3 ms·
This misses the mark, for reasons I can't see why. Maybe let's compare code 8 years ago to 4 years ago to today. I did Android dev. 8 years ago it was a nightm
by muzani 6y ago
This misses the mark, for reasons I can't see why. Maybe let's compare code 8 years ago to 4 years ago to today.
I did Android dev. 8 years ago it was a nightmare. To download an image, you had to build your own async thread, transfer the bits, resize the image, and then make sure there aren't any memory leaks and keep it small enough that it doesn't suck up all the RAM and crash the device.
4 years ago, it was easy. Just plug in the URL, and where you want it to go and it'll handle all the above + caching.
Today we have Android Jetpack. Now MVVM architecture is the default. Everything is cleanly handled - we make sure that there's no memory leak when someone makes a call within the half second it takes to download the image.
But for some reason, code is more tiresome to write. A single page used to be 2-3 files, now it's easily 12 files. Trying to debug a problem means sifting through those parts. The fact that we can code a full feature in 5 min means that very little thought is going into whether this feature is necessary, has side effects, or the responsibilities of the different parts. Budgets have gone up too, and now you can expect to deal with a freelancer from Qatar or Ukraine or whatever who builds a piece just fine, but nobody remembers how it works or whether this part was built correctly.
I'd say that the individual parts work fine but as a whole, they go together poorly.