Skip to content


5 Reasons Why I Run Linux.

It’s been a while since I’ve updated my blog. As nothing major has happened in my programming, I’ve pulled this file from my backups.  Here are my five reasons why I run Linux over Windows and OSX.

1) I can update of all the programs on my system with a single command.

With Windows and Mac, you have to deal with lots of stupid updater programs and constantly check websites for program updates. Then you actually have to install said updates once you realise that your system is out of Date.

With all major Linux distributions, there are people whose job is to maintain the programs provided by the Linux Distribution. Their job includes; updating the programs when necessary, modifying the programs so it will work on their Linux Distribution and ensuring that the programs to not conflict with each other.

The only drawback is that this system only works on two conditions; your Linux box is connected to the Internet, and that you do not mess with the program files (/usr directory) on your system.

2) Most of the Linux Desktop Managers support multiple workspaces.

Multiple workspaces are a wonderful idea, I cannot wait until Microsoft “borrows” this idea for Windows. They allow me to arrange the programs on the Desktop the way that I like then, and then switch to a new workspace in which I do the same thing over again. This is a not better than the “Windows Method” of minimising/maximising the program you are currently using.

Windows has attempted this for XP as part of their PowerToys suite. However I have found that it is too slow for my constant workspace swapping and on the odd occasion one of my programs disappears.

3) The middle click button on the mouse is used to paste text.

This was the initial reason why I stuck to Linux. Any text you select is copied into the X clipboard, and that text is pasted with the middle click button. After I switched back to Windows after using Linux for two weeks, I became constantly frustrated with my computer because nothing was happening when I press the middle mouse button.

4) You cannot purchase half a Mac and use it to upgrade you existing Mac.

As I am poor deprived university student, I cannot afford a shiny new computer whenever my old one breaks down. I just take out broken parts and replace it with new ones as necessary. I’ve been doing it for 6 years now, and although I’ve had to replace 3 main-boards, 3 processors, 10 power supply units, 2 sets of RAM, and 2 hard drives. And although I’ve changed its name twice, it’s still the same old computer I bought all those years ago as it still contains parts and peripherals from its original incarnation.

5) It is a lot easier to strip down a Linux System then it is to strip down a Windows or a Mac.

As a Linux Distribution divides everything into packages, it is really easy to remove the packages I do not need. Such a thing does not exist for Windows, it is all bunched up in a nice little directory called “C:/Windows”. I have managed to strip down Windows 98 SE to 8 MiB (17 MiB with DirectX 6) and Windows XP to 190 MiB. Stripping down your Operating System is an important skill if you are playing with underpowered systems (like a Carputer) or just need to free up those vital system resources.


There are many reasons why Linux is better than Windows, the two most obvious are Memory Management and Device Management. There are also many reasons why Windows is better than Linux, with again the two most obvious being interoperability with other Microsoft Products and Gaming. It just essentially came down to which system (Linux, Mac, or Windows) had the features that I wanted.

