Fiadliel

6 ms·

1.
by Fiadliel 10mo ago
If one actually looks at the current pingora API, it has limited ability to initialize async components at startup - the current pattern seems to be to lazily initialize on first call. An obvious downside of this is that a service can start
2.
by Fiadliel 6y ago
Concerning Denmark, I agree that using the decentralized model is highly likely at this stage. Criticism of the centralized model from both Left and Right political parties, so the government would get nothing but flak if they didn't c
3.
by Fiadliel 6y ago
It is a trial, with 50% given "chloroquine" (according to the article). The Danish Medicines Agency has a list of current and upcoming drug studies here: https://laegemiddelstyrelsen.dk/da/nyheder/temaer&
4.
by Fiadliel 7y ago
Actually, the thing we started using nix for was reliable caching of compiled artifacts, including not just your code, but all the programs and libraries that your code depends on. It's another thing that's difficult to do in a ge
5.
by Fiadliel 7y ago
I know it's less of an issue for go users, but one of the great things about nix is how your runtime dependencies are (mostly) defined by inference from the programs you've built. So, if you build a program that links against libp
6.
by Fiadliel 7y ago
Yup! I assume that at this point general counsel is involved in everything Google says publicly; it's then worth nitpicking at the exact details of what has or has not been admitted, because legal folk definitely have!
7.
by Fiadliel 7y ago
That is not what the note said. It said that screenshots made their way outside the company. I would associate that with an email account that wasn't the work account, a printed page that was taken off-premises, a non-work cloud-hosted
8.
by Fiadliel 7y ago
Agreed that there's not enough context to say why screencapping happened, what happened to said screencaps, and how all of this turned into scared employees. I currently perceive Google's note as if it were a press release; treat
9.
by Fiadliel 7y ago
HN link for that article: https://news.ycombinator.com/item?id=21636583
10.
by Fiadliel 7y ago
Google's statement does not claim that the screenshots were shared with others. "Outside the company" covers a multitude of possibilities. It could also include saving screenshots in one's personal GMail account (in Goog
11.
by Fiadliel 7y ago
I do appreciate that some people felt unsafe, but I wonder how exactly the messaging was made. Nobody ever came to me and asked how I felt about my work calendar being shared. You can't even get that information from Google. So this in
12.
by Fiadliel 7y ago
I meant, there is no way for subscribers to a calendar to do that automatically. There are possible heuristics that could filter out clearly personal entries (keywords, etc.), but that feature would need to be implemented by (cough) Google.
13.
by Fiadliel 7y ago
They obviously subscribed to work calendars in order to follow the work activities of those people. There is no other technical way to do that. There isn’t a way to separate out personal events — which shouldn’t be there, or at least should
14.
by Fiadliel 7y ago
Google’s statement is, in my opinion, disingenuous. Including personal information on your work calendar without using privacy controls is pretty bad practice, though obviously some people occasionally did it. There is no indication that th
15.
by Fiadliel 7y ago
Okay, I see what you mean. It is a statistic, and so far as it is what it is describes, it's true. And it has some use. The problem is that what people are usually asking for, is the 99th percentile of response time for user requests,
16.
by Fiadliel 7y ago
How about this: you have a load balancer that sends much less traffic to servers that are running slowly (but still a small amount of traffic, so that it recognises when the machine recovers). One backend server has a hardware problem; requ
17.
by Fiadliel 8y ago
The general aim of error handling in languages like Elm is for types to not lie. If you can either return a result, or an error, the type represents that. The more places that can return an error: the more complex the types, and the more co
18.
by Fiadliel 10y ago
There are three things that help: 1. the large number of values that you now know definitely have a value, and you can access without fear that they don't. 2. the helper functions for Maybe that let you deal with optionality in various
19.
by Fiadliel 11y ago
We plan to release the software in early June, but the article was published in advance of the release. I've put a public repository at the location to make this clear, we'll update it soon.
20.
by Fiadliel 13y ago
The string concatenation API for Java IS terrible, but see modersky's post for the reasoning. Just don't mistake a bad API for some kind of belief that Scala in general idly converts between types. The weakest point is APIs that u