I have been using Gnome 3.2 since Ubuntu 11.10 came out. So far I have been liking it quite a lot, it feels really natural and clean way to work. Before Gnome 3, I have been using Awesome & Gnome 2 desktops for years.

Gnome 3 extensions seem to be really easy to install, just two clicks and that was. I was already using some via ppa's, but this seems nicer.

Now, just if I can get automatic window tiling extension Gnome 3 would be perfect (there is manual tiling extension available, and one automatic one, but it is still buggy). Also, there is some small bugs in Gnome 3 still, but nothing earth-breaking anymore.

At least I like Gnome 3.

In past years, I have been using lots of different window managers. And still I run at least - LXDE, Awesome, Gnome3, Unit. I have always been quite flexible for using different ways of work, so I don't have any problem switching from Gnome 3 to Kde, or from Gnome 3 to Awesome - just short while of getting used to it and that's it.

I usually try out all new Desktops/Window managers which interest me, and run them for an week or two on my main laptop.

There is room for different Window managers/Desktops out there. I don't understand why there must be hate for one. Just switch to another one, it is your choice.

For me, Alt+{key above tab} works for jumping between application windows. And I am using Finnish keyboard, so it should work for Swedish as well.

You can use middle-button or right-click/New Window for that.

But, there is interesting difference:
if you click terminal launcher with middle mouse button, it opens it on new workspace. If you click it with right mouse button and select "New window" terminal starts on current workspace.

Why is that happening? I usually want it always to start on current workspace.

Agreed. Inbound connections should be blocked by disabling all unnecessary services which open listening ports. If service is not needed, then it should be disabled. If it is needed, then access to that service is probably needed too. Problem is, that in Windows it is impossible to disable certain listening ports.

Outbound connection blocking is much more valuable - if the malware is not clever enough to disable local firewall, it cannot open outbound connections.

If the vulnerable service is not needed, it should be disabled. And if it is needed, then it is probably allowed, or it won't work anyway? So how the firewall helps?

For example, if workstation needs file sharing service, it probably needs to allow incoming cifs/smbfs connections as well. And in that case, infected machine can use the service, regardless of the firewall.
If file sharing is not needed, it should be disabled. And that protects the machine without firewall. So how the firewall helps?

Local firewall can probably block outgoing connections, and that is about the only good use for one. But then, Windows allows software to modify some firewall settings, so probably that won't work anyway?

On my HP Compaq 8510w laptop with 3gb ram, I got totally different results. Firefox 3.0.6 was used in both Windows & Linux. At least I am happy Linux user, even I still have dual boot on my machine.

Linux ubuntu-810 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux

RESULTS (means and 95% confidence intervals)
Total: 4006.6ms +/- 1.3%

    3d: 471.8ms +/- 9.4%
        cube: 168.4ms +/- 19.6%
        morph: 176.4ms +/- 17.7%
        raytrace: 127.0ms +/- 14.5%

    access: 573.8ms +/- 5.5%
        binary-trees: 85.0ms +/- 29.3%
        fannkuch: 197.8ms +/- 16.5%
        nbody: 188.0ms +/- 6.8%
        nsieve: 103.0ms +/- 19.7%

    bitops: 452.4ms +/- 11.3%
        3bit-bits-in-byte: 87.6ms +/- 43.8%
        bits-in-byte: 98.4ms +/- 32.6%
        bitwise-and: 125.4ms +/- 12.6%
        nsieve-bits: 141.0ms +/- 20.7%

    controlflow: 61.8ms +/- 45.3%
        recursive: 61.8ms +/- 45.3%

    crypto: 256.0ms +/- 26.4%
        aes: 93.0ms +/- 18.3%
        md5: 81.0ms +/- 50.7%
        sha1: 82.0ms +/- 42.8%

    date: 415.0ms +/- 15.3%
        format-tofte: 243.6ms +/- 11.5%
        format-xparb: 171.4ms +/- 23.0%

    math: 467.8ms +/- 11.9%
        cordic: 165.2ms +/- 22.5%
        partial-sums: 197.0ms +/- 9.8%
        spectral-norm: 105.6ms +/- 33.2%

    regexp: 306.4ms +/- 11.0%
        dna: 306.4ms +/- 11.0%

    string: 1001.6ms +/- 4.3%
        base64: 142.8ms +/- 4.9%
        fasta: 228.0ms +/- 16.3%
        tagcloud: 181.6ms +/- 16.6%
        unpack-code: 325.8ms +/- 3.4%
        validate-input: 123.4ms +/- 20.8%

Windows XP SP3

RESULTS (means and 95% confidence intervals)
Total: 4917.4ms +/- 4.3%

    3d: 564.2ms +/- 13.9%
        cube: 209.2ms +/- 6.0%
        morph: 164.4ms +/- 37.6%
        raytrace: 190.6ms +/- 6.7%

    access: 779.4ms +/- 9.2%
        binary-trees: 116.2ms +/- 5.4%
        fannkuch: 328.4ms +/- 4.2%
        nbody: 189.4ms +/- 28.5%
        nsieve: 145.4ms +/- 37.9%

    bitops: 650.4ms +/- 32.3%
        3bit-bits-in-byte: 155.0ms +/- 43.7%
        bits-in-byte: 174.8ms +/- 29.5%
        bitwise-and: 131.0ms +/- 44.7%
        nsieve-bits: 189.6ms +/- 29.4%

    controlflow: 94.4ms +/- 40.8%
        recursive: 94.4ms +/- 40.8%

    crypto: 409.2ms +/- 31.0%
        aes: 136.8ms +/- 14.2%
        md5: 130.0ms +/- 40.7%
        sha1: 142.4ms +/- 41.9%

    date: 385.6ms +/- 16.2%
        format-tofte: 209.4ms +/- 23.4%
        format-xparb: 176.2ms +/- 9.9%

    math: 575.0ms +/- 8.4%
        cordic: 250.4ms +/- 14.2%
        partial-sums: 213.4ms +/- 13.2%
        spectral-norm: 111.2ms +/- 53.9%

    regexp: 278.0ms +/- 26.2%
        dna: 278.0ms +/- 26.2%

    string: 1181.2ms +/- 10.2%
        base64: 169.0ms +/- 20.7%
        fasta: 262.2ms +/- 14.2%
        tagcloud: 188.2ms +/- 32.6%
        unpack-code: 361.6ms +/- 24.6%
        validate-input: 200.2ms +/- 21.5%