dkulchenko

I've had the same experience with other laptops in the past (my Asus netbook lost its ability to hold its charge altogether after 10 months), but my MBP's battery life has not degraded in any noticeable fashion after 18 months of heavy use.

Please elaborate, I'd like to try this out. I've been playing around with LXC for years, but assumed /sbin/init always had to be the root process.

(A) knowingly causes the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage without authorization, to a protected computer;

http://www.law.cornell.edu/uscode/text/18/1030#a_5

Books are great, but I prefer using solely online resources to learn; I find it to be a more efficient use of my time. Though there are notable exceptions: The Pragmatic Programmer (http://pragprog.com/the-pragmatic-programmer) and Getting Real (http://gettingreal.37signals.com/) come to mind.

1. Be realistic. Try to not let your ego get the best of you.

2. Look at the big picture. Sometimes you get so focused on one thing, you lose sight of what's around you. Evaluate everything that goes in: be able to compromise on some to win in others.

About being a kid in the industry: it's really no different. You get additional attention just for being your age, but aside from that, everything else is the same. I like it that way.

The former is how I've learned near everything over the past 5 years; I can't remember the last time I bought a programming/reference-type book.

The latter is invaluable for browsing through others' code and I find it to be the fastest way to pick up new concepts. Why look through theoretical examples when you can look at real-world implementations?

The JS that's doing the work is at http://imgs.xkcd.com/static/waldo.js. On page load, it sends a GET request to http://umwelt.xkcd.com/story/ghenkEggov8 with params w for the browser width in pixels, h for the height and r with the referrer. The rest of the qualifiers (geoloc and browser (user-agent)) can be determined on the server-side.

As a response, you get back JSON with the alt-text, image URL, and positioning info, which is then used to fetch and position the image.

Fun fact: the server-side is written in Haskell:

  $ wget -S http://umwelt.xkcd.com/story/ghenkEggov8
  --2012-04-01 11:26:41--      http://umwelt.xkcd.com/story/ghenkEggov8
  Resolving umwelt.xkcd.com... 208.118.225.100
  Connecting to umwelt.xkcd.com|208.118.225.100|:80...  connected.
  HTTP request sent, awaiting response... 
    HTTP/1.1 200 OK
    Server: Warp/1.1.0.1
    Content-Type: application/javascript
    Access-Control-Allow-Origin: *
    Transfer-Encoding: chunked
    Connection: close

Well done Randall and davean.

Remember 2009? iOS was ahead by a wide margin. The HTC Hero had just been released and Android was in that "this is cool, but could go either way" period. I remember considering buying the Hero but holding back, unsure whether the platform would take off.

It did. I don't see any reason why we won't see the same effect with the tablet market. It's just a matter of time.