Over the years I've held various positions with regard to copyright and paying for non-physical information. With the Times in the UK opting for a paywall and a website which is effectively all user-generated content that I frequent often also moving towards a subscription based model I have been thinking about where I stand again. I hold conflicting opinions, as I am both a producer of copyrightable material and a consumer of that material. I'm going to lay both of these bags of snakes out straight and see what they look like.
Not having an abundance of free time these days, my website is a little unloved, but not forgotten. I decided to write up a few updates on my Nexus 1, my PhD, and the latest websites I'm working on.
I'm a big fan of the site book crossing, where you can either post books to other people around the world, or leave books lying in a coffee shop waiting for someone else to pick them up. When they do this, they can read your book, they can register this on the site as each book has it's own unique code on the book.
I've been an Apple user for a few years now, and I don't see myself switching back anytime in the medium term. But the Apple laptop line-up has some strange configurations and I wanted to see which laptop is best in a couple of different categories. So, I took a look at the spec sheets, and I decided to compare the line in the following headings:
Google do some cool stuff, and there have been long-running rumours about the cool stuff they were doing with their servers.
It's well known that the servers they use are commodity, off-the-shelf type, but it turns out now that they do make some modifications to what you have sitting in the box at your feet.
I was recently doing some reading on algorithms, as I was reading up on Dijkstra's algorithm, I noticed that there seemed to be a lack of nice explanations out there. I found lots of applets, and demonstrations, but none of them had a step-by-step explanation, i.e. why certain events were occuring.
Eoinbailey.com still runs off Drupal 5, this is because I was using Project and Project Issue Tracking extensively for a while, but I have moved towards a different approach, and currently I don't find myself using Drupal projects.
Drupal 6 has a problem, Project and Project Issue are not yet ready for it, and they may never be (incidentally this is the reason why drupal.org is still on Drupal 5, and will stay that way for the forseeable future). It is also the reason why I am still using Drupal 5 on this site.
