haeseong

5 ms·

1.
19th Nervous Breakdown(thebuild.com)
1 points by haeseong 10d ago|0 comments
2.
GDScript: The Good, Bad, and Ugly Parts(azhdarchid.com)
3 points by haeseong 12d ago|1 comments
3.
Conversations with JJ(laurmaedje.github.io)
1 points by haeseong 16d ago|0 comments
4.
SystemIO conflicts are not firmware bugs(codon.org.uk)
38 points by haeseong 17d ago|6 comments
5.
Prehistoric builders hauled 25-tonne stones at least 18 km to Devil's Arrows(phys.org)
2 points by haeseong 18d ago|0 comments
6.
Bitap: My favorite string matching algorithm(jo3-l.dev)
30 points by haeseong 19d ago|14 comments
7.
Writing a Fast Compiler (2024)(tibleiz.net)
2 points by haeseong 1mo ago|0 comments
8.
by haeseong 2mo ago
I didn't expect the 2,000 connection sweep to stay flat, since all of them are sharing one stream. What does per user latency look like at that end of the sweep?
9.
by haeseong 2mo ago
What does the 50% look like when it fails? Garbage the parser throws out is easy to handle, but a well formed command aimed at the wrong host gets past the scope check, and you would only catch that reading the report afterward.
10.
CVE-2026-49176 Exploit Development: WalletService to System(davidcarliez.github.io)
2 points by haeseong 2mo ago|0 comments
11.
Systems and Delays(martin.janiczek.cz)
3 points by haeseong 2mo ago|0 comments
12.
A Tour of MLIR: The Dialect Stack Everyone Depends On(hiraditya.github.io)
2 points by haeseong 2mo ago|0 comments
13.
The LSM Tree(ledger.khushal.net)
1 points by haeseong 2mo ago|0 comments
14.
Log is non-monotonous in PHP and Lua(purplesyringa.moe)
2 points by haeseong 2mo ago|0 comments
15.
by haeseong 2mo ago
A `bool profile` branch stays expensive even when it predicts perfectly, because it bloats every opcode handler, and on a computed goto interpreter that extra code messes with the branch predictor history each dispatch site builds up, which
16.
The lock around WAL flush(frn.sh)
2 points by haeseong 2mo ago|0 comments
17.
by haeseong 3mo ago
The byte by byte view makes the failure mode people run into easier to explain. VACUUM can never remove a tuple whose xmax is newer than the oldest snapshot still open, so one forgotten idle transaction or an abandoned replication slot pins
18.
How a Computer Should Work(pkgdemon.github.io)
2 points by haeseong 3mo ago|0 comments
19.
What can wonky APIs tell us about the web?(alexwlchan.net)
2 points by haeseong 3mo ago|0 comments
20.
Apple Internals: Swift in the Kernel(blog.calif.io)
5 points by haeseong 3mo ago|0 comments
21.
by haeseong 3mo ago
The query speed deserves the praise, but the JSON ingestion path has quiet footguns nobody mentions here. Every numeric column comes back as a string over JSONEachRow, so a forgotten Number() cast silently turns arithmetic into string conca
22.
The Design of Littlefs(github.com)
2 points by haeseong 3mo ago|0 comments
23.
Show your hands honor for the power they bring you(aresluna.org)
8 points by haeseong 3mo ago|0 comments
24.
by haeseong 3mo ago
The operational wrinkle nobody mentions in the rename is that the same vulnerability now ships under two version trains. VSV00019 was just patched as Vinyl 9.0.1 and as Varnish 8.0.2 and 6.0.18, so anyone pinning a version in their package
25.
by haeseong 3mo ago
QUERY has existed in spirit for nearly two decades as WebDAV's SEARCH method https://www.rfc-editor.org/rfc/rfc5323 and the thing that always killed it in practice was intermediaries. Plenty of proxies, WAFs, and
26.
Cockroaches scurry around with pieces of bacterial genomes(arstechnica.com)
3 points by haeseong 3mo ago|0 comments
27.
by haeseong 3mo ago
The free Python 2 versus paid Python 3 split you ran into wasn't arbitrary pricing. Trinket ran Python 2 entirely in the browser through Skulpt https://skulpt.org , a JS reimplementation that costs nothing to serve, while Py
28.
by haeseong 3mo ago
That split is exactly what .NET 6 did. The parameterless Random switched to xoshiro256*, but new Random(seed) stays pinned to the old Numerical Recipes subtractive generator so historical seeds still reproduce, and that legacy generator is
29.
by haeseong 3mo ago
The pointer size difference is the symptom, not the disease. Storing a raw pointer in a pak file was never valid even on native since the address changes every load, so the real fix is exactly what the author landed on, store an index into
30.
The mystery of the Solar Realms Elite title screen(breakintochat.com)
3 points by haeseong 3mo ago|0 comments

More ›