Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
haeseong
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
GDScript: The Good, Bad, and Ugly Parts
(azhdarchid.com)
2 points
by
haeseong
1d ago
|
0 comments
2.
▲
Conversations with JJ
(laurmaedje.github.io)
1 points
by
haeseong
5d ago
|
0 comments
3.
▲
SystemIO conflicts are not firmware bugs
(codon.org.uk)
38 points
by
haeseong
6d ago
|
6 comments
4.
▲
Prehistoric builders hauled 25-tonne stones at least 18 km to Devil's Arrows
(phys.org)
2 points
by
haeseong
7d ago
|
0 comments
5.
▲
Bitap: My favorite string matching algorithm
(jo3-l.dev)
30 points
by
haeseong
8d ago
|
14 comments
6.
▲
Writing a Fast Compiler (2024)
(tibleiz.net)
2 points
by
haeseong
1mo ago
|
0 comments
7.
▲
by
haeseong
1mo 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?
8.
▲
by
haeseong
1mo 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.
9.
▲
CVE-2026-49176 Exploit Development: WalletService to System
(davidcarliez.github.io)
2 points
by
haeseong
2mo ago
|
0 comments
10.
▲
Systems and Delays
(martin.janiczek.cz)
3 points
by
haeseong
2mo ago
|
0 comments
11.
▲
A Tour of MLIR: The Dialect Stack Everyone Depends On
(hiraditya.github.io)
2 points
by
haeseong
2mo ago
|
0 comments
12.
▲
The LSM Tree
(ledger.khushal.net)
1 points
by
haeseong
2mo ago
|
0 comments
13.
▲
Log is non-monotonous in PHP and Lua
(purplesyringa.moe)
2 points
by
haeseong
2mo ago
|
0 comments
14.
▲
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
15.
▲
The lock around WAL flush
(frn.sh)
2 points
by
haeseong
2mo ago
|
0 comments
16.
▲
by
haeseong
2mo 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
17.
▲
How a Computer Should Work
(pkgdemon.github.io)
2 points
by
haeseong
3mo ago
|
0 comments
18.
▲
What can wonky APIs tell us about the web?
(alexwlchan.net)
2 points
by
haeseong
3mo ago
|
0 comments
19.
▲
Apple Internals: Swift in the Kernel
(blog.calif.io)
5 points
by
haeseong
3mo ago
|
0 comments
20.
▲
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
21.
▲
The Design of Littlefs
(github.com)
2 points
by
haeseong
3mo ago
|
0 comments
22.
▲
Show your hands honor for the power they bring you
(aresluna.org)
8 points
by
haeseong
3mo ago
|
0 comments
23.
▲
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
24.
▲
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
25.
▲
Cockroaches scurry around with pieces of bacterial genomes
(arstechnica.com)
3 points
by
haeseong
3mo ago
|
0 comments
26.
▲
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
27.
▲
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
28.
▲
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
29.
▲
The mystery of the Solar Realms Elite title screen
(breakintochat.com)
3 points
by
haeseong
3mo ago
|
0 comments
30.
▲
Clojure is almost as fast as C (with some help)
(ertu.dev)
8 points
by
haeseong
3mo ago
|
0 comments
More ›