Indeed, you can see in the article that the text of Theorem 7.2 omits for brevity details which are present in the non-pretty printed Lean proof (for example H is non-empty, K is a real number, etc.)
84 karma · joined January 24, 2011
Indeed, you can see in the article that the text of Theorem 7.2 omits for brevity details which are present in the non-pretty printed Lean proof (for example H is non-empty, K is a real number, etc.)
And here's a post about it: https://www.reddit.com/r/learnmachinelearning/comments/oa7x3...
> Risks of global aggregate impacts are moderate for additional warming between 1–2°C, reflecting impacts to both Earth’s biodiversity and the overall global economy (medium confidence). Extensive biodiversity loss with associated loss of ecosystem goods and services results in high risks around 3°C additional warming (high confidence). Aggregate economic damages accelerate with increasing temperature (limited evidence, high agreement), but few quantitative estimates have been completed for additional warming around 3°C or above. [0]
I've always wished more scientific (or pop science) writing followed this approach.
[0]: https://www.ipcc.ch/site/assets/uploads/2018/03/ar5_wgII_spm...
We're on a mission to shift $1BN in advertising budgets towards independent content creators, so we're after someone with frontend and backend development skills to help make that happen.
We're looking for a full stack dev with 3+ years of experience building software professionally, but above all we're after people who are excited about building world-class software, getting their hands dirty with tough problems, and constantly learning.
Our stack is Rails 4.2, Angular, a PostgreSQL DB (now quite big, hundreds of millions of rows), Redis/Sidekiq, Gulp for builds - the whole shebang is at https://stackshare.io/peg/peg We recently moved into lovely new offices near Aldgate East, if you'd like to drop in and chat more about the roles, drop me a line: alex@peg.co
PS - We've recently added a fantastic developer to our team thanks to last month's Who is hiring thread :).
We're on a mission to shift $1BN in advertising budgets towards independent content creators, so we're after someone with frontend and backend development skills to help make that happen.
We're looking for one dev with 1+ years of experience building software professionally, and another with 3+ years; but above all we're after people who are excited about building world-class software, getting their hands dirty with tough problems, and constantly learning.
Our stack is Rails 4.2, Angular, a PostgreSQL DB (now quite big, hundreds of millions of rows), Redis/Sidekiq, Gulp for builds - the whole shebang is at https://stackshare.io/peg/peg We recently moved into lovely new offices near Aldgate East, if you'd like to drop in and chat more about the roles, drop me a line: alex@peg.co
We're on a mission to shift $1BN in advertising budgets towards independent content creators, so we're after someone with frontend and backend development skills to help make that happen.
We're looking for one dev with 1+ years of experience building software professionally, and another with 3+ years; but above all we're after people who are excited about building world-class software, getting their hands dirty with tough problems, and constantly learning.
Our stack is Rails 4.2, Angular, a PostgreSQL DB (now quite big, hundreds of millions of rows), Redis/Sidekiq, Gulp for builds - the whole shebang is at https://stackshare.io/peg/peg
We recently moved into lovely new offices near Aldgate East, if you'd like to drop in and chat more about the roles, drop me a line: alex@peg.co
We're on a mission to shift $1BN in advertising budgets towards independent content creators, so we're after someone with frontend and backend development skills to help make that happen.
We're looking for one dev with 1+ years of experience building software professionally, and another with 3+ years; but above all we're after people who are excited about building world-class software, getting their hands dirty with tough problems, and constantly learning.
Our stack is Rails 4.2, Angular, a PostgreSQL DB (now quite big, hundreds of millions of rows), Redis/Sidekiq, Gulp for builds - the whole shebang is at https://stackshare.io/peg/peg
We've just moved into lovely new offices near Aldgate East, if you'd like to drop in and chat more about the roles, drop me a line: alex@peg.co
/opt/letsencrypt/letsencrypt-auto certonly --rsa-key-size 4096 --server https://acme-v01.api.letsencrypt.org/directory -a webroot --webroot-path=$DIR -d $DOMAINS
...and using the secp384r1 curve for ECDHE key exchange: # in your nginx.conf
ssl_ecdh_curve secp384r1;
Arguably, the real state of the art is to use an ECDSA certificate. Let's Encrypt recently started supported them, they offer a equivalent level of security to RSA at much lower bit lengths (a 384 bit ECDSA key is considered equivalent to a 7680 bit RSA key) and a few recent TLS vulnerabilities (like DROWN) have targeted implementation details of RSA.The related records point is true though - indexes don't help if you're trying to implement multi-table search. Although then I'd argue a materialized view (refreshed with triggers) might be better than putting more columns into one of the data tables.
I think PostgreSQL fulltext search (with tsvector, tsquery etc.) is given an unfairly bad rap though. I'm not sure that "full text search works best when the text vectors are stored in physical columns with an index" is true - in my experience there's no performance penalty to just indexing the tsvector expression - no need to worry about additional columns or triggers.
I also think the assertion that the key problem is that "full text search is that words are broken up according to the rules defined by the language of the text" is very context-dependent. In many situations that's the most awesome feature of fulltext search. Usually when I search for "cat" I'm not interested in results for catacombs or categories, but when I search for restaurants, results matching restaurant (singular) are relevant too.
I definitely see that for a use-case like GitLab's, where the data includes code, full text search's stemming would be a hindrance rather than a help.
Because LetsEncrypt needs a very specific response to be served from a specific endpoint, you need this kind of total control to validate a domain and get a certificate issued.
And it's worth noting that while other developed nations are close to Japan in terms of life expectancy, they're WAY behind in terms of number of centenarians. Switzerland for example has an average life expectancy of 81.8 years, vs. Japan's 82.7. But Japan supposedly has 3.5x as many centenarians per capita (http://en.wikipedia.org/wiki/Centenarian#Centenarian_populat...).
https://github.com/mitallast/diablo-js
The code's not commented very heavily, but it's pretty readable nonetheless.
(Couldn't find one elsewhere, so uploaded files from this repo: https://github.com/canuckistani/Nyan-3D-Firefox-fix)
http://www.eurekalert.org/multimedia/pub/38262.php?from=1992...
Hihger res:
http://media.gizmodo.co.uk/wp-content/uploads/2011/11/Carbon...
window.App = new AppView
which I think is a good idiom.its just that they descend below the baseline, which looks a bit odd. The effect only appears at the default text zoom (on FF for Windows).
http://news.softpedia.com/news/Former-Kaspersky-Employee-Res...
It seems it's probably a beta version of AV 2009... Still embarrassing/potentially harmful to the company though - especially following the hacking of their website a few months ago (http://www.computerworlduk.com/news/security/3244882/kaspers...)
Apart from a couple of character encoding bugs, it seems to do a good job. I've uploaded the eBooks as html here:
http://alexpeattie.com/stackoverflow/html/
I've then been using FF/Chrome and a print-to-PDF driver to make PDFs (again, the only method that worked for me) which I'm uploading here:
http://alexpeattie.com/stackoverflow/
PDFs are taking a while to generate, esp. the larger ones. If anyone can find a faster method to convert the html files, let me know!