You know what’s frustrating?

People who announce FOSS software and drop a github link, but don’t say anywhere, including in the github readme:

  1. what environments the software will run in

  2. which files you should download from github

  3. what we should do with those files to get them to do something

We’re not all programmers. I’m an old-head computer-toucher but I don’t know how to use your mix of folders and loose random files.

#FOSS #Documentation #Programming #Elitism #WTF #Frustration

  • remotelove
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    26 days ago

    I have seen this done by companies that are forced to release their code because it is a derivative of another open source app itself. 3D printer companies were notorious for that, from my experience.

    If it’s some random bit of code from a single developer who probably doesn’t code for a living, I am usually happy with whatever I can get. Going in with the expectation that the code won’t be documented and the app being a cluster fuck dampens the pain a bit, for sure.

    I suppose I just have a high tolerance for any pain caused by trying to get random apps working. My latest endeavor was getting Prusa slicer built in Visual Studio and I am absolutely not a Windows developer. It was just a matter of reading any build errors that were thrown one at a time.

    I should note that I am not a developer by any means, but have enough of an understanding of code to navigate through just about any random repository. (I have been in IT security for a number of years, so digging through random shit code determining exploit plausibility is part of my day job.)

    Didn’t mean to derail your rant and I understand your point, btw. It’s annoying to dig though weirdly structured, and undocumented code, but it doesn’t seem that bad to me.

    If you have an example repository you can share, that would be cool. I am super curious what triggered this post, s’all.