A long time ago I gave an example of how people use PDFs when they shouldn’t. Later I followed up with a bit about how Adobe Acrobat is a grotesque resource hog that makes Jabba the Hutt look like Jenny Craig. Now to complete the trilogy we have this slashdot story about various security flaws within either PDF files or Acrobat. Like so many Slashdot stories, it has these frustrating gaps in the piece so that the users can read the whole thing and still come away with enough diverging interpretations to get a really good flame war rolling. A key quote:
Ok, so is this a fundamental flaw in the design of PDFs or poor implementation on the part of Adobe? By saying “features supported by the product” it leaves open the view that PDFs are inherently flawed and Adobe just followed the spec. I doubt this, but the story isn’t clear enough.
Either way, it sucks and does little to improve my opinion of the PDF format. There are a very small slice of people who need it and use it well, and an army of imbeciles who misuse the thing on a grand scale.
In Defense of Crunch
Crunch-mode game development isn't good, but sometimes it happens for good reasons.
What is this silly word, why did some people get so irritated by it, and why did it fall out of use?
Quakecon 2012 Annotated
An interesting but technically dense talk about gaming technology. I translate it for the non-coders.
Fixing Match 3
For one of the most popular casual games in existence, Match 3 is actually really broken. Until one developer fixed it.
Bethesda NEVER Understood Fallout
Let's count up the ways in which Bethesda has misunderstood and misused the Fallout property.