Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kiitos
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
181.
▲
by
kiitos
1y ago
> Write down your top-level dependencies. The computer will figure out transitive ones. They are guaranteed to be the same, since everything is immutable. dep@ver can resolve to totally different outputs, depending on resolver (repositor
182.
▲
by
kiitos
1y ago
i am getting the sense that you have missed the point
183.
▲
by
kiitos
1y ago
oh good a purity test for OSS projects, this is exactly what's needed in the ecosystem, and will surely have a positive impact
184.
▲
by
kiitos
1y ago
it's pretty interesting to see this discrepancy in response to this idea some folks -- i guess like you? -- read this and think, "oh, great. a mandate that fixes a problem i don't have, and now might be something i'm for
185.
▲
by
kiitos
1y ago
Nothing in this post suggests any kind of expectation, mandate, or obligation to post anything in any kind of channel. The problem that this post is trying to address, is that these kinds of informal rambling channels -- which have enormous
186.
▲
by
kiitos
1y ago
> if an interface has enough consumers, they will collectively depend on every aspect of the implementation ... Yep! > [and that] constrains changes to the implementation, which must now conform to both the explicitly documented inter
187.
▲
by
kiitos
1y ago
we also have an option for node discovery that uses pkarr.org, which is using the bittorrent mainline DHT and therefore is fully decentralised if users access that bittorrent mainline DHT thru a third party server then it's o
188.
▲
by
kiitos
1y ago
a URL is also a single string that's easy to copy and paste, the question I have is how these strings get resolved to something that I can connect to if you need to go thru a relay to do resolution, and relays are specified in terms of
189.
▲
by
kiitos
1y ago
ngrok and tailscale and lots of other services offer all of these capabilities, the only unique thing of this one seems to be the opaque string identifiers + some notion of "decentralization" which is what I'm trying to under
190.
▲
by
kiitos
1y ago
the use case here is somebody opens a web browser and types/pastes an ID into the top bar -- and it needs to resolve, correctly, without prior knowledge, in roughly the same amount of time that DNS takes today relays are the only thing
191.
▲
by
kiitos
1y ago
tl;dr: resolving ids to destinations requires a third party relay
192.
▲
by
kiitos
1y ago
OK so given $ ./dumbpipe listen ... To connect use: ./dumbpipe connect nodeecsxraxj... that `nodeecsxraxj...` is a serialized form of some data type that includes the IP address(es) that the client needs to connec
193.
▲
by
kiitos
1y ago
> In the iroh world, you dial another node by its NodeId, a 32-byte ed25519 public key. Unlike IP addresses, this ID is globally unique, and instead of being assigned, ok but my network stack doesn't speak nodeID, it speaks tcp/
194.
▲
by
kiitos
1y ago
tailscale is a wrapper around wireguard in the same way that dropbox is a wrapper around rsync
195.
▲
by
kiitos
1y ago
In the OP screen share, they toggle various telemetry options on and off, but every time a setting changes, there is a pop-up that says "a setting has changed that requires a restart [of the editor] to take effect" -- and the user
196.
▲
by
kiitos
1y ago
this discussion should be ample evidence that it very clearly does not
197.
▲
by
kiitos
1y ago
> Memory safety is not a spectrum. You are either memory safe or unsafe. if there is one takeaway from this discussion, i think it must be that memory safety does not have any single, commonly-accepted, or objective definition -- and tha
198.
▲
by
kiitos
1y ago
I suppose Go's notion of memory safety is satisfied by forbidding pointer arithmetic, and, maybe somewhat transitively, preventing arbitrary out-of-bounds access to memory. It definitely satisfies this notion of memory safety. Maybe th
199.
▲
by
kiitos
1y ago
For the purposes of this discussion, sure: https://go.dev/ref/mem Relevant bit for the OP is probably: A data race is defined as a write to a memory location happening concurrently with another read or write to t
200.
▲
by
kiitos
1y ago
You don't need logs for that, you can get it from metrics just fine. Via absolute value counters, or some kind of percentage-complete gauge, either way you can easily see progress over time...
201.
▲
by
kiitos
1y ago
This package spawns a goroutine that updates an atomic value every second based on a time.Time from a time.Ticker, and its functions load that atomic value. This is not really comparable to anything in package time in any useful way...
202.
▲
by
kiitos
1y ago
> To see what I mean by this, consider this program written in Go, which according to Wikipedia is memory-safe: The Wikipedia definition of memory safety is not the Go definition of memory safety, and in Go programs it is the Go definiti
203.
▲
by
kiitos
1y ago
It's not a question of number of machines, it's a question of how much load any individual program can serve. Requests per second, per process. If that's O(1k) or less, then sure, do whatever you want, it's trivial load.
204.
▲
by
kiitos
1y ago
Instead of making users enable every formatting rule explicitly e.g. jqfmt -ob -ar -op pipe It would be better if the tool enabled a common set of rules by default, so that `echo ... | jqfmt` actually did something useful :)
205.
▲
by
kiitos
1y ago
The "compressed form" of logs you're describing here is really just metrics...
206.
▲
by
kiitos
1y ago
log all major logical branches within code (if/for) This certainly does not work for any non-trivial amount of load...
207.
▲
by
kiitos
1y ago
Please, please tell me how I can hold an LLM correctly. My requirements are: it doesn't tell me anything that it's hallucinated, or which is factually incorrect. That's it. That's the only requirement.
208.
▲
by
kiitos
1y ago
In addition to the prior comments re: how the example JSON parse failures are actually correct... Let me consider a broken JSON document: `{"key": "value\nda"}` So using xxd on that input we get 00000000:
209.
▲
by
kiitos
1y ago
You're describing scripts, which require interpreters like I guess uv or Node or Python. A CLI tool is a native binary.
210.
▲
by
kiitos
1y ago
> Previously .. I didn't want to take the time to spin up on the trivia for a new language or platform ... Now? I'll happily use things like Go and Bash and AppleScript and jq and ffmpeg It's pretty wild that you're c
More ›