3 ms·

Just be aware that "boomer rant" creator made one of the most highly successful and used game development libraries in history. I would wager 75% of the games

Just be aware that "boomer rant" creator made one of the most highly successful and used game development libraries in history. I would wager 75% of the games in your steam library use or depend on SDL in some way. Almost certainly most of the games from your childhood that you cherish and love have used SDL too. You should probably be thanking them for creating something that gave you joy at one time, and giving it away for free...

postalrat 6y ago
Thinking takes effort.
HotVector 6y ago
I see where the SDL author is coming from, but is it really that hard to get local GitLab instance running? Or even just using GitLab? I saw other replies about how GitHub has a network of open source developers, but that didn't bother the SDL author before, and I don't see why it is bothering him now.
- rvz 6y ago
  If open-source organisations like RedoxOS, GNOME, GTK (Who use their own self-hosted instances of GitLab), etc are able to self-host, surely SDL can too, thanks to the new technologies out there that automates this. When your entire project is sitting on GitHub like nearly everyone else out there and something goes wrong, don't be surprised when one has to tweet at the CEO of GitHub if the repository is falsely flagged for 'some reason' or if your GitHub actions, pull requests and packages are experiencing a degraded service. [0] https://news.ycombinator.com/item?id=22663627 https://news.ycombinator.com/item?id=22663627 [1] https://news.ycombinator.com/item?id=26066365 https://news.ycombinator.com/item?id=26066365
- qbasic_forever 6y ago
  You missed a key point that the SDL author raised--they're tired of maintaining all the ancillary software around a project. Every minute they waste troubleshooting a CI/CD failure, bugzilla limitation, etc. is a minute taken away from working on their actual project. And as this is an OSS project of love and not their full-time job it's even more infuriating for them to waste their free time janitoring services. Gitlab self hosted is fantastic, but it's far from 'set it and forget it' maintenance. There's significant technical overhead to keeping it updated, secure, migrating its database with major releases, scaling out the underlying hardware as project demands increase, etc. Moving to a hosted platform like Github solves those problems and gets them back to being productive on their project. The authors are really lamenting that they have to give up control of their project's source code and tie themselves to a new commercial offering (something that history has shown us over and over will inevitably lead to more technical debt in the future as platforms fade--just ask any former sourceforge, google code, etc. user). I don't blame them--it's sad to see that the state the art in self-managed OSS source code never progressed much beyond "become a domain expert in server operations and kludge together a suite of tools with wildly different UI, management and operations; also, documentation is non-existent or wildly out of date".

postalrat 6y ago

Thinking takes effort.

HotVector 6y ago

I see where the SDL author is coming from, but is it really that hard to get local GitLab instance running? Or even just using GitLab? I saw other replies about how GitHub has a network of open source developers, but that didn't bother the SDL author before, and I don't see why it is bothering him now.

rvz 6y ago
If open-source organisations like RedoxOS, GNOME, GTK (Who use their own self-hosted instances of GitLab), etc are able to self-host, surely SDL can too, thanks to the new technologies out there that automates this. When your entire project is sitting on GitHub like nearly everyone else out there and something goes wrong, don't be surprised when one has to tweet at the CEO of GitHub if the repository is falsely flagged for 'some reason' or if your GitHub actions, pull requests and packages are experiencing a degraded service. [0] https://news.ycombinator.com/item?id=22663627 https://news.ycombinator.com/item?id=22663627 [1] https://news.ycombinator.com/item?id=26066365 https://news.ycombinator.com/item?id=26066365
qbasic_forever 6y ago
You missed a key point that the SDL author raised--they're tired of maintaining all the ancillary software around a project. Every minute they waste troubleshooting a CI/CD failure, bugzilla limitation, etc. is a minute taken away from working on their actual project. And as this is an OSS project of love and not their full-time job it's even more infuriating for them to waste their free time janitoring services. Gitlab self hosted is fantastic, but it's far from 'set it and forget it' maintenance. There's significant technical overhead to keeping it updated, secure, migrating its database with major releases, scaling out the underlying hardware as project demands increase, etc. Moving to a hosted platform like Github solves those problems and gets them back to being productive on their project. The authors are really lamenting that they have to give up control of their project's source code and tie themselves to a new commercial offering (something that history has shown us over and over will inevitably lead to more technical debt in the future as platforms fade--just ask any former sourceforge, google code, etc. user). I don't blame them--it's sad to see that the state the art in self-managed OSS source code never progressed much beyond "become a domain expert in server operations and kludge together a suite of tools with wildly different UI, management and operations; also, documentation is non-existent or wildly out of date".