frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Aging and Eye Problems

https://ldstephens.net/posts/aging-and-eye-problems/
1•speckx•10s ago•0 comments

Building the Tampermonkey Replacement

https://www.youtube.com/watch?v=bvv3bYf-6ik
1•jobello•1m ago•1 comments

Reverse Engineering Crazy Taxi, Part 3

https://wretched.computer/post/crazytaxi3
2•wgreenberg•2m ago•0 comments

MS Sharepoint sunset of "Alert me" (on folder changes) completes next month

https://techcommunity.microsoft.com/blog/spblog/sharepoint-alerts-retirement/4410402
1•realityfactchex•2m ago•1 comments

Official Invitation to the Beta Test: "Knowledge in a Box"

https://sozialsoziokrat.substack.com/p/official-invitation-to-the-beta-test
1•Daniel_Bauer•5m ago•0 comments

Data Viz and Table Design from the Letterpress Era

https://chris-parmer.com/data-viz-from-the-letterpress-era/
1•robertclaus•8m ago•0 comments

Reviewing Code Requires Reading

https://hauleth.dev/post/review-requires-reading/
2•birdculture•9m ago•0 comments

Miasma Worm Targets AI Coding Agents via GitHub Repos

https://safedep.io/miasma-worm-ai-coding-agent-config-injection/
2•ngetchell•9m ago•0 comments

Harness engineering: Leveraging Codex in an agent-first world

https://openai.com/index/harness-engineering/
1•pramodbiligiri•10m ago•0 comments

Show HN: Relic, a tiny coding agent for ancient and constrained systems

https://github.com/felixrieseberg/relic
1•felixrieseberg•10m ago•0 comments

Microsoft and OpenAI broke up – now they're ready to fight

https://www.theverge.com/ai-artificial-intelligence/942242/microsoft-build-ai-agents-openai-compe...
1•speckx•10m ago•0 comments

Agentic Search Models with OpenSearch and Elasticsearch

https://bonsai.io/blog/agent-search-with-sid/
8•h3h•13m ago•0 comments

Meta weighs big equity raising after blockbuster Google deal

https://www.ft.com/content/e6df645d-1709-4a77-b15d-aa43a0209efd
2•mfiguiere•13m ago•0 comments

Crowdsource agents for reasoning, reward top. A live Experiment

https://rezontree.com
1•BuddhaSource•14m ago•1 comments

Mythos found the bugs. Who funds the fixes?

https://opub.dev/blog/mythos-found-the-bugs-who-funds-the-fixes
1•goodroot•14m ago•1 comments

SupXML: The modern, memory-safe XML parser drop-in replacement for libxml2

https://supso.org/blog/introducing-supxml-modern-memory-safe-xml-parser-alternative-to-libxml2
1•jrpt•14m ago•0 comments

74k words and CPUs playing ZOEAE: How I built a dictionary for word game pedants

https://wordtrak.com/blog/2026-06-05-how-i-built-a-new-dictionary-for-pedantic-word-game-players
2•qrush•15m ago•0 comments

Crowdsource agents for reasoning, reward top. A live Experiment

https://reazontree.com
1•BuddhaSource•15m ago•2 comments

Call for Testing: PhoenixDKIM, A security-focused DKIM milter

https://www.phoenixdkim.org/
1•peregrinus_13•16m ago•1 comments

The reason dating is broken: Data behind romance went from joyful to miserable

https://www.youtube.com/watch?v=HGBuEjzsrHE
1•maxloh•18m ago•0 comments

Azure Functions Core Tools repository taken down

https://github.com/Azure/azure-functions-core-tools
1•hectorm•20m ago•1 comments

The Reflection on My First Year at Meta (Facebook)

https://johnjr.dev/posts/the-reflection-on-my-first-year-at-meta/
2•johnjr•21m ago•0 comments

Show HN: Interact with your .eml files using MCP tools

https://github.com/MiguelRipoll23/eml-mcp
1•PhilDunphy23•22m ago•0 comments

Show HN: Audit any AI/data pairing with Veritrooper

https://veritrooper.com/
1•brian8620•22m ago•0 comments

Show HN: Fooglemap – a map for local restaurant discovery

https://fooglemap.com/
1•rankiwiki•24m ago•0 comments

Meta putting up tents across the US to house AI servers

https://www.tomshardware.com/tech-industry/artificial-intelligence/meta-putting-up-tents-across-t...
3•jeffufl•24m ago•2 comments

Bend under pressure not under nonsense

https://julienreszka.com/blog/bend-under-pressure-not-under-nonsense/
1•julienreszka•26m ago•0 comments

Chrome Breaks Records Again on Speedometer 3.1 and Jetstream 3

https://blog.google/chromium/a-double-victory-for-web-speed-chrome-breaks-records-again-on-speedo...
1•ksec•27m ago•0 comments

The web. Without permission. Grub is back, with a vengeance

https://deepbluedynamics.com/grub
2•kordlessagain•28m ago•0 comments

TanStack AI

https://tanstack.com/blog/your-mcp-your-way
2•berlianta•29m ago•0 comments
Open in hackernews

Packed Data Support in Haskell

https://arthi-chaud.github.io/posts/packed/
77•matt_d•1y ago

Comments

nine_k•1y ago
> Introducing the ‘packed’ data format, a binary format that allows using data as it is, without the need for a deserialisation step. A notable perk of this format is that traversals on packed trees is proven to be faster than on ‘unpacked’ trees: as the fields of data structures are inlines, there are no pointer jumps, thus making the most of the L1 cache.

That is, a "memory dump -> zero-copy memory read" of a subgraph of Haskell objects, allowing to pass such trees / subgraphs directly over a network. Slightly reminiscent of Cap'n Proto.

90s_dev•1y ago
We are always reinventing wheels. If we didn't, they'd all still be made of wood.
Zolomon•1y ago
They mention this in the article.
spockz•1y ago
It reminds me more of flat buffers though. Does protobuf also have zero allocation (beyond initial ingestion) and no pointer jumps?
cstrahan•1y ago
No, one example of why being variable sized integers.

See https://protobuf.dev/programming-guides/encoding/

carterschonwald•1y ago
One thing that sometimes gets tricky in these things is handling Sub term sharing. I wonder how they implemented it.
tlb•1y ago
> the serialised version of the data is usually bigger than its in-memory representation

I don’t think this is common. Perhaps for arrays of floats serialized as JSON or something. But I can’t think of a case where binary serialization is bigger. Data types like maps are necessarily larger in memory to support fast lookup and mutability.

nine_k•1y ago
I suppose all self-describing formats, like protobuf, or thrift or, well, JSON are bigger than the efficient machine representation, because they carry the schema in every message, one way or another.
IsTom•1y ago
If you use a lot of sharing in immutable data it can grow a lot when serializing. A simple pathological example would be a tree that has all left subtrees same as the right ones. It takes O(height) space in memory, but O(2^height) when serialized.
gitroom•1y ago
honestly i wish more stuff worked this way - fewer hops in memory always makes me happy
lordleft•1y ago
This was very well written. Excellent article!
NetOpWibby•1y ago
Is this like MessagePack for Haskell?