121–130 of 345 posts
supplied by deadbeef\n\n\
cracked by rOn\n\n\
32kb cool intro by lone";
Edit: Apparently it's an Easter Egg! Credit to bri3d for research
Earlier quoted context omitted.
Windows executables mostly work forever. Especially if they were widely distributed. If Winamp is broken on Windows N+1, it's Windows that is broken. If Winamp is broken on Wine, it's Wine that is broken.
May have been true 20 years ago. But these days it is not hard to find a game which works in Wine but not Windows. And DirectX is often the reason.
I have Master of Orion 2, which came out when DirectX was in version 1.0. It technically executes in Windows 10, but the graphics are glitchy.
When they re-released it on Steam along with the MoO remake, they actually packaged the DOS version with DOSBox rather than release the Windows version.
Earlier quoted context omitted.
> No Forking Amusing; there are already 6 forks on GitHub as of this writing.
Now 52 forks on GitHub. Thug life.
This is like a park having a sign on the corner telling you to not step on the grass because it is privately owned but people go and make picnic there anyway
Are there any tools that can receive an entire code base like this, then analyze and answer questions about the code, structure, functionality?
Open sourcing is always good, because maybe you can learn some things by reading it. Also, Winamp Legacy is a fairly important piece of software, so having an archive of its source is a great thing. But the restrictions on the source are interesting. To quote the license file: * No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form. * No Forki…
This seems to go against GitHub's own ToS[1]: > By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). [1] https://docs.github.com/en/site-policy/github-terms/github-t...
Earlier quoted context omitted.
The language is pretty clear to me. I understand what you’re saying, and suspect that this is an honest oversight on their part, but as it currently reads forks are prohibited. They may have meant something else, but what it says now is “no forking.”
They know exactly what they're doing. They're open-washing the program to get attention. It worked. As I write this, it's the number one YComb story. But, it's in no way, shape, or form open source.