Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
raggi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
24 ms
·
361.
▲
by
raggi
3y ago
the call to system is obfuscated, static analysis wouldn't see it
362.
▲
by
raggi
3y ago
Except had we been doing that they would have put guards in place to detect it - as they already had guards to avoid the code path when a debugger is attached, to avoid building the payload in when it's not one of the target systems, a
363.
▲
by
raggi
3y ago
I ran pack that way, and observed the error I posted
364.
▲
by
raggi
3y ago
it’s not safe to disable SQLite’s thread safety as you do here: https://github.com/PackOrganization/Pack/blob/main/Libraries... and then do your own locking. You attempt to pass the flag at open time to
365.
▲
by
raggi
3y ago
Windows 11 sandbox, running atop Windows 11. Binary downloaded from your webpage. Data being packed was an unzipped copy of linux-master.zip fetched from GitHub unpacked with windows zip, selecting skip for the overlapping case files.
366.
▲
by
raggi
3y ago
That was the binary download from the website. You have a build.sh for the Linux binary artifacts, but no equivalent for the windows artifacts so i did not bother preparing a windows build
367.
▲
by
raggi
3y ago
I went to do some testing in a sandbox system (as the compilation strategy is unclear, missing builds for some of the artifacts). I was able to initially construct an archive of the linux tree (that failed in decompression), but subsequentl
368.
▲
by
raggi
3y ago
Not when threading is disabled, as it is in this project.
369.
▲
by
raggi
3y ago
Often new things are met with an excess of skepticism but I agree here. I'd take this more seriously if the format was documented at all, but so far it appears to be "this implementation relies on sqlite and zstd therefore it'
370.
▲
by
raggi
3y ago
We do a very similar thing in Tailscale, it was necessary to stay within the old iPhone memory budget.
371.
▲
by
raggi
3y ago
I would love to see this and excalidraw converge feature & spec wise.
372.
▲
by
raggi
3y ago
What I really want: dictionaries derived from the standards and standard libraries (perhaps once a year or somesuch), which I'd use independently of build system gunk, and while it wouldn't be the tightest squeeze you can get, it
373.
▲
by
raggi
3y ago
multiple layers of gatekeeping, both corporate and individual. It’s understated in the article but present: hard battle to get access to configuration. After that experience there’s uncertainty if the battle to change the default is worth t
374.
▲
by
raggi
3y ago
Despite being asynchronous it contains a single linear schedule and two callbacks. The obvious outcome is two layered constructors, and a single top level API object with two custom events. You couldn't describe what was going on in an
375.
▲
by
raggi
3y ago
go all in on webgpu compute
376.
▲
by
raggi
3y ago
It widowed my sister. Grow up.
377.
▲
by
raggi
3y ago
The position of “I regularly don’t know if I have a string or a uri” is indeed a commonly raised issue. It folds out to two other problems: It implies a lack of conventions around interfaces and variable names. The surrounding statement als
378.
▲
by
raggi
3y ago
Invest in webgpu compute. It's not just for web, but it is portable.
379.
▲
by
raggi
3y ago
in a lot of these systems I interact with they're limited by packet rate more than packet size. I'm not disputing latency sensitivity in the application, I'm surprised that frame size in the normal range has measured to intro
380.
▲
by
raggi
3y ago
Very interesting, I bet this had come up before but remained undiagnosed, yay for packet captures
381.
▲
by
raggi
3y ago
I’m just a little surprised as economies of scale have pushed support for larger frames into most of the hardware you can purchase. I can absolutely believe somebody saying this, but intuition is telling me that it’s a misdiagnosed problem
382.
▲
by
raggi
3y ago
that concern with these numbers is very surprising, do you know if there’s somewhere with writing about this?
383.
▲
by
raggi
3y ago
The picture in the case of losses is pretty complicated with dack, sack, congestion control, and so on. If loss is high enough that this is a main concern TCP performance is generally shot already.
384.
▲
by
raggi
3y ago
the messy challenge here is that the trade-offs shifted, but persist contrarian arguments. packets are too small to be efficient without doing excessively tight loop optimizations, which is what makes fragmentation "slow" (it'
385.
▲
by
raggi
3y ago
Haha, I like broadside. I had to lookup egg of columbus, TIL
386.
▲
by
raggi
3y ago
The problem is intractable unless you enforce lossless perfect ordering as a strict requirement. There's no way to define "first" as written in the premise without it.
387.
▲
by
raggi
3y ago
If I was revisiting, I'd probably eradicate the layer and pick a fixed number of flow types with distinct headers and state machines. The layers were a reasonable choice given the understanding of the time, but in hindsight I think you
388.
▲
by
raggi
3y ago
"no molecules are possible" does not imply "absolutely nothing forms a structured dynamic", the thought experiment ceases prematurely if it stops there, partly because the structural makeup is not yet well enough known t
389.
▲
by
raggi
3y ago
It might not ever work "like walking", but nor does a linear array of a bunch of miniature speakers in a pair of headphones work like spatial audio in the real world, but the brain figures this out fairly quickly. The question her
390.
▲
by
raggi
3y ago
GNU binutils and LLVM both have support for debuginfod server topologies now, it would be great to see Rust tools get on the train. https://github.com/llvm/llvm-project/commit/36f01909a0e29c10... And naturall
More ›