Welp, that's true, my bad! It seems this rule was relaxed somewhat - mentioning the stack in the rules text is still frowned upon, but there's still some cards that mention it in the rules text (and a lot more that contains the split second reminder)
Note how the waterhouse's link - https://gatherer.wizards.com/Pages/Search/Default.aspx?actio... - contains a bunch of cards that were playtested but eventually rejected (they are the black-and-white cards with just a rough sketch in place of art), presumably because of the high bar that stack-fiddling cards should meet
Doing a search, I count 40 results with "stack" in their text; it appears that 18 of them have "split second", a few of them have "stack" in their name, several are from "Un" expansions or this weird "Mystery Booster" thing, several mention the stack in explanatory text about what it means to end the turn or end the combat phase... but there are several cards such as Grip of Chaos ("Whenever a spell or ability is put onto the stack, if it has a single target, reselect its target at random") that are from regular expansions.
Is this a recent standards change? I remember some legendary artifact that caused spells on the stack to be copied and explicitly described it that way.
I recently made a game pretty much just like this. It's like a game of Drawful mixed with telephone so you can see how the image changes through cycles of AI drawing and human interpretation.
In 2007 a conservative SCOTUS majority upheld a federal ban on partial-birth abortion [0]. Thomas wrote a concurring opinion where he explicitly glossed over whether congress actually had that authority under the commerce clause. Normally he jumps at any chance to say congress has exceeded their authority under that clause. I wouldn't find it hard to believe if this court upholds a more general federal abortion ban
If so, then the patch he submitted builds upon my work! He fixed a line feed conversion bug that was present in Windows. I use Linux so I did not experience this issue.
I remember seeing that patch get merged but I didn't know about the whole video game context. This is amazing. I wrote the patch because I was trying to print a 4096 bit RSA secret key as a QR code. Awesome to see it getting used for something even more awesome.
Here are the links to my contributions and related pages:
ZBar used to automatically convert binary data to text when decoding 8 bit QR codes, mangling the data in the process. My patch adds the option to disable that, enabling the data to be extracted without corruption.
I also added the one shot feature to the ZBar tools to make it easier to use in automated scripts that expect exactly one output:
Storing secret keys as QR codes is an interesting application as well. I remember reading on here about a CEO who printed out a database encryption key as a base64 string and then couldn't type it in correctly when it was needed to restore backups. A machine-readable format definitely seems the way to go.
So it turns out you can basically use type theory to encode a surprisingly large number of desirable traits about your program. (Caveat being that as you get more restrictive, you reject more "good" programs at compile time--no free lunch with Rice's theorem.)
It turns out you can encode a lot of other interesting properties in a type system (esp. if you're building on top of the existing type system), though--you can ensure that a java program has no null-dereference checks (https://checkerframework.org/ has a system that does this), and Coq uses its type system to ensure that every program halts (as a consequence, though, it isn't actually Turing complete).
There's also cool things like Lackwit (http://ieeexplore.ieee.org/document/610284/) which basically (ab)used type inference algorithms to answer questions about a program ("does this pointer ever alias?", etc.).
I really liked the message of each generation of programming considers the next "not real programming". It makes me reconsider the pushback against node-esque micro-packages: http://www.haneycodes.net/npm-left-pad-have-we-forgotten-how.... Maybe this is just the next logical evolution of programming.
