aaronm67
Also - cheap land does not mean that it's cheap to build and maintain. Almost all of the infrastructure required to build (sewer, power, roads, etc) scale up with area, not density.
In NYC and SF, you'd never fill your contract if you were trying to pay < 150.
They aren't -- this is exploitable in the browser if not patched at the OS level.
> For a drive-by exploit to work (assuming there is one, just because a site is "shady" it doesn't mean it will be 100% sure that it will try to infect your computer with something) it will need to make a TON of assumptions about your setup
If you run these on an ad network, you get access to millions of different setups - you don't need to make any assumptions, you're virtually guaranteed to find someone with a vulnerable setup.
The goal of this license is to encourage more companies to contribute to open source, not to encourage usage.
All these certificates do is make it so Google's browser (and only Google's browser) will mask the fact you're on Google's domains if you sign the file a certain way.
If anything, this shows more anti-competitive practices -- they're adding features into their browser that specifically benefit a features of their search engine.
Requiring a long password on a site where the impact of a breach is minimal is not a good policy, you're just going to get people who can't ever login.
Construction in NYC is far more expensive than anywhere else in the world, largely because of union contracts.
This all to save a fraction of a microsecond on an operation that's called 60 times on the page.
If all you're using jQuery for is a document.querySelectorAll polyfill + the most primitive event handling, you're possibly safe, as those don't change terribly often...but at that point, you should probably be using a different library or a custom build of jQuery.
https://www.youtube.com/watch?v=KcOQfYlyIqw
It's pretty interesting, and can be done in a way that doesn't require any user input.
You're right, you're not going to use this to encode movies or very large media files, but for encoding shorter clips, the performance isn't unreasonable.
For building a "stripped down" version, there is a config flag "--disable-everything" that can be used, and I will investigate it a little more. We probably won't end up hosting the compiled file, just out of the interest of repo-size, but I can certainly build a "build-minimal" script.
_([ ... ]).map( ... ).filter( ... ).value()
They've made tabs slower to open and have gotten rid of configurable keyboard/mouse shortcuts -- it's now just Chrome with a different skin.
http://jsbin.com/odupog/1/edit
Either way, should alleviate some of the privacy concerns, as you can only get ClipboardData from elements where "paste" has a visible effect.
document.body.addEventListener("paste", function(e){
console.log("paste event fired")
})