Java allocation might be more optimized than malloc. But garbage collections is often slower than free, for large apps (practical observation).

For me, the problem is not clicking, but dragging.
It starts feel like nails on the blackboard.

Personally, I find that I am slowly developing an RSI type problem wrt touchpads and touchscreens, preventing extensive use. Anyone else?

Just wait until the DRM activates the 'Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses' mode.

Duracell(r)

My problem with both go and javascript is the problem called 'implicit semicolon insertion'.

For me, the acceptable solution to Python is to make the 'pass' keyword mandatory at the end of block.

Emacs can auto indent based on this:

    if True:
        a
        b
        pass
    c

Too bad they added significant whitespace. I'd support a semicolon-less syntax, but not at the cost of significant whitespace.
Perhaps an alternate function call syntax or using {}instead of () in expressions would work.

IMO every Quake Instagib server should have a (callvote) option for insta_weapon 1 (great fun, but
aimbot cheaters usually get bored very soon)

IME, GC can only be faster if you can afford to 2x the RAM (physical, because virtual more or less doesn't work for GC, unlike malloc/free) and you have problems with fragmentation in malloc/free program (but going to 2x RAM will more or less solve it there too).

Please don't say that GC allocation is fast without accounting for freeing too, otherwise you are just moving the bottleneck where it cannot be easily accounted for.

There are two reasons for not using wave:
1. it's slow (even firefox 3.6).
2. no "standalone server" yet, that I could install at work, or for my _private_ stuff

Because thats 1000 times worse than 2 or more toplevel windows.

Click to focus makes sense to users that mostly use the keyboard (also for switching focus). Especially since mouse focus is/was often incorrectly implemented as "focus window under mouse".

If you use only the mouse, you don't need focus anyway.

Try it with a horse.

>There is still no excuse for Toyota not coding the ECU to cut throttle when it senses that the driver has BOTH the throttle and the brakes on simultaneously. All drive by wire VW/Audis are setup this way.

I really hope this happens only partially and under hard braking.