frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

DeepMind's WeatherNext model achieves breakthrough forecasting cyclones

https://deepmind.google/blog/weathernext-ai-model-achieves-breakthrough-in-forecasting-cyclones/
138•bhavansig•4h ago•32 comments

A Physicist Rigged His Pet Hamster’s Wheel to Upload to Strava

https://www.runnersworld.com/news/a73355106/hamster-wheel-strava-running/
309•aanet•2d ago•71 comments

DeepSeek V4 Flash 0731

https://arcprize.org/results/deepseek-v4-flash-0731
688•tosh•20h ago•413 comments

Hardware backdoors in some x86 CPUs

https://github.com/xoreaxeaxeax/rosenbridge
206•epestr•7h ago•60 comments

U.S. Department of Energy Launches the Genesis Open Models Initiative

https://genesisopenmodels.anl.gov/
284•moelf•15h ago•106 comments

What happens if an entire class of workers loses faith in their careers

https://www.noemamag.com/why-is-everyone-in-tech-so-sad/
794•RickJWagner•1d ago•879 comments

k-Coloring is Faster than Computing the Chromatic Number

https://arxiv.org/abs/2607.25973
26•matt_d•1w ago•3 comments

Now we have a timeline of the OpenAI accidental attack against Hugging Face

https://simonwillison.net/2026/Aug/7/openai-timeline/
96•882542F3884314B•3h ago•106 comments

Europe's free satellite service just made it easier to track wildfires

https://arstechnica.com/gadgets/2026/08/europes-free-satellite-service-just-made-it-easier-to-tra...
82•01-_-•4h ago•6 comments

No One Can Afford to Make Myst Games Anymore

https://www.wired.com/story/no-one-can-afford-to-make-myst-games-anymore/
18•littlexsparkee•2d ago•5 comments

Assembly Hall of Shame

https://github.com/xoreaxeaxeax/asm-hall-of-shame
374•piotrgrabowski•20h ago•92 comments

ao486: x86-compatible Verilog core implementing all features of a 486 SX (2014)

https://github.com/alfikpl/ao486
38•csmantle•6d ago•4 comments

Gateway 2000's hilariously bad ads in the 90s (Part II)

https://buttondown.com/suchbadtechads/archive/gateway-2000-part-2/
6•rfarley04•1h ago•0 comments

Show HN: Rotating torus in terminal (but with kitty graphics protocol)

https://andreadimatteo.com/torus-v0-5.html
8•deotman•6d ago•2 comments

Ancient Library – 1,060 Greek/Latin texts, click any word to parse it

https://ancientlibrary.net/
225•aagha•19h ago•70 comments

NASA figured out how to keep its Voyager 2 probe running for another year

https://www.space.com/space-exploration/voyager/nasa-figured-out-how-to-keep-its-48-year-old-voya...
292•wglb•12h ago•61 comments

2027 memory capacity is reportedly sold out

https://www.ign.com/articles/ramageddon-continues-another-year-as-2027-memory-capacity-is-reporte...
418•inigyou•1d ago•402 comments

SupererDuperer

https://www.shirtpocket.com/blog/supererduperer
132•zdw•6d ago•27 comments

Managing AI Coding Costs at Scale

https://www.databricks.com/blog/managing-ai-coding-costs-scale
267•moonikakiss•19h ago•227 comments

Microsoft Edge is about to lock out older ad blockers, just like Chrome did

https://www.theverge.com/tech/976880/microsoft-edge-extensions-ad-blockers-mv2-mv3
32•eternalreturn•3h ago•20 comments

The Nixpkgs core team has disbanded

https://discourse.nixos.org/t/the-nixpkgs-core-team-has-disbanded/79413
338•Meleagris•12h ago•164 comments

New Amazon Data Center Is Set to Have the Most Polluting Power Plant in the U.S.

https://www.nytimes.com/2026/08/08/climate/amazon-data-center-texas-pollution.html
150•sbulaev•4h ago•160 comments

From One Seed to a Thousand Leaves – Merkle's Authentication Tree

https://0xkrt26.github.io/math_behind_security/2026/08/03/merkle-tree.html
29•denismenace•3d ago•2 comments

An all-sky map of half a million supermassive black holes

https://www.sdss.org/black-hole-mapper-release-20/
178•MarcoDewey•22h ago•40 comments

Carl's Required Reading

https://carlkolon.com/reading/
201•cckolon•6d ago•26 comments

Radical Study Suggests Life on Earth Arose Twice

https://www.sciencealert.com/radical-study-suggests-life-on-earth-arose-from-non-living-matter-twice
170•jnord•1d ago•108 comments

Responding to the next frontier of critical cyber capabilities

https://openai.com/index/responding-next-frontier-critical-cyber-capabilities/
190•artninja1988•21h ago•185 comments

Making Postgres 300x faster for analytics: batching, operator fusion, and SIMD

https://malisper.me/how-we-made-postgres-hundreds-of-times-faster-the-query-engine/
301•poly2it•1d ago•155 comments

Oracle bans AI-generated code from OpenJDK

https://app.dealroom.co/news/feed/oracle-bans-ai-generated-code-from-openjdk-despite-ellison-s-cl...
495•delduca•20h ago•356 comments

Kitesurf: Agent-first browser that runs in V8 isolates

https://blog.cloudflare.com/kitesurf/
202•m3h•1d ago•57 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.