31 karma · joined April 10, 2010
So maybe it has to do with more than just DPI, but generally I've read that high-DPI screens have no trouble at all with displaying antialiased fonts. (And yes, I have tried numerous calibration tools, with no luck).
If you're going to read K&R, make sure you visit the Errata page. There are a bunch of examples that have typos (some of them are not on the Errata page though).
But reading one C book isn't going to teach you everything about C. A lot of the C code out there makes heavy use of macros and multiple pointer indirections, which isn't covered in much detail in K&R. And if you're interested in the newer C99 standard, The C Primer is a great book (but it's quite thorough, which imo, is a good thing).
If you're going to try out the examples from K&R, pass these arguments to gcc: -ansi -pedantic -Wall -Wextra -g
The -g flag is for debugging symbols. I think I still have most of the fixed examples from K&R that will compile, if you're interested in these. Also, make sure to bookmark these two links:
http://www.eskimo.com/~scs/cclass/krnotes/top.html
http://users.powernet.co.uk/eton/kandr2/
The first one gives you some better explanations of what has been said in the K&R book (divided by chapters). The second one has most answers to the exercises in the book.
E.g. the D language doesn't have a very modern looking website atm., but someone has took the task to update it recently. It's not up yet since the community is trying it out.
"Fortunately, it seems I was able to acquire access to the VP8 spec, software, and source a good few days before the official release"
And you're absolutely right about making decisions, they have to be made. Anyway, I don't want to steal the topic, but thanks for the handy reminder. :)