Sunday, November 22, 2009

Garrys mod


For any of our readers who plays Garrys mod we have a 2 player server which will be up for a month on a trial. Currently me and Mekapedia are the only admins of the server. Ill try and be on it as much as possible. If any issues arise or you want to suggest an addon send us an email.

Server ip: 205.234.159.101


Friday, November 20, 2009

The Lessons of Plan 9

In 1969, two researchers in AT&T Bell Labs came up with an operating system that would influence the entire computer industry for years to come - this was called Unics, in spite of Multics. It was shortly after changed to Unix.

Unix has influenced every major operating system to date, and indeed, every major one except Windows is based off of it. It's combination of portability and usability has enabled it to flourish in many areas. Indeed, in the 1980s and thought the early 90s it was the most dominant operating system, but ultimately Windows succeeded due to the "Unix Wars".

But this is not about Unix specifically.

It is about Plan 9.

Plan 9 was conceived in the mid 1980s as a successor to Unix, from the same people who developed Unix. It was the epitome of the Unix philosophy - everything was represented as a file, every program did one thing, and did it well. It introduced "9P", a unified communication standard that allowed access to everything in the same way, and across the entire network. It was a fantastic system, far outpacing Unix and Unix-like systems in design.

But it had one folly, one flaw that could not be corrected by any amount of operating system design.

Unix.

It was inferior - Plan 9 was by far a greater system. The issue was that everyone used Unix - and no one thought that it was worth their time to upgrade, because Unix did the job well enough. Eric Raymond eloquently describes this in his book, The Art of Unix Programming:

"Plan 9 failed simply because it fell short of being a compelling enough improvement on Unix to displace its ancestor. Compared to Plan 9, Unix creaks and clanks and has obvious rust spots, but it gets the job done well enough to hold its position. There is a lesson here for ambitious system architects: the most dangerous enemy of a better solution is an existing codebase that is just good enough."

And thus, another great advancement in computers was turned down, something that repeats itself it history many, many times, as we can see from Macintosh: it fails capture most of the market share for the very same reason.

It wasn't all useless, of course. From Plan 9 we got both the /proc filesystem (even though this was introduced in Version 8 Unix, is was expanded upon in implemented to a greater extent in Plan 9, and this is the version of /proc that most Unix-like systems use, or base their implementations off of) and we got UTF-8, which was made specifically for Plan 9.

But these are but the basic Milk Chocolate bar and Nutty Chocolate bar if Cadbury's were to go out of business.

And what can we take away from this?

Systems where the advantages cannot outweigh the cost of implementation will not succeed.

And this, of course, applies to Linux. And Macintosh.

Cost is not just monetary, it is in time as well. People do not take time if they can avoid it. Indeed, most people never change the operating system that comes with the computers that they purchase, and never will. Linux is at a major disadvantage here - it's market penetration preinstalled on computers is small, though the growing netbook sector is a huge boost, most people still opt for Windows.

Why?

It's because Windows works for them, and they have no need to change what they are doing.

Linux is undoubtedly better then Windows as an Operating System, and so is Macintosh. The issue is, no one cares. This is truth.

And indeed, for people that do switch, Linux is inferior for 90% or the population 90% of the time to Macintosh. Why? Macintosh is easier to use, it's more stable, and likely, faster (compared to Ubuntu, do to drivers). It also has a superior support network.

And that is why Linux will likely never be anything but the pet of Google - because even the mighty Canonical cannot implement the system to an extent that people will use it. Google will - the penetration of netbooks, coupled with Google vast resources and propaganda machine - will allow it be successful. Linux will still have the niche market of geeks, but for the majority, it will be something that relates to Google Chrome OS.

And indeed we can learn from Plan 9 that likely this hierarchy will change only rarely, and only because large companies are major supporters. Chrome OS will dominate for a long time to come, and Linuxes such as Ubuntu and Fedora and Gentoo will all stay in relative obscurity.

Why am I saying this? Do I detest this order?

