this post was submitted on 20 Feb 2024
1127 points (97.2% liked)
Microblog Memes
4844 readers
2250 users here now
A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
Rules:
- Please put at least one word relevant to the post in the post title.
- Be nice.
- No advertising, brand promotion or guerilla marketing.
Related communities:
- !whitepeopletwitter@sh.itjust.works
- !best_of_mastodon@sh.itjust.works
- !curatedtwitter@sh.itjust.works
- !curatedtumblr@sh.itjust.works
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
As someone who quite hates being in that situation (although I can build binaries and all that with a little grunt), I can't quite understand why sometimes developers can't do what's seemingly so simple for them - build and release their code as a package.
Like, I know there are variables when building, but why can't you just make a default package (okay, series of packages for different OSes if needed) for everyone to enjoy? Is it just some elitist mindset or no bothering about anyone but devs or are there valid reasons for such actions beyond "I don't care"?
It's not always that simple and I also don't want to do the testing and support that requires. I'm not gonna set up a windows vm and 5 different Linux vms and get a Mac to build and test for every platform. If you want to use my software you're welcome to do so but unless you're paying me I don't see why I should provide a service that is just a pain in the ass for me. Open sourcing the code alone is already a commitment that not everyone is willing to do as that requires documentation, issue tracking, community support and much more. I build stuff that I want to use and am interested in and as a thank you to the OSS community also share that work but that does not include end user support