3 ms·
Joe Armstrong on OO: Because the problem with object-oriented languages is they’ve got all this implicit environment that they carry around with them. You wante
by uggedal 17y ago
Joe Armstrong on OO: Because the problem with object-oriented languages is they’ve got all this implicit environment that they carry around with them. You wanted a banana but what you got was a gorilla holding the banana and the entire jungle.
- jcapote 17y agoDown modded you by accident (is there an undo?), that's a great quote
- byrneseyeview 17y agoSlightly offtopic: I think it would be possible to implement downvotes on stories, and undoing of votes, through an FF extension. What you'd do is this: you would sign up for the extension, and it would implement your actions by ignoring other people's actions. For example, user A wants to downvote a story. User B wants to upvote it. User A clicks the extension-added downvote button, and when User A clicks "upvote," the vote is discarded. Similarly, the system would undo your downvote by ignoring the next downvote. This is probably not an intended HN feature, though.
- astine 17y agoI don't think that there is anyway I would sign up for something that would allow people to cancel my upvotes. Even if I did, I'd open another browser to upvote and only us the extension enabled one to downvote, which would negate the point of the system. I don't think that it would work.
- apu 17y agoAn easier way to do it would be the way the "undo send email" in gmail works: you don't actually take the action for a few seconds, during which time the user can change his mind. My guess is that most accidental up/down votes are realized almost immediately, so this "grace period" would only need to be a few seconds.
- byrneseyeview 17y agoThat would handle accidental votes, but not votes that can't be made, e.g. downvotes. I think it would make more sense to have a single mechanism for all of these.
- hassy 17y agoSnappy quote, but it does not make much sense out of the context. "they've" must be referring to functions/methods, not programming languages. And in prototype-based languages methods aren't as tightly tied to data as in class-based languages, which is what I'm guessing Joe Armstrong criticizes here.