frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Gemini 4 Argon

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-4-argon/
806•bradleyg223•3h ago•535 comments

The top secret URSALA, RAQUEL, and FARRAH satellites

https://www.thespacereview.com/article/4951/1
70•Bluestein•1h ago•9 comments

Surprisingly complex waves reveal the brain's inner workings

https://www.quantamagazine.org/surprisingly-complex-waves-reveal-the-brains-inner-workings-20260930/
99•ibobev•4h ago•35 comments

EDG C++ front-end goes public

https://edgcpp.org/#transition
120•iandinwoodie•3h ago•42 comments

Launch HN: Magnitude (YC S25) – Self-optimizing inference engine for agents

https://github.com/magnitudedev/magnitude
115•anerli•5h ago•50 comments

Singapore govt dating app uses Gale-Shapley stable marriage algorithm

https://twitter.com/tuakdotsol/status/2105105417760391258
120•rzk•13h ago•41 comments

Why the Bronze Age Collapsed

https://www.worksinprogress.news/p/why-really-caused-the-bronze-age
44•AnodicElegy•1d ago•31 comments

Dear Software Makers

https://blog.jim-nielsen.com/2026/dear-software-makers/
52•speckx•3h ago•26 comments

Halfspace experimental IDE for solid modeling with distance fields

https://www.mattkeeter.com/projects/halfspace/
51•luu•3h ago•6 comments

5x faster Edge Functions: V8 isolates to Firecracker MicroVMs

https://www.netlify.com/blog/edge-functions-firecracker-microvms/
94•jbott•5h ago•35 comments

A brief history of the Bloomberg terminal

https://spectrum.ieee.org/bloomberg-terminal
203•rbanffy•8h ago•81 comments

CHOMPI portable sampler instrument is now open-source (hardware and software)

https://www.chompiclub.com/opensource
25•lashkari•5h ago•3 comments

Doing a Machine Learning PhD While Working in Japan

https://www.tokyodev.com/articles/doing-a-machine-learning-phd-while-working-in-japan
31•pwim•15h ago•6 comments

You said no MCP

https://earendil.com/posts/you-said-no-mcp/
582•yarapavan•13h ago•330 comments

Coltrane's Tone Circle

https://jtomschroeder.com/blog/tone-circle/
15•jtomschroeder•8h ago•2 comments

Functional Ultrasound Imaging (fUSI) from scratch

https://www.neuroai.science/p/functional-ultrasound-imaging-from
17•pminimax•3h ago•3 comments

Before pixels: Modular industrial dashboards

https://unsung.aresluna.org/before-pixels-modular-industrial-dashboards/
30•leephillips•4h ago•6 comments

Show HN: Lathoa, a math app for kids where the AI is wrong on purpose

https://lathoa.ai/en
15•thanouil1411•8h ago•3 comments

Bild AI (YC W25) Is Hiring a Founding Product Engineer

https://www.ycombinator.com/companies/bild-ai/jobs/dAbC3Gd-founding-product-engineer
1•rooppal•6h ago

I could've accessed 17T Microsoft records

https://blog.faav.net/how-i-couldve-accessed-17-trillion-microsoft-records
236•luispa•2d ago•103 comments

Mechanochemistry of Molecular Motors [video]

https://www.youtube.com/watch?v=hpxbMVbL3Ms
5•surprisetalk•1d ago•0 comments

Great Dirhombicosidodecahedron ("Miller's Monster")

https://www.software3d.com/MillersMonster.php
21•cobbzilla•6h ago•1 comments

The last time my family was replaced by technology

https://manuel.darcemont.fr/posts/the-last-time-my-family-was-replaced-by-technology/
159•megalomanu•10h ago•394 comments

What TLA+ can and can't check

https://buttondown.com/hillelwayne/archive/what-tla-can-and-cant-check/
125•b-man•9h ago•29 comments

CS240 AI Cheating Retrospective

https://turkeyland.net/thoughts/ai.php
69•ArchAndStarch•3h ago•49 comments

Burning Man death rates – A short lesson in statistics

https://ihavenapkinthoughts.substack.com/p/burning-man-death-rates-a-short-lesson
91•viraj_shah•2d ago•113 comments

SDF vs. MSDF vs. Slug: GPU Text Rendering

https://alphapixeldev.com/sdf-vs-msdf-vs-slug-vs-rive-gpu-text-rendering/
124•ibobev•9h ago•50 comments

Responsible Release of AI-Generated Mathematics

https://agmai.org/general-sep29/
68•aureianimus•20h ago•79 comments

Gemini 4 Argon (High): Intelligence, Performance and Price Analysis

https://artificialanalysis.ai/models/gemini-4-argon
69•theanonymousone•2h ago•28 comments

Gitea 28.0

https://blog.gitea.com/release-of-28.0.0/
59•porridgeraisin•2h ago•25 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.