Why not just run one of the terminal-based clients in screen? rtorrent is a good option. And it can do things like watch a directory for .torrent files and you can set up rules to do things like stop the torrent after seeding to a certain ratio, so you don't even have to control it if you don't want to.

Of course it doesn't support the other protocols you mentioned.

Running a gnome app on kde would consume a little more memory. This is due to the fact that it also has to load the gnome libraries. However libraries are shared across all applications that use them, so if you have 10 gnome applications open the libraries doesn't take up more memory than if you had one open. Assuming that the gnome apps and the kde apps are equal otherwise, I would guess that you would be using only about 20-40mb more. So small enough to be negligible. If you like the kde desktop and gnome apps then run the gnome apps on a kde desktop.

Is this really true anymore? With devices like the Nokia N900 being released, that has full-featured browsers that can handle everything a desktop browsers can, I doubt this will be an issue much longer.

Right, because android existed back in 2005 when nokia released the nokia 770, their first linux-based device, and the first in the series of what is now the N900. They would never have tried that if it wasn't for android.

1. fork() works just fine, is extremly stable, and is faster than using threads on most platforms. I agree that perls ithreads implementation is a bit shaky, but most of the time fork() is simpler and faster anyway, so why bother with it? 2. What language is there than can't be decompiled? I can't think of one.

I care.

There are many great games for gameboy color, I had a gbc and about 10 games, but I haven't been able to play them for a while becuase I lost my GBC. I want to re-play them again some day.

Sure, this rom isn't needed for re-playing them, but its also a bit of preserved history. Thats one of the main reasons for dumping roms, its not all about piracy, its preserving a bit of history for future generations.

I have spent quite a bit reading on the subject, and I'm one of the people who belive that the "water ape" hypothesis is correct. I also think that the article linked to in this slashdot story is correct. Is this a contradiction?

Not really, the hypothesies (whats the plural of hyphotesis?) are not mutually exclusive. The water ape hypothesis gives a timeframe of us living mainly near shores and spending a lot of our time in the water between six and two million years ago, depending on who you ask, and personally I believe that its closer to the 6 million mark than the 2 million mark. And since this article is talking about what we did 1.9 million years ago, there is no reason they can't both be correct. We could have spent a few million years on the shores/in the water, then moved on to land, become meat eaters and learned how too cook. There is plenty of time for us to have done both.

I also agree with the hyphotesis that says that we started using fire around 2-3 million years ago, which seems to fit into this timeline nicely.

We travel trought time at every moment of every day. Oh? You didn't mean going forward in time at a rate of one second per second?

Do we still have the right to read?

That's a relatively well-known term among computer geeks who also likes reading fiction. It's used in multiple books/novels in the genre 'cyberpunk'.

Maybe it is slow, but currently that is the price for anonymity. If you don't think waiting a few seconds here and there is worth it for being anonymous then don't use services like this. There are plenty of people who think anonymity is worth a lot more than that. If you only want to be anonymous if its convenient and without negative side effects then you are probably not one of the ones who need to be anonymous.

He seems to be assuming that you only want to run a website on this service. I don't think hosting websites on this kind of service is a good idea at all. There are many other types of application you run on clould computing infrastructure, which makes much more sense, and negates almost all of his claims.

Consider for example a rendering farm. One day you may have two items to render. Another day 10 items. The next day 5 items. Should you really scale up and down manually each day, when you could just as easily just start the amount of servers you need based on how many jobs have been submitted for that day, and how large the jobs are?

There are many other examples. Websites are not the only thing you run on these services.

It stands for Internet Engineering Task Force, it has nothing to do with Internet Explorer.

You can read about them on wikipedia.