1,062 karma · joined October 30, 2015
Mozilla has a blog post about doing efficient float32 math: https://blog.mozilla.org/javascript/2013/11/07/efficient-flo...
V8 bug: https://bugs.chromium.org/p/v8/issues/detail?id=5541
Using a Float64Array is faster at the expense of memory usage. (I've never seen a case where the code generated by V8 bottlenecks on memory bandwidth fwiw.)
> "We have found contraband in [courier] shipments," says U.S. Customs official Bob Fischler, "but percentage-wise it is infinitisemal. And in any seizure we made, it was obvious that the on-board courier had nothing to do with it." In fact, at New York' JFK and at London's Heathrow airport, because of the sheer volume of courier shipments, all courier pouches go to a central location for clearance. The courier is typically dismissed before customs physically inspects the shipments.
- From Air Courier Bargains by Kelly Monaghan.
I also like to say that the final analysis was automated. It was done entirely in Mathemtica notebooks that talk to a data-processing API, and can be re-ran whenever. The notebooks are getting released along with the journal article for the sake of transparency and reprodibility.
(Also, I automated my SSL cert renewal ;))
I happen to have just opened a PR to support indexed PNGs in node-canvas (HTML Canvas impl for node) based roughly on the proposed pixelFormat API [1,2] for the same reason that the space savings can be immense.
It's also straightforward to change the palette of an indexed PNG after it's encoded because you don't need to re-compress the body. This lets you do cool tricks with recoloring images.
[1] https://github.com/Automattic/node-canvas/pull/935 [2] https://github.com/WICG/canvas-color-space/blob/master/Canva...
Would be interesting to see these benchmarks on Haswell/Broadwell vs Skylake.
We're building a real-time, cloud-based bioinformatics data analysis application and seeking engineers to join our team. (No experience in bio needed.)
Ideally you have a passion for and experience with building highly interactive, creative interfaces (e.g. business intelligence or dashboarding apps, products like Google Docs). Prefer familiarity with Angular 1.5/2, web sockets, node.js and/or C++.
my username at primitybio . com
The cache is also a whopping 56 MB.
It would be nice if this was more explicit. For example, is traffic that is TLS-terminated at their LB reencrypted all the way to the back end VM? At what point is it decrypted again? Are those keys unique to us or are they used for whatever traffic happens to traverse the same network paths? (I assume shared but with software-defined networking maybe it's practical for them to be unique.) What does the "control plane" encompass?
In any case, I'm curious what people think about trusting the service provider for inter-service and inter-VM encryption. Do you use the LB's TLS termination? Do you still enable encryption for your DB connections even if it is (or will soon be) redundant with their network encryption?
We're building a real-time, cloud-based bioinformatics data analysis application and seeking engineers to join our team. (No experience in bio needed.)
Ideally you have a passion for and experience with building highly interactive, creative interfaces (e.g. business intelligence or dashboarding apps, products like Google Docs). Prefer familiarity with Angular 1.5/2, web sockets, E2E testing.
my username at primitybio . com
1. Overall, no net benefit. We still had to query a k/v store on every action to check that the token wasn't revoked.
2. Less secure because there's no way to make it act like an HTTP-only cookie (no access from JS).
3. No way to revoke all of one user's tokens because there is no list of those tokens. We want to limit (or be aware of) the number of active logins and let the user sign out from all locations (as you can in Gmail). If the token is only stored on the client, there's no way to do this. You could store a list of all granted tokens and only use it for these revocations, but that's yet another level of complexity. (When we dropped JWT, the diff was -1200+95 LOC because we had to handle a lot of scenarios like this.)
4. Adding tokens to client-side requests is a pain. The common example for e.g. Angular is to use an HTTP interceptor to add a header. More code, but it works... Except for img and a (anchor/link) elements where you can't add a header. So you put the token in the URL query instead, and now you're vulnerable to session leaking if a user shares a URL with someone else. And you have to manually update those embedded tokens when they expire, as many JWT folks recommend you make the expiry short.
Good riddance.
For example, [0] (2010) reports that ~5% of people in the US were positive for Ad36, 35% Thailand, 52% South Africa, 91%(!) Malawi, 88% Cameroon, 48% Botswana, 43% Brazil. Malawi, Cameroon, Thailand and Botswana are solidly in the lower % obesity parts of the map that you linked to, while the US has the lowest antibody prevalence and highest obesity. They don't have Ad36 data for Europe unfortunately, but ...
Ad36 is not the only adipogenic (fat-causing) serotype. Ad5, 9, 31, 36 and 37 are all correlated or linked to being adipogenic [1]. The above paper [0] has numbers for Ad5 if you're interested: Europe was 39% negative, US 31%, the African countries 10-13%, Brazil 18%.
[0] https://www.ncbi.nlm.nih.gov/pubmed/19925902 [1] https://www.ncbi.nlm.nih.gov/pubmed/26352001