@mint I don't know about Elixir as a whole but there seems to be a lot of bullshit where, like, something is plucked from an implicit expected structure returned by one of the functions in a module, and you have to read the entire call stack because you can't just test it interactively because there are 20 lines of destructive context built up. I think there is a bug in one of the existing uploaders but I don't know if the bug is still there or if I'm reading it wrong.

I don't think the way pattern-matching is used lends itself to code that is easier to read or write or debug or even spot the bugs in. I shit out all those MRFs and a lot of them have comments or commit messages indicating that the code is bad but I eventually just stopped making a note of that because it applies to all of them. Trying to write "good" code to fit into Pleroma has

I say "the way pattern-matching is used" and I can't say for certain whether this has to do with the project or the APIs the project has to use or if every Elixir codebase looks like this. I pretty strongly suspect that this is the ecosystem/language's fault. Phoenix reeks of a design that was conceived by Rails fetishists, and Rails is one of the worst designs you can come up with.

I want to conform to an interface, play nice with the internal tooling, and that's 95% of the effort. The other 5% of the effort is calling two upstream endpoints. I think these ratios are backwards.