If it was over WiFi, I would be much more concerned
181 karma · joined June 29, 2011
If it was over WiFi, I would be much more concerned
https://github.com/facebookexperimental/eden
Previous discussion https://news.ycombinator.com/item?id=23124095
In the extreme case, imagine that your k hash functions are nearly identical: hash function `H_i` differs from `H_1` only in that the outputs for the `1`st and `i`th elements in the input space are swapped. Of the `N` elements in the input space, all but `k` will completely collide.
Well...
Comcast made IPv6 on-by-default to all residential customers some time ago (IIRC) and available (not sure if on-by-default) to all business customers. [1] Verizon requires all LTE devices to support v6 [2] and achieved >70% penetration in 2016 [3] (I'm too lazy to find a more recent statistic.) T-Mobile launched v6only in 2014 [4] and hit >90% in 2018. [5]
> Eventually, of course, the dam is going to break and IPv6 will become ubiquitous. ISPs will decide that buying blocks of IPv4 addresses costs more than providing new customers with IPv6 plus some kind of carrier-grade NAT for legacy IPv4 addresses. More website hosting companies will support IPv6 in response, and suddenly IPv4 will be so last-decade.
In short, that happened.
[1] https://business.comcast.com/help-and-support/internet/comca... [2] https://www.apnic.net/wp-content/uploads/2017/01/vzw_apnic_1... [3] https://archive.today/20160719154102/http://www.worldipv6lau... [4] https://www.internetsociety.org/resources/deploy360/2014/cas... [5] https://pc.nanog.org/static/published/meetings/NANOG73/1645/...
Unfortunately, they're essentially unauditable and sometimes frightfully broken, eg https://arstechnica.com/gadgets/2019/10/how-a-months-old-amd...
Fun times
The first paragraph of the readme starts with "Folly (acronymed loosely after Facebook Open Source Library) is a library of C++14 components" and gcc 5.1 is the first version (https://gcc.gnu.org/projects/cxx-status.html#cxx14) which supports all of c++14
The readme was updated and now reads
> folly supports gcc (5.1+), clang, or MSVC. It should run on Linux (x86-32, x86-64, and ARM), iOS, macOS, and Windows (x86-64). The CMake build is only tested on some of these platforms; at a minimum, we aim to support macOS and Linux (on the latest Ubuntu LTS release or newer.)
folly is used in FB opensource projects on Windows, macOS, and Linux (e.g. watchman) and Android and iOS (React Native, though that might not include the whole library.)
Often, when ls is being slow, you can speed things up drastically by disabling the things that require a stat (colors, -F, etc.) that are often added by distro's shell files (invoking ls with a full path is an easy way to disable shell aliases.) Also, sorting is on by default, which slows things for obvious reasons.
When all you need to do is kill the stat overhead for small dirs on slow file systems, "echo *" is beautifully simple.
From user perspective, what is the point of saving file in a program that is falling over when you could potentially save a corrupt file and instead of retaining some of the work the user will end up with a blob of useless data. I guess you could do Save As... and then manually compare changed data with last save. Still I'd be extremelly suspicious of it.
I am absolutely shocked that nobody else has even hinted at this. I wouldn't recommend this tool in almost any circumstance.
what kind of low-latency phone do /you/ have? :-)
Now, the left sidebar, in addition to wasting ton of space, separates sections only by slight vertical gaps, makes almost no use of color, and displays [same screen size] 2 of "My" calendars, and 2 "Other" calendars.
The generally garish color changes, I could live with. Mushing the UI components together into a sea of whitespace, making them less distinctive, and wasting most of the screen, on the other hand...