frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Introducing System One Models and Jev

https://typesafe.ai/blog/introducing-system-one-models-and-jev
1292•albelfio•12h ago•378 comments

Apple Reference Image: A New Approach for Verified Photography

https://security.apple.com/blog/apple-reference-image/
208•imwally•6h ago•135 comments

Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations

https://github.com/arnegiacomo/fugleramme
1597•arnemunthekaas•19h ago•200 comments

Show HN: I made a flight simulator, except you're just a passenger

https://inflightsimulator.com
155•rkotcher•1d ago•66 comments

An update on Wayback Machine access

https://blog.archive.org/2026/09/15/an-update-on-wayback-machine-access/
511•ChrisArchitect•14h ago•264 comments

Negativland, Culture Jamming, and the Art of Making Something New

https://blog.archive.org/2026/09/11/negativland-culture-jamming-and-the-art-of-making-something-new/
73•bananaboy•5h ago•18 comments

Doing Everyone Else's Job

https://yosefk.com/blog/doing-everyone-elses-job.html
43•luu•1d ago•19 comments

Gemini 3.8 Live and 3.8 Live Extended Thinking

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-8-live-gemini-3-...
393•leumon•14h ago•260 comments

Datamimic – don't let your coding agent invent its own test world

https://github.com/rapiddweller/datamimic
31•ake2l•3h ago•5 comments

Building a Linux GPU Driver for the M4 Mac Mini in One Month

https://codyho.dev/blog/gpu-driver/
291•ADevWithAnIdea•12h ago•169 comments

Recreating Voodoo Graphics and a Late-1990s Gaming PC on an FPGA

https://nand2mario.github.io/posts/2026/zsst-voodoo/
116•zdw•9h ago•30 comments

German Rheinmetall open-sources its Battlesuite connected weapon system protcol

https://rheinmetall.github.io/onboardapi-documentation/9.10.0/index.html
210•summarity•11h ago•72 comments

Why I'm still bearish on LLMs after Navier-Stokes

https://dank.systems/posts/2026-09-15-ai-bear.html
206•jaykru•14h ago•215 comments

We got admin access to Baseten's production GitHub

https://www.strix.ai/blog/baseten-harbor-github-pat-takeover
271•bearsyankees•14h ago•149 comments

A software thing I built: GPS on a 25MHz 486-SX

https://forum.vcfed.org/index.php?threads/a-software-thing-i-built-gps-on-a-25mhz-486-sx.1258966/
14•JPLeRouzic•2h ago•6 comments

Intelligence per Watt: Measuring Intelligence Efficiency of Local AI

https://arxiv.org/abs/2511.07885
26•pythonic_hell•1d ago•0 comments

Saving Jet Fuel

https://tech.marksblogg.com/scikit-decide-openap-optimal-flight-planning.html
88•marklit•9h ago•41 comments

MartyPC – A Cycle-Accurate IBM PC/XT Emulator

https://github.com/dbalsom/martypc
9•yitchelle•2h ago•1 comments

Show HN: Capsule – Single-file web apps that save their data into SQLite

https://withcapsule.app/
322•bashtian•18h ago•129 comments

Learning to solve hard problems in RL for LLMs by never giving up

https://mnoukhov.github.io/posts/ngu/
86•natolambert•13h ago•4 comments

Let's make quality the norm again

https://www.forbrukerradet.no/short-life/
377•ingve•22h ago•385 comments

EU Floats Canada Becoming the Bloc's First 'Associate Member'

https://www.bloomberg.com/news/articles/2026-09-16/eu-proposes-canada-become-the-bloc-s-first-ass...
8•helsinkiandrew•12m ago•3 comments

Chopping up books when they're physically too big

https://attainablefelicity.mattkirkland.com/20260915/cut-up-your-books.html
166•matt_kirkland•13h ago•155 comments

Jean-Pierre Serre turns 100

https://mathshistory.st-andrews.ac.uk/Biographies/Serre/
131•jzox•11h ago•24 comments

An interactive world map of the stories cultures have told

https://originmap.sunnyguha.com/
42•momentmaker•2d ago•4 comments

Stay discoverable in search while disallowing AI training

https://blog.cloudflare.com/accountable-mixed-use-ai-crawlers/
63•djfergus•5h ago•37 comments

The Beauty of Roundabouts

https://gruhn.me/blog/2026-09-14/
45•ngruhn•2d ago•62 comments

Suspected sabotage causes major Netherlands rail disruption

https://www.bbc.com/news/articles/c8ly49w9g1edo
479•choult•22h ago•424 comments

WangNet – 1.8 MB, zero-dependency Numberwang adjudication in 11 languages

https://github.com/GraafHenk/numberwang
149•Liogra123•12h ago•52 comments

Most people prefer traditional architecture

https://www.worksinprogress.news/p/do-people-prefer-traditional-architecture
332•alihm•1d ago•285 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.