Rman Virgil wrote:An abstract is a brief summary of a research article - the original is 8 pages, what I posted considerable less and sans formula for the layman
An abstract is a summary that appears at the beginning of a manuscript, and is part of the manuscript itself.
Rman Virgil wrote:You need to brush up on the latest scientific research into psychic powers.
As long as the JREF prize remains unclaimed, I see no reason to.
Rman Virgil wrote:I can only offer what is strictly my work alone. This is not and those I play & collab with outside of this community do not want any of their work submitted to this project. Though we have the game itself in common there is a vast cultural-values chasm that is likely to never be bridged in much the same way that the Klan would never convince Mahatma Gandhi to lend a hand in a lynching.
There's a problem with this position. Namely, Warzone is licensed under the GPLv2. That means any changes to it
must be licensed under the GPLv2 as well (unless said changes are never published).
As the designer or developer of a new application, you're faced with hundreds of micro-decisions each and every day: blue or green? One table or two? Static or dynamic? Abort or recover? How do we make these decisions? If it's something we recognize as being important, we might ask. The rest, we guess. And all that guessing builds up a kind of debt in our applications — an interconnected web of assumptions.
As a developer, I hate this. The knowledge of all these small-scale timebombs in the applications I write adds to my stress. Open Source developers, scratching their own itches, don't suffer this. Because they are their own users, they know the correct answers to 90% of the decisions they have to make. I think this is one of the reasons folks come home after a hard day of coding and then work on open source: It's relaxing.
That only really works if you're the project manager of an open-source project, really. Else you still gotta argue with everyone else about which way is the right way. :/