frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AI's top startups are barely publishing their research

https://www.science.org/content/article/ai-s-top-startups-are-barely-publishing-their-research
381•YeGoblynQueenne•9h ago•203 comments

The coolest use for the Vision Pro

https://christianselig.com/2026/07/vision-pro-house/
582•robbiet480•10h ago•235 comments

Show HN: Open-source engine running Gemma 4 26B in 2 GB RAM on any M-series Mac

https://github.com/drumih/turbo-fieldfare
748•gitpusher42•16h ago•259 comments

Superlogical

https://www.superlogical.com/
640•yan•15h ago•389 comments

LLM Honeypot

https://llm2human.pages.dev/
190•8thom•8h ago•52 comments

The Productivity Mirage

https://frantic.im/mirage/
182•msephton•8h ago•60 comments

Keychron announces first open-source firmware for gaming mice

https://www.digitalfoundry.net/news/2026/07/keychron-announces-first-open-source-firmware-for-gam...
353•JLO64•14h ago•141 comments

The Cold Email

https://zachholman.com/posts/cold-email
172•holman•10h ago•69 comments

Logic for Programmers

https://logicforprogrammers.com/
81•_doctor_love•6h ago•7 comments

Anatomy of a Frontier Lab Agent Intrusion: A Timeline of the July 2026 Incident

https://huggingface.co/blog/agent-intrusion-technical-timeline
355•artninja1988•1d ago•205 comments

London’s most equidistant pub

https://equidistance.io/londons-most-equidistant-pub/
15•lambfruit•4d ago•2 comments

A.I. companies are recruiting electricians and carpenters by the thousands

https://www.nytimes.com/2026/07/29/business/economy/data-center-electricians-training.html
269•thm•16h ago•329 comments

Kimi K3-256k

https://www.kimi.com/code/docs/en/kimi-code/models
407•monneyboi•11h ago•118 comments

Angels in Coptic Magic I: Introduction

https://www.coptic-magic.phil.uni-wuerzburg.de/index.php/2026/01/16/angels-in-coptic-magic-i-intr...
39•jruohonen•3d ago•2 comments

Show HN: Edge Drop- #1 productivity and unique clipboard 200 stars on GitHub

https://github.com/Deepender25/Edge-Drop
4•Deepender25•1h ago•1 comments

Turning a dumb AC unit smart (without losing my security deposit)

https://prilik.com/blog/post/automating-ac-nyc/
152•austinallegro•12h ago•119 comments

NSF pilots 4-year PhDs with industry research placements

https://www.nsf.gov/news/nsf-partners-universities-industry-pilot-initiative-four
66•osnium123•4h ago•71 comments

Show HN: CheapFoodMap – A map of good meals under $10

https://cheapfoodmap.com/
182•jaep1•14h ago•184 comments

Some thoughts about Anthropic's new cryptanalysis results

https://blog.cryptographyengineering.com/2026/07/29/some-notes-about-anthropics-new-results/
138•supermatou•14h ago•71 comments

The Rust on ESP Book

https://docs.espressif.com/projects/rust/book/
149•AlexeyBrin•4d ago•15 comments

Man and the Computer by John G. Kemeny (1972 book by the co-creator of BASIC)

https://archive.org/details/mancomputerbyjoh0000john
42•MilnerRoute•8h ago•11 comments

Kuna: Decompiler Development in the Age of Coding Agents

https://noelo.org/blog/kuna-release/
24•matt_d•4h ago•7 comments

Launch HN: Tokenless (YC S26) – Automatic model switching to save money

https://usetokenless.com/
59•rohaga•15h ago•50 comments

A Trampoline

https://dogdogfish.com/blog/2026/07/29/a-trampoline/
97•matthewsharpe3•11h ago•54 comments

Recursive Filters: SMA, EMA, Low‑Pass, and a Tiny Kalman

https://www.staszewski.xyz/blog/recursive-filters/
35•kamilstaszewski•2d ago•8 comments

Show HN: A local merge queue for parallel Claude Code agents

https://github.com/funador/claude-code-merge-queue
32•funador•6h ago•9 comments

SalesPatriot (YC W25) Is Hiring FDEs

https://www.ycombinator.com/companies/salespatriot/jobs/M46X6YX-forward-deployed-engineer
1•maciejSz•10h ago

Refactoring cuisine: how an Iraqi stew sailed to Singapore

https://iza.ac/posts/2026/07/the-journey-of-bamya/
49•infinitewalk•3d ago•13 comments

Hamburg's Stadtpark: A Park Built to Be Used

https://alsterrunde.com/hamburgs-stadtpark-a-park-built-to-be-used/
139•mertbio•3d ago•36 comments

KOReader

https://koreader.rocks/
700•Cider9986•20h ago•215 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.