this post was submitted on 20 Feb 2024
1218 points (98.5% liked)
Programmer Humor
19809 readers
274 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's an additional feature of GitHub that literally everyone uses. Therefore it has purpose. I think it's ridiculous to argue against it.
Explain to me how developers or the UI would suffer from easier access to releases?
Literally everyone? I’ve been a software engineer for ten years. My company doesn’t use it, and no company I’ve worked for has. I guess they are not part of “literally everyone?”
Explain to me how GitHub working on one product feature (releases) has no impact on how much they can work on others. Apparently in your rich enterprise software career you’ve found that resources and time are limitless? Or maybe you think it’s trivial for a platform like GitHub to change their UI.
This smacks of lots junior software engineers I’ve worked with who think problems are simple and solutions are easy because they’ve never actually DONE anything. I get that you’re very convinced that this is easy and cost less but it’s pretty clear to me you have no idea what you’re talking about.
Again. I've said before that release downloads are an additional feature. But it's a feature most people use. Neither did I say it was easy, nor it was cheap. Just that it makes sense and that it doesn't take anything away from the professionals regarding UI quality or focus.
It makes sense from a pure UX perspective. But of course the real goal of GitHub is to make money, and their paying customers are mostly corporate entities using it for enterprise development. Unless those companies decide that a download button/better release feature is desirable, it's not likely to happen.
Most corporations tie GitHub into their own build system so such a feature isn't likely to be considered useful. They pay for GitHub to reduce development costs, which is why GitHub spends so much effort on analytics and the dev experience instead of open source/public users.
Thanks for understanding what I was getting at and your well written 'realistic' addition to it. There's not much I can add besides saying you're absolutely right.