frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: HackerBooks – HackerTube, but for books mentioned on HN

https://hackerbooks.org
379•roansh•3h ago•111 comments

Mathematics has changed. Let's act like it

https://terrytao.wordpress.com/2026/11/01/mathematics-has-changed-lets-act-like-it/
25•smilelamp•36m ago•15 comments

HackerTube: YouTube built from videos recommended by HN

https://karpathy.bearblog.dev/hacker-tube/
1929•karpathy•23h ago•488 comments

Patrick Stewart taught us what good men do with power

https://www.vox.com/politics/508526/patrick-stewart-jean-luc-picard-star-trek-liberalism
139•rhaynes•1h ago•97 comments

Police chief unplugs Flock cameras after company ignores contract cancellation

https://www.tomshardware.com/tech-industry/big-tech/police-chief-physically-unplugs-flock-cameras...
301•entryleveljobsc•4h ago•98 comments

Copper – A minimal low-level programming language with OOP and generics

https://tibleiz.net/copper/
60•bogdanoff_2•1d ago•26 comments

Seoul Viosys begins production of rare-earth-free white light emitter

https://www.semiconductor-today.com/news_items/2026/oct/seoul-291026.shtml
86•gmays•2h ago•15 comments

Proving and improving the Platonic Representation Hypothesis with JEPAs

https://arxiv.org/abs/2610.39302
75•Anon84•5h ago•41 comments

Bidirectional charging during grid outages

https://www.jefftk.com/p/bidirectional-charging-during-grid-outages
45•luu•22h ago•62 comments

Lenovo's 'encrypted' fingerprint USB is just an unencrypted SD card in a case

https://www.reddit.com/r/technology/comments/1xl2pr3/lenovos_encrypted_fingerprint_usb_drive_is_j...
231•entryleveljobsc•4h ago•92 comments

An Italian farmer found some unknown seeds in his attic and planted them

https://www.smithsonianmag.com/science-nature/italian-farmer-found-unknown-seeds-attic-with-nothi...
679•ecares•20h ago•186 comments

Novellas with Groff

https://movq.de/blog/postings/2026-10-31/0/POSTING-en.html
72•dverlaeckt80•5h ago•25 comments

Frontier Airlines Likely Breached

https://www.reddit.com/r/frontierairlines/comments/1xl20e8/psa_email_scam/
90•999900000999•2h ago•21 comments

One-minute frequency disturbances from synchronization in power systems

https://www.nature.com/articles/s41560-026-02144-0
78•croes•1d ago•32 comments

Parchment Paper History: How We Got Paper Perfect for Baking (2019)

https://tedium.co/2019/11/21/nonstick-parchment-paper-history/
5•colinprince•1d ago•2 comments

Show HN: I rebuilt my old canvas 3D library as a small WebGL 2 library – phoria2

https://kevs3d.co.uk/phoria2/
47•kevs3d•1d ago•6 comments

The AI cost of JavaScript frameworks

https://nolanlawson.com/2026/10/28/the-ai-cost-of-javascript-frameworks/
230•luu•12h ago•159 comments

Brazilian Court Sanctions Lawyers for Prompt Injection in Court Filing

https://jetstream.security/insights/brazilian-court-sanctions-prompt-injection-filing/
267•doodlesdev•16h ago•149 comments

Memdoor: A team of 5 Qwen3.8-27B models beats Fable 5 on LiveCodeBench Hard

https://github.com/guregodevo/memdoor/tree/main/examples/workflows/team-solve
385•guregodevo•20h ago•189 comments

Show HN: OmniDiff – Opensource, super fast, content aware Git difftool, in Rust

https://github.com/ivankovic/omnidiff
50•FabCH•6h ago•24 comments

TCP Use-After-Free: CVE-2026-98432 / CVSS 9.8

https://atlasum.net/blog/cve-2026-98432-linux-ipv4-tcp-uaf
631•oger•23h ago•307 comments

Radiation Map of the World

https://radiaverse.com/
79•slater•3d ago•29 comments

Show HN: Point your camera at a landscape to learn about its geology

https://outcrop.rocks/
101•headsupernova•3d ago•28 comments

Landline phones will switch off across Britland in 100 days, no extensions

https://www.theregister.com/networks/2026/11/01/landline-phones-will-switch-off-across-britland-i...
57•edward•3h ago•33 comments

SS27 Color Stats

https://sarahconstantin.substack.com/p/ss27-color-stats
4•surprisetalk•3d ago•0 comments

Understanding Email Encryption

https://www.fastmail.com/blog/email-encryption/
98•nmjenkins•1d ago•21 comments

Running a bootstrapped SaaS for 20 years with my brother

https://blog.zamzar.com/2026/10/30/20-years-766-million-files-two-chameleons/
203•whyleyc•2d ago•46 comments

Leaking Secrets from Air-Gap Computers by Spelling Radio Signals from RAM (2024)

https://arxiv.org/abs/2409.02292
159•hapax_legomena•17h ago•82 comments

Enlightenment 0.28.0 Release

https://www.enlightenment.org/news/2026-10-31-enlightenment-0.28.0
45•birdculture•3h ago•15 comments

Domain hacks with unusual Unicode characters (2018)

https://xn--69f31l4t57c0mag4b613h.xn--7uh4898msjaso/🆆🆃🅵/
44•n_plus_1_acc•8h ago•38 comments
Open in hackernews

Falsify: Hypothesis-Inspired Shrinking for Haskell (2023)

https://www.well-typed.com/blog/2023/04/falsify/
90•birdculture•1y ago

Comments

sshine•1y ago
How does Hedgehog and Hypothesis differ in their shrinking strategies?

The article uses the words "integrated" vs. "internal" shrinking.