That is not to say that Windows is not worth it. I’ve purchased a Windows Licence a few times in my life, in my experience Windows is only good if you use your computer for;

  • Running a few programs (2, 3 or 4 depending on your Memory and Processor) at once.
  • Gaming, on the condition that you reinstall Windows every so often, as it keeps your system fresh and responsive.
  • That specific piece of software that does not work in Wine. This is the most common reason people choose Windows over Mac/*nix. I know a few people who are forced to dual boot Windows for the sole purpose of running their Internet Banking and/or Taxation Software in Windows.

Posted in Random Ramblings. Tagged with , .

Review for the Murder, She Wrote Board Game

Murder She Wrote was a Little Old Lady Investigator, solving weekly muders that “just so happen” to occour in the vicinity of her1 television show that was popular in the late 80s and early 90s. The show follows Jessica Fletcher, a popular mysetry novel writer, who is constantly involved in the muder investigation of the week.

Either a muder occours in her vicinity, in which case she becomes one of the suspects. Or one of her friends (or extended family members) is the prime suspect of the murder. Thus Jessica must detemine who the real murderer is and clear her/the suspects name, using her knowledge as a muder/mystery writer. To make each show unique, but similar, the following situations may or may not happen2:

  • She is either helped or hindered by the police.
  • The real murderer assists and/or hinders Jessica’s investigations. Turning on her when she discovers who the murderer is.
  • A kind, young man in his late 20’s does not believe that Jessica can solve the muder. The youth becomes Jessica’s companion/guide and is shown the finer arts of muder investigation.
  • The real murderer (or his/her assistant(s)) places Jessica under survaliance (either by following her and/or bugging her house, car, and/or phone).
  • The real murderer skips town in a yacht (and is usually caught by the police a day or two later).
  • The police do not want to do a full investigation, as one or more of the police investigators is corrupt and has been bought out by the murderer.

In the end, Jessica determines who the real murder and everybody else’s name is cleared.

During the shows prime, the “Murder She Write Board Game” was created and published by Warren. The game falls under the category of the who at the table did it style of board games.

The Murder She Wrote Board Game as played by (in order from left to right); Fred (the ghost of Mathew's dead lizard), my imaginary accountant, the spirit my once operationable Linux Server, and Me (the photographer).

The Murder She Wrote Board Game, as played by (in order from left to right); Fred (the ghost of Mathew's dead lizard), my imaginary accountant, the spirit my once operationable Linux Server, and Me (the photographer).

The Murder Shw Wrote Board Game is best summarised as an explore the map type board game (like Cludo) where one of the players (henceforth called the “muderer”) runs about mudering the (aledgably) innocent townsfolk. Everyone else (henceforth known as the “Jessicas”) must check the dead/alive-nes of each and every townsperson, and use their detective skills (AKA their deduction skills and memory) to determine who the “murderer” is before he/she skips town on a boat.

Well, I’ve typed a lot, now it’s time for the ‘review’ iteself

Complexity – 4/103

A great way to determine if a game is too complex, is to play it while under the influence of alcahol. I tried just that with the friends who gave the game to me and after 15 minutes everyone was confused as to what is going on, and the “murderer” gave herself away. This is definatly a game to play sober, probably while sipping tea and chatting about the weather (and such the like).

Play Time – 6/10

Suprisingly enough, the Murder She Wrote Board Game is the only board game that I own without an estimated playing time written on the box. I have not played the game enough times to get a good estimation on how long the game goes for. If I had to guess I’ll say that the average game with 4 players would last 45 minutes and a 6 player game would last five quarters of an hour.

Setup Time – 7/10

Although the game is easy to setup, it does require some people shuffling. Everyone is required to leave the room and then enter the room one player at a time. The “murderer” must kill one of the local townsfolk, while the “Jessicas” stare at the board for ten seconds.

Design – 7.5/10

The design of the board game was probably the most redeaming feature ofthe board game itself. The path is not too long, nor short. The inside sections (where the “murderer” preforms his/her killing spree in, and the “Jessicas” can check the dead/alive-ness of the building’s resident) are decently spaced, so it usually takes 1 or 2 turns4 to move between buildings.

The artwork on the board is also interesting, as with the style of 1980’s family board games

Unfortunatly points have to be taken away for the long distance between the “Escape” spaces (where the “murderer”, having killed everyone can escape in a yacht) and the “Accuse” spaces (where the “Jessicas” must be on to accuse one of the players of being the “murderer”). Which casts great suspission on one of the players when he is trying to land on a square that is a long distance away from the square everyone else should (at the final stage of the game) be trying to reach.

Uniqueness – 2/10

Sadly this game is not very unique, having no real decernable feature that I have not seen in other who at the table did it board games. This conformatity to the who at the table did it board game genre is the second reason as to why this review is so sparse.

The only thing about the game that is slightly unique is how the “muderer” murders the townsfolk (and I’m not going to tell you, you have to find and play the game to find out :p ).

Enjoyment – 5/10

I must say that I enjoyed the game more then Cludo. This doesn’t say much, as my memories of Cludo involve missing cards, blatent cheating and loud agruments over said cheating.

Overall – 5/10

The Murder She Wrote Board Game is one of your average 1980’s board games. It is not a game that I would play constantly, but it is a game that would be played on occasion when we are after something different from the modern and/or challanging games of my board games collection.


Footnotes:

    1. I had a strange time researching Murder She Wrote. The TV Tropes Murder She Wrote Wild Mad Guess Entry had the most insightful theories as to why Cabot Cove is constantly plagued with murders.
    2. I have only seen ~25 episodes of Murder She Wrote. After the first 12 episodes I realised that the episode’s plot involves one or two of the six main situations mentioned in this blog post.

    3.As the game does not market itself as a thinkers game, the more complicated the game is, the worse off it is for casual games.
    4.Or, in the worst case; constantly rolling seven ones travelling from the hotel to the tennis club.

Posted in Random Ramblings. Tagged with , .

Uni Life has taken one toll…

My university assignments have not been great this semester. I have to work on two (well, technically five) group assignments that require me to spend long hours huddled over a desk, scratching my head about why my team members (you know you are) decided to do what they did and then try to mould my work to match theirs.

That in itself is not a problem, I’ve been doing the whole moulding thing for three years. Trying to mould my skills so that my work matches what my assessors want me to do. This semester it has been different and it is beginning to show. Instead of being shown examples of how my work is supposed to look and feel; two of my courses (the ones I’m working on group assignments for), do not have any examples at all. Only a marking sheet, detailing how the assessment is going to be marked. Better yet, my google-fu is only showing me pages which describe what information I should include, not how to express it or even to what extent I should express it. This is because business spend thousands of dollars (and weeks of employee’s time) to draft these types of documents, and thus do not publish them on the public web.

This has led me to completely underestimate the level of work needed to complete these assignments. Combine this with the hassles of working in a group that barely holds meetings every week. Add in a little stress and my sleep problems (I cannot maintain a steady sleep cycle), and I have 13.4 days to a lot of work.

Thus, I am stopping my work on my PDRC4.01 entry. I have approximately 18 hours of development and 4 hours of testing left on the project, but I cannot fit it in my schedule if I want to finish my assessment. Don’t worry Keiran (they guy who gave me the idea), you’ll see a working copy of BlokTris in the not too distant future. I will restart work on the game when my assessment is handed in, but for now I have to put it asside.

Posted in Uni Life. Tagged with .

Gantt Charts Galore

Well, my life has been busy in the past week and I have not had any real time to work on my SNES projects. So in the interest of Project Management and Gantt Charts (which took up 60% of my work last week). I wondered how much work I have to do this week. So I did what now comes naturally, and did a gantt chart.

Here is a simple one, which does not take care of spontaneous events (like this blog post) or obvious events (like eating or sleeping).

Boy do I have a lot of work ahead,

Boy, do I have a lot of work ahead of me.

Posted in Uncategorized.

New SNES SDK Found

After just remembering that I actually have a development blog, I realised that it just contained my horrible idea of an advanced math library made from WLA-DX macros. After realising the idea is just too improbable, I have decided to remove all trace of it from the Interwebs (except this post of course).

My current attempt as SNES programming revolves around a SNES SDK that Lint blogged about. The SDK (found at http://code.google.com/p/snes-sdk/) contains;

  • A modified copy of TCC (Tiny C Compiler), that generates WLA-DX compatible 65816 assembly from a .c file.
  • A python script that optimises the output created by 816-tcc. (this still needs a lot more work, I can see a lot of rules that could be added to improve the final assembly output by as much as 20% (hopefully I’m not exaggerating))
  • A patched version of WLA-65816 and wlalink to compile the codes and link them together.
  • And, finally a port of LordTech’s SNESC demo to SNES-SDK.

The advantage of using this SDK over what I’ve been doing now, is that I do not have to worry about screwing up math on the SNES ever again (which lead me to attempt that horrible math library in the first place). I know this sacrifices a lot of CPU time and ROM space, but I’m sure that the cost will be worth it.

I’m currently testing out this SDK by using it to develop my entry to this year’s PDRC coding competition. I’ve nearly finished designing the game on paper and should have a detailed design in by the end of the week, ready for coding soon. If I am satisfied with my results, I will be using this kit in the future for other SNES projects.

Posted in snes-sdk. Tagged with .