frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

πFS

https://github.com/philipl/pifs
395•helterskelter•4h ago•102 comments

A Written Language for the Cherokee So Efficient It Was Thought to Be Magic

https://www.smithsonianmag.com/innovation/man-created-written-language-cherokee-did-efficiently-e...
19•grahambargeron•1h ago•7 comments

How JPL keeps the 13-year-old Curiosity rover doing science

https://spectrum.ieee.org/curiosity-rover-jpl-mars-science
147•pseudolus•5h ago•30 comments

Anthropic requires 30 day data retention for Fable and Mythos

https://support.claude.com/en/articles/15425996-data-retention-practices-for-mythos-class-models
62•lebovic•1d ago•17 comments

I'm Eric Ries, author of "The Lean Startup" and new book "Incorruptible" – AMA

482•eries•8h ago•384 comments

Cybersecurity researchers aren't happy about the guardrails on Anthropic's Fable

https://techcrunch.com/2026/06/10/cybersecurity-researchers-arent-happy-about-the-guardrails-on-a...
44•speckx•6h ago•41 comments

What is it like to be a bat? (1974) [pdf]

https://www.sas.upenn.edu/~cavitch/pdf-library/Nagel_Bat.pdf
46•shadow28•2h ago•38 comments

PgDog is funded and coming to a database near you

https://pgdog.dev/blog/our-funding-announcement
360•levkk•9h ago•182 comments

L'Affaire Siloxane

https://mceglowski.substack.com/p/laffaire-siloxane
124•idlewords•1d ago•18 comments

World Capitals Voronoi

https://www.jasondavies.com/maps/voronoi/capitals/
16•vincnetas•2d ago•3 comments

Show HN: Extend UI – open-source UI kit for modern document apps

https://www.extend.ai/ui
114•kbyatnal•7h ago•24 comments

GeoLibre 1.0

https://geolibre.app/
117•jonbaer•5h ago•8 comments

Farmer donates land for a park, city sells it for $10M as data center land

https://www.tomshardware.com/tech-industry/farmer-donates-land-for-a-park-city-sells-it-for-data-...
305•maxloh•4h ago•106 comments

Mercedes‑Benz starts large‑scale production of electric axial flux motor

https://media.mercedes-benz.com/en/article/bebac2af-acdc-465a-9538-adb0bf3d8ccf
494•raffael_de•15h ago•314 comments

Show HN: HelixDB – A graph database built on object storage

https://github.com/HelixDB/helix-db/tree/main
78•GeorgeCurtis•7h ago•29 comments

Building an HTML-first site doubled our users overnight

https://mohkohn.co.uk/writing/html-first/
951•edent•10h ago•439 comments

Claude Desktop spawns 1.8 GB Hyper-V VM on every launch, even for chat-only use

https://github.com/anthropics/claude-code/issues/29045
307•tonyrice•5h ago•212 comments

Authentication issues related to API requests

https://www.githubstatus.com/incidents/fcj3088jg1wx
148•Multicomp•7h ago•29 comments

Anthropic's model naming, extrapolated

https://samwilkinson.io/posts/2026-06-09-anthropics-model-naming-extrapolated
249•sammycdubs•4h ago•71 comments

Apache Burr: Build reliable AI agents and applications

https://burr.apache.org/
162•anhldbk•8h ago•87 comments

Show HN: Atlasphere – Live Infrastructure Diagrams

18•andreygrehov•1d ago•4 comments

Policy on the AI Exponential

https://darioamodei.com/post/policy-on-the-ai-exponential
108•yjp20•4h ago•165 comments

All 9,300 Japanese train station, animated by the year it opened (1872–2026)

https://jivx.com/eki
178•momentmaker•10h ago•60 comments

Raspberry Pi 5 – 16 GB, $350

https://www.adafruit.com/product/6125?src=raspberrypi
121•akman•3h ago•140 comments

Show HN: Artie – Real-time data replication to your warehouse, now self-serve

https://www.artie.com
18•tang8330•17h ago•5 comments

Smudging the game disc to make speedrunning 'SpongeBob' faster

https://www.inverse.com/input/gaming/the-dirty-secret-that-makes-speedrunning-on-spongebob-a-lot-...
62•pncnmnp•20h ago•36 comments

A €0.01 bank transfer could compromise a banking AI agent

https://blue41.com/blog/how-we-helped-bunq-secure-their-financial-ai-assistant/
155•tvissers•9h ago•143 comments

Free financial literacy platform for kids – 90 lessons, no paywall

https://learnfinly.com
3•narensara•1h ago•0 comments

Pick and Place: Carbon Nanotube Nanoassembly Process

https://www.c12qe.com/news/pick-and-place-carbon-nanotube-quantum-chip-manufacturing
18•bpierre•2d ago•4 comments

DiffusionGemma: 4x Faster Text Generation

https://blog.google/innovation-and-ai/technology/developers-tools/diffusion-gemma-faster-text-gen...
264•meetpateltech•7h ago•67 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.