Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
euank
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
euank
1y ago
I can give an n=1 anecdote here: the dns resolver used to have hard-coded caching which meant that it would be unresponsive to pod updates, and cause mini 30s outages. The code in question was: https://github.com/grpc/g
2.
▲
by
euank
4y ago
Coincidentally, Google has sorta done that too! ChromiumOS/ChromeOS is built using portage, and is certainly rolling release. It's not really a traditional linux distro, but it's something.
3.
▲
by
euank
4y ago
> Does anyone know if and where I could file a bug report? The linux kernel does take bug reports: https://docs.kernel.org/admin-guide/reporting-issues.html However, that bug probably isn't specific enough as y
4.
▲
by
euank
5y ago
> Email has never had explicit threading The "In-Reply-To" header is described in rfc2822. It is an explicit header in the RFC that is how you create threads. Every mail client I've used correctly understands how to thread
5.
▲
by
euank
6y ago
The kubelet can talk to containerd's cri endpoint, yes, but there's one additional bit of complexity. If someone wants to use kubelet + docker so that they can, for example, ssh into a node and type 'docker ps' to see co
6.
▲
by
euank
6y ago
For what it's worth, there are a few cases where docker vs some other runtime does make a difference. One difference is that if you 'docker build' or 'docker load' an image on a node, with docker as a runtime a pod
7.
▲
by
euank
6y ago
containerd can serve CRI requests itself. This has been the case since the containerd v1.1.0 release[0], which included the cri "plugin" as an in-process part of the containerd binary. For a while, to keep up the plugin idea, it w
8.
▲
by
euank
6y ago
I think that the title of this is a bit misleading. Kubernetes is removing the "dockershim", which is special in-process support the kubelet has for docker. However, the kubelet still has the CRI (container runtime interface) to s
9.
▲
by
euank
6y ago
> is there a name for this bias? I think it's response bias. https://en.wikipedia.org/wiki/Response_bias
10.
▲
by
euank
6y ago
You're right that nixos / all nix packages isn't/aren't perfectly reproducible. In practice, most of the packages in the nixos base system seem to be reproducible, as tested here: https://r13y.com/
11.
▲
by
euank
6y ago
A Dockerfile is not a reproducible set of build instructions in most cases. I'd guess that the vast majority of Dockerfiles are not reproducible. Let's look at an example dockerfile for redis (based on [0]) FROM debian:buste
12.
▲
by
euank
6y ago
This proposal is more powerful than that one rust macro, but rust's abilities around embedding files are much more powerful than go's approach. This proposal allows "go build" to embed things in a very specific way, but
13.
▲
by
euank
7y ago
Go's channels aren't exposed outside a specific go process's runtime. The runtime doesn't give you any convenient way to redirect them. They're not like erlang's mailboxes at all in that regard. Furthermore, ch
14.
▲
by
euank
7y ago
One of the weird peculiarities of path-style API requests was that it meant CORS headers meant nothing for any bucket pretty much. I wrote a post about this a bit ago [0]. I guess after this change, the cors configuration will finally do so
15.
▲
by
euank
8y ago
It does not currently (only linux and macOS), but porting it over should be really easy! The cross platform story for rust isn't as seamless as an interpreted language like lua, but it's still good enough that it's not a huge
16.
▲
by
euank
8y ago
Fair question! I didn't know a rust rewrite of autojump existed! I already benchmark pazi against autojump by itself, so adding in a benchmark against autojump-rs will basically be drop-in, and I do expect pazi will still be faster, bu
17.
▲
by
euank
8y ago
This looks nice! I'm especially interested in the claims of performance. I've also written an autojumper[0] (in rust) after being frustrated by performance issues in other autojumpers, among other reasons. For mine, I've gone
18.
▲
by
euank
8y ago
I can recommend pazi as a convenient tool for zapping around https://github.com/euank/pazi The readme also lists several alternatives in the same space as pazi.
19.
▲
by
euank
8y ago
I've found fasd ( https://github.com/clvv/fasd ) to be the most featureful of the directory jumping tools, and it's much faster than autojump as well. I'd be remiss not to mention pazi however, which is t
20.
▲
by
euank
12y ago
This is an anomaly that your explanation doesn't apply to though. Notice that it has 50 points and is half an hour old. I count 12 items on the front page currently that have 50 or fewer points and are 1 or more hours old and yet remai
21.
▲
by
euank
12y ago
This is an interesting oddity such as you might expect to see on reddit's /r/mildlyinteresting or til, but I don't feel that this fits well on HN personally. I'm not saying HN is turning into reddit by having this c
22.
▲
by
euank
12y ago
They don't mention Amazon specifically except in the title and the final sentence. I recall, when I signed up for my free year of AWS, that it required a valid credit card. They claimed to only target providers that need essentially on
23.
▲
by
euank
12y ago
"show on the right" required a restart after being checked to work for me in linux. Perhaps that helps?
24.
▲
by
euank
12y ago
It was the parent I responded to who said all software should strive for this. My argument is not against the philosophy of the window manager in this instance, but rather against applying it everywhere as the parent seemed to think would b
25.
▲
by
euank
12y ago
The fraction of terrorists in "all people that use the internet" is approximately equal to the fraction of terrorists in "privacy seekers" -- both are roughly zero. The NSA only was given such pervasive power to catch te
26.
▲
by
euank
12y ago
I do not like the "API should be completely transparent" and "API must not be bloated". I personally think APIs exist to hide complexity. They should make sense, they should be usable, but they need not be transparent. L
27.
▲
by
euank
12y ago
Jshint still complains about it even though it's technically okay.
28.
▲
by
euank
12y ago
Promises show a good use case. It's common to have many promise-laden bits of code and it's clear that the first callback is success, second, error, and third progress. Having to do "def promise1_success" ... "def p
29.
▲
by
euank
12y ago
Why no mention of FirefoxOS? The Mozilla foundation has our best interests at heart much more than Google and while it's not C++, html5/javascript is certainly an open enough platform which basically everything has started to targ
30.
▲
by
euank
12y ago
I'm hoping it means the installation is non-destructive and it uses your existing configs, with no changes, as a base and then modifies them from there when you use the webui. If that's true, it's poorly phrased.
More ›