Personally, in my own code I also like to put pass at the end of all blocks. It's more consistent, and it also makes auto indent in the editors work properly. Anyone else?

Abusing javascript as a semicolonless language is a bad idea (Go also).

If you wish to have a langage without semicolons, design your grammar properly, not add kludges to the lexer.

I'm waiting for python to fix "from __future__ import braces". Or at least make "pass" mandatory for end of block

POST /orders/42?pay=1

POST was always about actions, not just resources.

An HTTP request has two parts: a resource (URL) and a method. Expressing your method in the resource rather than the, um, method muddles the two.

If it's a flash problem, I don't think Chromium has flash at all.

As the original article points out, this is not a flash related issue.

If RAM is precious, you shouldn't use GC anyway. It typically has 2x memory use overhead to reduce GC performance cost.

I don't see how it would be 2x: a minimal GC would just require an additional pointer per allocation (in the worst case) for the GC roots.

malloc() has overhead too, typically immediately before the pointer it returns there's data about the allocation, such as the size of the alloc, magic for detecting bad free()'s, etc (though I guess a simple slab allocator would just need a single bit for each allocation, plus a pointer per slab).

I like the same model. (send password change token to email). BrowserID from Mozilla may help here too.

Me too :(((

Agreed, but there's a solution. Emacs recognises the end of a block by using "pass" to end the block. This makes it reindent properly. It's not the official python style, but I prefer to write code that way. Try it, it's not bad.

Or the zeroth month.