ajro

That is why you should use unique password for each site.

But this in my opinion explains well both why people are seduced by forth and why forth is not widely used.

EDIT: also gives opinion why Chuck Moore can be successful using forth.

EDIT: spelling.

I am not sure about that at all. For imap for example you could be required to submit your password followed by one time code in single login command:

. login youraccount yourpasswordyourotp

So in the password prompt when the client connects you should type in your password + your otp in one step. But that is still two factor authentication. Of course there is no sense in caching/storing such password. It would be less convenient for sure but saying that you can't do 2-factor for imap is exaggeration.

http://news.ycombinator.com/item?id=2443089

In one of the comments on reddit ascheinberg wrote:

Like every single site like this, the problem is that the public is ready to ingest content faster than content becomes available, or rather, faster than worthy news is made, so in the lack of real gripping news, things of general interest fill the gap

So maybe we should try to slow things down by limiting number of votes/submissions per person per day?

If someone could submit only one story per day maybe he would do that more carefully?

The same applies to votes - with limited number of votes available someone would consider more carefully what to spend his votes on?

And as additional benefit making things slower on HN could have positive effect on our productivity ;).

If you posted a simple example of JavaScript written in continuation-passing style and using this call/cc implementation probably everything would be clear.

  function callcc (f,cc) { 
    f(function(x,k) { cc(x) },cc);
  }

Isn't emacs more popular among programmers and vi/vim among sysadmins/unix guys?

Why not to use real read-recepit requests (MDN, DSN) and respect someone's rigth to disable it in their mail client?

Of course there are rare cases that you need to trade size for speed. But it should be done with careful cosideration.

Edit: I forgot to add that I always thought that 'duct tape programming' means writing hacks to fix hacks - which is bad.