The thing that people need to keep in mind when discussing the GPL is that it was created to achieve an ideological and political goal, namely that users of software should have the right to modify and extend the software as they see fit. To achieve this goal, the GPL seeks to ensure that the source code is always available and that reusing the source code in question comes without any restrictions save for what the GPL itself imposes in order to ensure this "right" is never withdrawn.
Well, let's face it! Users love Games. Me too.
I still have some really great childhood memories, playing with those lovely old games.
Do you remember trying to save the poor Lemmings? Damn, they do seem predestined to fall!
Or what about XWing? And Dangerous Dave (a blatant game
copy of inspired by Super Mario)? I still have nightmares with the Aliens from X-COM every once in a while !
Yes, they are not "Crysis V" but these games have some strange power to keep
people me sitting for hours in front of odd-ugly graphics.
Some of the best adventure games are from that era: Day of the Tentacle, the first Monkey Islands, Sam & Max...
You would probably face tons of issues if you try to run these old games (DOS games) directly in Windows or Linux unless you use an app called DosBOX. For those who don't know about it, it is a (software) BOX where you can run DOS games.It's free, opensource and downlodable through ReactOS Apps Manager(rapps) !
But, no, this is not about DOSBox but about ReactOS...
Intellectual property is something way too many people like to talk about without actually understanding the nuances of the laws supporting them. While I could easily go on and on about these misconceptions, I'll focus primarily on those that relate to free software and open source, of which there are plenty. Some of the more prominent ones include incorrectly claiming what is and what is not a GNU Public License (GPL) violation and the notion that companies should "just" go and open source their stuff.
It is somewhat difficult to put into words just how much hate I have for this particular issue. Debugging it ended up taking an entire week and the result surprised pretty much everyone on the team, including the senior developers. The issue that was highlighted however has very deep root causes that touch upon the very foundation of the C ABI and its brittleness.
Weclome to the second part of the series where I discuss bugs that were truly irritating to debug. In general, fixing a bug is usually simple. Finding the bug is where the actual work is involved.