frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

DeepSeek V4 Pro 0813

https://openrouter.ai/deepseek/deepseek-v4-pro-0813
899•explosion-s•16h ago•365 comments

Mushroom behind 'tiny people' hallucinations identified

https://phys.org/news/2026-08-qa-mushroom-tiny-people-hallucinations.html
115•wglb•5d ago•73 comments

We tracked down the 16-year-old WAL-reset SQLite bug

https://tailscale.com/blog/sqlite-wal-reset-bug
1011•ropbear•18h ago•188 comments

ChatGPT Desktop (Codex Desktop) for Linux

https://openai.com/codex/
53•allanrbo•3h ago•23 comments

Delta

https://zed.dev/blog/introducing-delta
531•khy•14h ago•186 comments

Qwen3.8-2.4T

https://huggingface.co/Qwen/Qwen3.8-2.4T-A95B
601•Philpax•17h ago•139 comments

Principia Mathematica is modern and insightful

https://okmij.org/ftp/Computation/Impressions/PrincipiaMathematica.html
142•matt_d•9h ago•66 comments

Antiqua–Fraktur dispute

https://en.wikipedia.org/wiki/Antiqua%E2%80%93Fraktur_dispute
77•buzzy_hacker•2d ago•11 comments

2026 Eclipse Webcams

https://jonty.github.io/2026_eclipse_webcams/
478•zoenolan•20h ago•132 comments

Flutter 3.47

https://flutter.dev/blog/whats-new-in-flutter-3-47
92•gumby271•8h ago•84 comments

Why Target Common Lisp for Code Generation?

http://funcall.blogspot.com/2026/08/why-vibe-code-in-lisp.html
95•oumua_don17•23h ago•78 comments

uBlock Origin Is Giving Up the Fight to Keep Ads Off Facebook

https://digitalescapetools.com/2026/08/ublock-origin-stops-chasing-facebook-ads.html
463•Markoff•21h ago•574 comments

Happy 45th Birthday to the IBM PC and Model F/XT

https://sharktastica.co.uk/articles/pc-fxt-45
82•tart-lemonade•8h ago•21 comments

Tim King, AmigaDOS developer, has died

https://amiga-news.de/en/news/AN-2026-08-00070-EN.html
266•doener•18h ago•33 comments

HTML over WebSockets: real-time SPAs with barely any JavaScript

https://en.andros.dev/blog/ef4968f5/html-over-websockets-real-time-spas-with-barely-any-javascript/
191•redbell•15h ago•134 comments

Grok 4.6

https://x.ai/news/grok-4-6
528•iLuddite•17h ago•479 comments

Launch HN: Discovered Materials (YC P26) – AI agents to discover new materials

https://discoveredmaterials.com/research/
135•advaith08•1d ago•28 comments

The punched card tabulator

https://www.ibm.com/history/punched-card-tabulator
5•Bluestein•5d ago•0 comments

Thanks to social media, canned sardines are a scarcity on the supermarket shelf

https://corneroffifth.studio/why-cant-you-find-canned-sardines-right-now/
113•carabiner•10h ago•135 comments

From rubber boots to Copa: When MicroProse Soccer revolutionized football

https://spillhistorie.no/2026/08/08/fra-gummistovler-til-copa-da-microprose-soccer-revolusjonerte...
21•TMWNN•3d ago•1 comments

Why tiny JPEGs look different in Chrome

https://guillaumetech.github.io/posts/jpg-scaling-chrome/
296•gutechh•18h ago•63 comments

Someone is running mass vulnerability scans, spoofing AI bots like ClaudeBot

https://knownagents.com/insights
271•gavinhking•18h ago•200 comments

The Three-Stroke Problem

https://penpot.app/blog/the-three-stroke-problem/
7•elenathor•1w ago•0 comments

Build Wide, Ship Narrow

https://adapt.com/blog/build-wide-ship-narrow
83•ashumz•8h ago•23 comments

Pixel Watch 5

https://blog.google/products-and-platforms/devices/pixel/pixel-watch-5/
139•ortusdux•16h ago•272 comments

Breaking the WAL

https://antithesis.com/blog/2026/wal-reset-bug/
99•wwilson•12h ago•42 comments

Locating an unknown source of radiation in a heterogeneous environment (2019)

https://repository.lib.ncsu.edu/items/451b001d-e63a-4968-866d-3fb3a599b1e7
27•toomuchtodo•4d ago•20 comments

Shade Map

https://shademap.app
186•fredley•19h ago•47 comments

Lovable raises $400M Series C

https://lovable.dev/blog/series-c
137•thoughtpeddler•16h ago•136 comments

Nvidia doubles RTX PRO 6000 Blackwell's MSRP to a staggering $16,000

https://www.tomshardware.com/pc-components/gpus/nvidia-doubles-rtx-pro-6000-blackwells-msrp-to-a-...
10•jacquesm•1h ago•1 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.