dcherman

This seriously sounds like malpractice. If I were you, I'd be consulting a lawyer.

Is it really unfortunate? It's a matter of opinion. I find a single `var self = this;` to be much more readable than many .bind(this) calls when you're several levels deep.

I'm sure this was made in jest, but this is probably a real concern with folks at the NSA. With stuff like this becoming consumerized and easy to use, how long do you think it's going to be before some jerk decides it'd be a good idea to strap a bomb to one and fly it into a building?

Not true in directives where the point is to do DOM manip. The only reason you can "avoid" jQuery is because they provide a poor man's replacement in their jqLite implementation. To this day I still don't understand why they made that decision.

If that's how you interpreted my response, then I apologize; that was not my intent. It was simply an observation directly responding to the post immediately above mine, not intended as a generalization.

The vast majority of cyclists that I've encountered are perfectly fine and do not engage in those behaviors I was referring to. I've simply noticed that often the ones that are loudest and most outspoken about "sharing the road" in these debates are often the ones that seem willing to share the road the least, and that immediately changes the tone from a productive one to one of "us versus them".

So in other words, you believe that "sharing" means bikers own the road. I think you need to understand what sharing means, and it doesn't mean that you get to be an unnecessary annoyance to others.

This is the type of attitude that does not help driver/biker relations.

I know this is ( hopefully ) not a common occurrence, but let me tell you something that I recently witnessed.

I was driving on back-roads to my parents house, and it's not uncommon to see bikes on these roads since they are pretty good biking roads as I understand it. The difference is that these bikes were riding 4 wide on a single lane road, and they had a car in front of them driving between 15-20mph with their hazard lights on, presumably in an attempt to keep cars from passing them.

How is this not "owning" the lane? That was not the first time I've seen this happen either. Bikers also need to understand that this behavior is not reasonable.

I understand that not all bikers share this mentality, but I do often feel like "sharing the road" means "what's mine is mine and what's yours is mine" when I see people doing things like this. This does not help driver/biker relations.

So I know this is an idealistic point of view, but:

1. It's documented to return `null`. The fact that it returns undefined in some edge cases is a bug. If you want to be nice about it, you can approach them and explain the upcoming behavior change as a heads up, however it's still a bug that should be fixed.

2. No sympathy for those projects here; you can't use undocumented/private interfaces and expect them to be officially supported. I do it myself, however I do it with full knowledge that every single version change is potentially breaking to me, and I make sure to have unit tests to confirm the behavior still exists in X version. I may also approach the project and say something like "Hey, I found using X undocumented interface is actually really useful, how can we expose this as an official thing?"

The link to `Thierry Nicola's post about his use of React` is broken FYI

That's pretty scary. That implies that in addition to the target, anyone in the general vicinity of the target ( up to whatever the range of these things are ) would be tracked as well.

It's a good thing we can trust our agencies not to keep databases containing this unrelated but invasive information....right?

That code snippet is also using a faulty technique for identifying an Array. Although it will work for the majority of cases, if you're using an array from a different iframe, the instanceof check will fail since the Array constructors are not the same.

You should be using Array.isArray ( ES5 compatible browsers ), or Object.prototype.toString.call( obj ) === '[object Array].

Lodash, Underscore, and jQuery all provide utility methods to do that comparison for you.

I'm pretty sure it's due to http://es5.github.io/#x10.4.2 section 1A.

Calling eval like that causes it to be an indirect eval call which results in it being executed in the global context.

Out of curiosity, do you have a source for this? I developed tinnitus last year and currently do wear earplugs while sleeping, however I certainly don't want to make it worse.