You must be joking. When I needed a second MRI after a tumor was removed from my brain my very expensive health insurance denied the payment because it was medically unnecessary according to their contract quack Dr. Ramalamadingdong with a certificate from Bangladesh. I paid for it out of my own pocket.
Fuck the US health care system and fuck anyone who will defend any part of it.
Yes the entire purpose of Ingress was to make meat modules walk to under-documented locations, take pictures, and indicate points of interest. The meat modules seemed to think it was "fun". Hard to explain.
I don’t get how this is supposed to work with sports and other activities. In high school I had water polo/swimming practice mornings at 6:15. Is that now illegal?
More people should try high performance services with non-traditional protobuf implementations. The fact that every language has a generated parser in no way preclude you from parsing them yourself. Hand-rolled serialization of your outbound messages can also be really fast, and the C++ gRPC stack will just accept preformatted messages and put them on the wire. Finally the existence of gRPC itself should not make you feel constrained against implementing the entire protocol yourself. It’s just HTTP/2 with conventional headers.
Which part do you doubt: the assistant or the wifi? I never use the assistant stuff but the wifi is great.
Gsuite accounts never work right with every product google launches, often get features late or never. Many google products have _never_ become available for gsuite accounts.
Meetup doesn’t “run” these. You’re just picking boring ones. The only meetup I attend is a bunch of random motorcyclists who go up the coast highway every week. Never felt bored.
The result is pretty impressive. Go's scheduler is not this good. When my Go GRPC servers get up near 100,000 RPS their profiles are totally dominated by `runqsteal` and `findrunnable`.
Inside Google's main repo there are different build targets for libraries with incompatible API changes that are too difficult to fix all at once, e.g. there might be numpy_1_8 and numpy_1_10 separately.
Python at Google muddled along for years without numpy at all so it's not like anyone would be seriously harmed by having an old release in the repo.
All of the supposed flaws of a monorepo in this article are actually flaws of git. This is a very common phenomenon. I often joke there are two kinds of developers: those who prefer monorepos and those who have never used perforce.
It’s not because of the lawsuit. Their grid really is dangerously under-maintained and prone to bursting into flames. Turning it off is the rational short-term move.
Latency caused by packet loss. TCP needs microsecond timestamps and the ability to tune RTOmin down to 1ms before it is suitable for use in a datacenter. With the mainline kernel TCP stack you are looking at, at a minimum, a 20ms penalty whenever a packet is dropped.
Isn't it a pretty good reason? gRPC is terrible in a datacenter context without Google's internal TCP fixes that Linux won't adopt (and which have been advocated for in numerous conference papers since at least 2009). If they are steadfast cavemen what other workaround exists?
Fuck the US health care system and fuck anyone who will defend any part of it.