No, not at all. It simply is. We should embrace our niche - not go around complaining that it is not big enough, as it likely will never be.

Thursday, November 19, 2009

Google Wave

Hello blog readers!
As promised, this is a review of Google Wave, and yes, after this review I will be giving out one free invite to a lucky reader. Alright now without further ado; I present to you; My Google Wave review.

When I received my Wave invite I was ecstatic. There is a certain prestige that comes with having Google Wave, especially if your friends are as geeky as mine. So when I logged on the guy part of my brain wanted to click everything. After doing this for a while I thought to myself, "This is cool, but who is going to use this?" Initially it is very hard to imagine one using this is ones everyday life. One thing that I couldn't get over was the cluttered nature of the thing. Anyone can edit any part of the wave and that can get messy pretty quickly.

As I used it for a while I started to come around. I could see how people would use this. Google describes it as "Email-2.0" but I don't think that this will replace email. I had an opportunity to work on a project with a friend who also had Wave. Google wave is a great tool for collaborating on projects, but thats it. The difference between this and something like Google Docs is that when you use Google Docs you are left with something finished that you could hand in to a teacher or boss. Wave works more like a brainstorming session or a meeting. It's really good for planning and discussing, but it won't produce a document. In ots of cases all that one is looking for is an easy way to collaborate over the Internet.

Wave gets easier to use the more you use it, it is actually quite intuitive. One nice feature for users with Google gears installed is that you can actually drag and drop files from your desktop into the Wave. I also like how Google incorporated bots into the system. There are loads of bots you can use, all with a different but useful function. These range from a phycatrist bot, to a Twitter bot, to a blogger bot , and even a bot that translates your message to a different language as you type. There is lots of potential for Google wave to grow through bots and through extensions, which are rather limited right now. On thing that I'm not fond of is the live typing feature. I haven't found a way to disable this yet but it is really irritating. As the name implies it lets all other editors of a wave see exactly what you type, as you type it. At first this seems like a great idea, but for a terrible speller like myself it can be rather embarrassing. I can recall a conversation on wave I had with my friend where he typed "Half naked" instead of "Half baked". He corrected his error but not before the other editors of the wave had seen it. This is a really negative for me, but I'm sure in the future there will be a way to turn it off. Another useful feature is "playback". This lets you go through the wave in chronological order and see how it has progressed.

In conclusion I'd have to say that this is a great product from Google. Its still a little half naked baked but keep in mind that it is still in the preview stage. I think that people will use this service and it will be quite successful. Good Job Google, keep up the great work!

Finally, we come to the part of the post where I give away an invite to a lucky reader. If you havn't read the post yet and you just skipped down here to get the invite, go back and read the post then come back. Done? Ok, here is the deal; first person to email the Guys On FOSS email account (guysonfoss@gmail.com) gets it, please include the email address you'd like me to send the invite to in your email. I'd also appreciate it if you left us some feedback on this review.

If anyone would like to converse with us on Google wave and you have an account already you can do so by adding us to your contact list with this address: guysonfoss@googlewave.com

-The Thoth-

Saturday, November 14, 2009

Short post today!

Stay tuned to the blog over the next week, because with my google wave review I will be giving one lucky reader an invite to... Google Wave!
-The Thoth-

Friday, November 6, 2009

New logo

I hope you like the new logo to the blog. If you want to download the Gimp source file here's a link to it. If you dont know what Gimp is, its a advanced image editing tool that has similar tools Photoshop. Here's a link to download Gimp for Windows. If you want to download it for a certain Linux distro here's a link to all the different commands for different Linux distros. Finally here's a link for if you use a Mac.

Thursday, November 5, 2009

Google Wave... Guess who's got it?

You've read about it, you've heard about it, you've dreamed about it. Now one of the Guys has been invited to test it. I am of course referring to the new Google Wave.

Its true, I've been invited by a good friend to try out Google Wave. I've only had it for about a day now, so I'm going to play with it for a while and then write up a little review for the blog. Stay tuned to this blog to read my review.

-The Thoth-