4
jestdotty
130d

tools people REALLY wanna use are written like garbage

and also very active, in terms of tickets and pull requests
but the code is overly complex for no reason and a mess, turns out

I looked at the codebase and I have no clue what's going on
then found the API it's calling and I'm sitting here going "Jesus fuck I could've just wrote my own"

it's actually really strange, I see this pattern often of tools tons of people rely on and want to use but they're coded horribly, tons of bugs, and the code is entirely incomprehensible. though all the low effort pull requests is a new one I guess, generally there's no activity or the maintainer is just gone (maybe it's AI?)

anyway then I looked at the API it's wrapping and I'm confused why this library has such shit usability, and furthermore why the hell the code was like that cuz I read that first for about an hour and just kept going in circles. bruh what

guess I'll find out tomorrow if I'm signing up for unanticipated complexity or these people really did mess this up

Comments
  • 1
    That’s the problem with using metrics like number of github issues and number of stackoverflow results to determine popularity.

    The shittier and the more problems your product has, the more popular it appears to be.
  • 1
    Sure you can maybe create a better tool suited just for your use-case
    Doubt when it has to support all the shit that's requested in issues over years and having to maintain backwards compatibility
Add Comment