frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Dutch governments builds alternative for Microsoft based on NixOS

https://www.dawo.community/en/
456•fjfaase•4h ago•215 comments

Platform-Independent SIMD in Go

https://go.dev/blog/simd-experiment
35•yurivish•1h ago•5 comments

Git-bug: Distributed, offline-first bug tracker embedded in Git

https://github.com/git-bug/git-bug
37•alentred•1h ago•5 comments

Pentium II at 600Mhz with Voodoo 3 Emulated on 86Box with M6 Mac Mini

https://nyaa.sh/reviews/mac-mini-m6-emulation
114•hugh4life•5h ago•44 comments

Ink and Switch Interactive Homepage

https://www.inkandswitch.com/
69•iFreilicht•3h ago•13 comments

F-Droid 2.0

https://f-droid.org/2026/09/24/f-droid-2.0-a-new-chapter-for-android-freedom.html
1301•daveoc64•21h ago•372 comments

Topcoat is pushing the boundary of server applications with Rust

https://tokio.rs/blog/2026-09-24-topcoat-server-applications
21•sagacity•2h ago•19 comments

CVE-2025-13032: Entering and Breaking the Avast Antivirus Sandbox Part 2

https://www.safateam.com/intelligence-hub/research/technical-articles/cve-2025-13032-entering-and...
68•safateam•5h ago•17 comments

Show HN: Make cursed fonts like Times New Bastard

https://bastardica.mitpit.com
749•MitPitt•1d ago•101 comments

I'm Tired of Being on the Network

https://matduggan.com/im-tired-of-being-on-the-network/
3•sagacity•42m ago•0 comments

Special Projects (2016)

https://openai.com/index/special-projects/
38•vinhnx•4h ago•23 comments

Oracle on the hook to pay data centre investors even if site has no electricity

https://www.ft.com/content/a96bf05a-a299-4d6a-a753-b298dd0f4016
70•Betelbuddy•2h ago•47 comments

The Mafia may be keeping fentanyl out of Italy

https://economist.com/europe/2026/09/24/the-mafia-may-be-keeping-fentanyl-out-of-italy
112•runeks•2h ago•120 comments

Show HN: Agentic CUDA Kernel Optimizer

https://github.com/bertaye/agentic-cuda-optimizer
19•bertaye•2h ago•0 comments

Show HN: Whiteboard (YC W26) – An open-source IDE for thoughtful software design

https://github.com/devdotfast/whiteboard
336•sidharthkmenon•19h ago•121 comments

Boards of Casio

https://www.ambionix.com/blog/boards-of-casio/
14•fidotron•3h ago•1 comments

Amiga Screens: A Primer

https://www.datagubbe.se/amscr/
29•msephton•5h ago•4 comments

Why is the liver so weirdly regenerative?

https://dynomight.substack.com/p/liver
448•jbotz•20h ago•230 comments

2DWillNeverDie

https://2dwillneverdie.com/
267•surprisetalk•2d ago•63 comments

Fearless SIMD v1.0

https://linebender.org/blog/fearless-simd-1-0/
275•verdagon•3d ago•42 comments

Rails World 2026 Opening Keynote [video]

https://www.youtube.com/watch?v=vDjW_dRyKXY
360•an0malous•1d ago•391 comments

Toyota is taking the Corolla electric

https://electrek.co/2026/09/23/toyota-best-selling-corolla-electric/
362•cisc•1d ago•638 comments

My weird new hobby: Wandering around Tokyo on Google Maps

https://ahmedhossamdev.com/writing/my-weird-new-hobby-wandering-around-tokyo/
358•ahmedhossamdev•2d ago•162 comments

The Test

https://tante.cc/2026/09/24/the-test/
9•latexr•42m ago•0 comments

Opus 5.5 is good at explainer videos

https://launchvideo.io
306•iacguy•16h ago•163 comments

What About Rails?

https://jardo.dev/what-about-rails
113•jrochkind1•10h ago•63 comments

Using LLMs to trace alchemical knowledge and decode 17th century letters

https://resobscura.substack.com/p/ai-labs-need-to-start-funding-historical
144•benbreen•17h ago•31 comments

Two-tier encryption in the UK

https://macanorak.com/two-tier-encryption-in-the-uk/
471•ReturnoftheHack•1d ago•421 comments

Google’s Project Suncatcher to put ML infrastructure in space

https://blog.google/innovation-and-ai/models-and-research/google-research/google-project-suncatch...
201•xnx•23h ago•406 comments

Show HN: Hamilton – a no-internet Android health dashboard, named after my dog

https://play.google.com/store/apps/details?id=com.gads.hamilton&hl=en_US
3•hamilton_app•7m ago•0 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.