this post was submitted on 07 Jul 2023
52 points (98.1% liked)
Slide for Lemmy
518 readers
4 users here now
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Extra notes for the techies; been kotlinifying the codebase as I go, its now mostly done, but vast swathes of the code in the original namespace needs serious redesign. There are some really great things in this, like I just came across the subsampling imageview which is a brilliant idea, but its undermined a bit by mindbogglingly bizarre things like using sharedpreferences to communicate the result of a folder chooser dialog. Notably, I've added some homegrown error reporting in this, that auto posts a github issue with stack trace on crash, which I'm real happy about, and I'm sure will get a battering once I tag a release
It is great that you do this, I am just wondering if this is maybe too much work compared to a rewrite? Just thinking of what the original developer said, codebase was in too bad shape for fixing much and he wanted to start from scratch.
I think it didn't help that he was probably quite sick of the codebase. I'm new to it, and I at least have a plan for the modernization, so it should go okay! Just a shame that a lot of it is behind-the-scenes work for now to get something that fully works. Also, personally I hate frontend work anyway so having a preexisting world class UI is a big win