> the raison d’être of internal shrinking: it doesn’t matter that we cannot shrink the two generators independently, because we are not shrinking generators! Instead, we just shrink the samples that feed into those generators.

Besides that it seems like falsify has many of the same features like choice of ranges and distributions.

_jackdk_•1y ago
This is the key sentence:

> The key insight of the Hypothesis library is that instead of shrinking generated values, we instead shrink the samples produced by the PRNG.

Hedgehog loses shrink information when you do a monadic bind (Gen a -> (a -> Gen b) -> Gen b). Hypothesis parses values out of the stream of data generated by the PRNG, so when it "binds", you are still just consuming off that stream of random numbers, and you can shrink the stream to shrink the generated values.

Here is a talk that applies the Hypothesis idea to test C++: https://www.youtube.com/watch?v=C6joICx1XMY . Discussion of PBT implementation approaches begins at 6:30.

thesz•1y ago
This is fascinating!

If I understand correctly, they approximate language of inputs of a function to discover minimal (in some sense, like "shortest description length") inputs that violate relations between inputs and outputs of a function under scrutiny.

evertedsphere•1y ago

    newtype Parser a = Parser ([Word] -> (a, [Word])
missing a paren here
moomin•1y ago
I’m honestly completely failing to understand the basic idea here. What does this look like for generating and shrinking random strings,
chriswarbo•1y ago
One straightforward approach would be:

- Generate a random number N for the size (maybe restricted to some Range)

- Generate N `Char` values, by using a random number for each code point.

- Combine those Chars into a string

falsify runs a generator by applying it to an infinite binary tree, with random numbers in the nodes. A generator can either consume a single number (taken from the root node of a tree), or it can run two other generators (one gets run on the left child, the other gets run on the right). Hence the above generator would use the value in the left child as N, then run the "generate N Chars" generator on the right child. The latter generator would run a Char generator on its left child, and an 'N-1 Chars' generator on its right child; and so on.

To shrink, we just run the generator on a tree with smaller numbers. In this case, a smaller number in the left child will cause fewer Chars to be generated; and smaller numbers in the right tree will cause lower code-points to be generated. falsify's tree representation also has a special case for the smallest tree (which returns 0 for its root, and itself for each child).

mjw1007•1y ago
I've found in practice that shrinking to get the "smallest amount of detail" is often unhelpful.

Suppose I have a function which takes four string parameters, and I have a bug which means it crashes if the third is empty.

I'd rather see this in the failure report:

("ldiuhuh!skdfh", "nd#lkgjdflkgdfg", "", "dc9ofugdl ifugidlugfoidufog")

than this:

("", "", "", "")

gwern•1y ago
Really? Your examples seem the opposite. I am left immediately thinking, "hm, is it failing on a '!', some sort of shell issue? Or is it truncating the string on '#', maybe? Or wait, there's a space in the third one, that looks pretty dangerous, as well as noticeably longer so there could be a length issue..." As opposed to the shrunk version where I immediately think, "uh oh: one of them is not handling an empty input correctly." Also, way easier to read, copy-paste, and type.
dullcrisp•1y ago
Their point is that in the unshrunk example the “special” value stands out.

I guess if we were even more clever we could get to something more like (…, …, "", …).

gwern•1y ago
The special value doesn't stand out, though. All three examples I gave were what I thought skimming his comment before my brain caught up to his caveat about an empty third argument. The empty string looked like it was by far the most harmless part... Whereas if they are all empty strings, then by definition the empty string stands out as the most suspicious possible part.
tybug•1y ago
shae•1y ago
I care about the edge between "this value fails, one value over succeeds". I wish shrinking were fast enough to tell me if there are multiple edges between those values.
The Hypothesis explain phase [1][2] does this!

  fails_on_empty_third_arg(
      a = "",  # or any other generated value
      b = "",  # or any other generated value
      c = "",  
      d = "",  # or any other generated value
  )
[1] https://hypothesis.readthedocs.io/en/latest/reference/api.ht...

[2] https://github.com/HypothesisWorks/hypothesis/pull/3555

chriswarbo•1y ago
> As opposed to the shrunk version where I immediately think, "uh oh: one of them is not handling an empty input correctly."

I agree that non-empty strings are worse, but unfortunately `("", "", "", "")` wouldn't only make me think of empty strings; e.g. I'd wonder whether duplicate/equal values are the problem.

chriswarbo•1y ago
> I'd rather see this in the failure report:

> ("ldiuhuh!skdfh", "nd#lkgjdflkgdfg", "", "dc9ofugdl ifugidlugfoidufog")

I would prefer LazySmallcheck's result, which would be the following:

    (_, _, "", _)
Where `_` indicates that part of the input wasn't evaluated.
yorwba•1y ago
A minimal reproducing example cannot guarantee that you'll correctly diagnose a bug just by looking at the example (because multiple potential bugs could cause the same example to fail) but it can guarantee that when you step through the code to understand what's happening, you won't have to deal with huge amounts of irrelevant data.

Maybe an alternative shrinking procedure could directly minimize the number of instructions that need to be executed to hit a failure...

edsko•1y ago
(Author of falsify here.) You are absolutely correct that the empty string isn't always the best counter-example. The goal of shrinking is to shrink to the _simplest_ possible value (this is true for all approaches to shrinking). What constitutes "simple" is very much domain specific. It would certainly be possible to write a generator that would shrink to, say, "foo", as the canonical "simplest" example of a simple string. Indeed, since we are working in a lazy language, you could (with a bit of effort) shrink to `undefined` if the other arguments are not used at all.
mjw1007•1y ago
I agree it can be domain-specific, but I think it's more common than not that empty containers, and the number zero, are corner cases rather than typical values.

So I think it would be a decent quality-of-life improvement to make generators of the sort you suggest easily available, and have the tutorial docs use them from the start.