kwamenum86

Expert troll?

The day I left Hacker News and didn't look back. Sick and tired of this "community".

Actually an improvement

This reads like satire especially toward the end

this smells like a js engine optimization. you wouldn't expect substantially different machine code to run for "Direct assignment" and "other". i wouldn't be surprised if the loop is being unrolled or something.

If this is their IP they should license the technology out to an established company. If this isn't their IP they're kind of screwed anyway.

Pathetic? Care to elaborate on that?

that's kind of the point...

I see some criticisms (that I agree with) of the "security" model here.

Implementing the self destruction protection on the client is problematic (even in the case of SnapChat) because the end user is in control of the client. So if users are motivated enough they'll be able to circumvent any protections you implement.

The nice thing is that most users are not motivated enough to do what's necessary to retrieve the self-destructing messages. It's a lot easier to save the message when sent to a web client but it's still beyond the ability of most users.

So no these applications aren't providing real security but it's close enough for the types of messages that I assume people are sending.

Not CSRF. XSSI. It's actually completely different

Actually this prevents XSSI (cross-site script inclusion) not XSRF (cross-site request forgery).

XSRF vulnerabilities allow an attacker to issue web requests on a user's behalf; oftentimes though people only call it a vulnerability when you can issue a request that changes some state. And XSRF is usually prevented by including a hard to guess token with the request that is tied to the user and allows you to determine whether the request was generated by an authorized party. Please don't try to prevent XSRF by using while(1) :)

"It is ironic since whenever I have met with our elected officials they are invariably thoughtful, well-meaning people."

Maybe they come off as thoughtful and well-meaning because many of them are sociopaths. Indeed, politicians are much more likely to be sociopaths and psycopaths; they're great manipulators.

http://en.wikipedia.org/wiki/Antisocial_personality_disorder

http://en.wikipedia.org/wiki/Psychopathy

you probably run into that more with global functions, which this definitely isn't suitable for. but if you trickle a callback that just handles, for example, keydown on a single input, this sort of thing is really useful.

My favorite part is the tongue in cheek title for Tim Berner-Lee: "Web Developer". That's an understatement (as well as a perfectly accurate one).

Don't use this. Mutation events are insanely expensive.

Have to disagree.

This has already been mentioned elsewhere but comments with little value are already penalized when people downvote them.

If you notice more crap comments that aren't being downvoted that's because a) the community standards are changing and b) there's no good way to penalize all crap comments anyway - some will slip through the cracks. And as a result of b) great comments will slip through the cracks, which means people will lose points needlessly even when they're not trolling.

I'm not saying your proposal wouldn't have an impact on trolls. But there would likely be an awful lot of collateral damage.

You might find the fourth page of the code examples for the date function helpful. Shows several formatting examples.

Why doesn't it surprise you?

Smells like an acquisition in a year or so (and I mean that as a compliment). Congrats in advance.

Like a 3 clawed hammer, there simply is no reason for this :) j/k

It's really cool. And really impressive. And if you can make it perform well in the browser (big if I bet) I can think of several valid use cases. Nice work

First of all, technically this is a CAPTCHA still.

Second of all, you can eliminate the vast majority (or sometimes all) of your spam using honeypots much simpler CAPTCHAS like "what is four + 2?".

I don't think any of these suggestions make JSON easier to read, generate, or consume. What problem are you setting out to solve?

Opening paragraph: "JSON is strict. Keys need to be quoted; strings can only be double-quoted; objects and arrays can't have trailing commas; and comments aren't allowed."

If this represents a comprehensive list of the problems JSON5 solves I think you'll have a hard time rallying people around your cause.

Wait...when you say fail are you saying they fail to produce something optimal or fail to produce working code?

Thanks for sharing. I didn't realize you can do that with Github before reading your post.

This isn't really "pinning" a pull request. The problem is not that "GitHub Pull Requests are dynamic".

Any branch name is just an alias for the latest commit in that branch. For example master is just an alias for the latest commit in master so you can reference that commit without the SHA1 hash. When I submit a pull request for foo/master then push new commits for foo/master, I just changed what master points to so my pull request changes. By using the commit hash you avoid the commit alias problem because new commits won't change what a commit hash references.

In fact, virtually anywhere you use a branch name in git or github you can also use a commit hash.

Michael Bloomberg has a BS in EE. So this isn't that far-fetched. But thus was more a call to action than anythjng so Jeff Atwood is getting caught up taking a political platitude at face value.

Depending on what browsers you're supports it's probably far easier to use generated content (:before, :after). Maybe combined with calc or CSS expressions.

Kudos. This is very impressive. However, I think iframes + postMessage + xframe DOM/BOM abstraction is the more clean, reliable, usable, etc. way to go. Or defining a sandbox API for browsers that doesn't require iframes. But this could even be a nice first step towards that sandbox API.

Thanks for the clarification