frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Nvidia agrees to acquire Hugging Face for $13B

https://www.businessinsider.com/nvidia-in-talks-to-buy-hugging-face-13-billion-dollars-2026-8
856•mfiguiere•6h ago•360 comments

CEO fired developers to make room for AI. Developers create open source AI CEO

https://github.com/SenteLabsAI/OpenExecutive
455•GrumpySciGuy•5h ago•283 comments

Mechanical Turk shutting down September 30

https://www.mturk.com/
293•tmp10423288442•7h ago•84 comments

Pnpm 12.0

https://pnpm.io/blog/releases/12.0
52•jcbhmr•2h ago•28 comments

GLM-5.3-Flash

https://z.ai/blog/glm-5.3-flash
977•Philpax•17h ago•497 comments

Kusama Yayoi Dies at 97

https://news.jp/i/1465528042000662661
142•phantomathkg•4h ago•11 comments

Tailcat – Like netcat, but over Tailscale’s data plane

https://github.com/tailscale/tailcat
544•nderjung•13h ago•98 comments

Asahi Linux Progress Report: Linux 7.2

https://asahilinux.org/2026/08/progress-report-7-2/
218•pizzaiolo•8h ago•63 comments

Worst-case glacial lake flood scenarios in a transboundary Himalayan basin 2022

https://nhess.copernicus.org/articles/22/3765/2022/nhess-22-3765-2022.html
138•totetsu•8h ago•61 comments

U.S. State Department pauses immigrant visa applications

https://www.wsj.com/politics/policy/u-s-state-department-pauses-immigrant-visa-applications-25b31b23
456•sss111•13h ago•683 comments

Laion Big Video Dataset

https://projects.laion.ai/bvd/
51•ks2048•5h ago•13 comments

An ongoing 3D-printer AGPL violation

https://lwn.net/SubscriberLink/1089390/46116614cc74b814/
379•Velocifyer•13h ago•168 comments

Stripe acquires Clerky

https://www.clerky.com/blog/clerky-is-joining-stripe
150•zakshay•10h ago•26 comments

Zohran and the Short Link

https://iamwillwang.com/notes/zohran-and-the-short-link/
171•wxw•7h ago•61 comments

Twitter Viewer – View Twitter Without Account

https://twitterwebviewer.com/
403•motownphilly•17h ago•227 comments

The Hugging Face incident and the road ahead

https://openai.com/index/hugging-face-incident-and-the-road-ahead/
246•amrrs•12h ago•296 comments

CoMaps: The Offline App That Guided Rescuers Without a Signal in Venezuela

https://hotosm.org/en/news/comaps-the-offline-app-that-guided-rescuers-without-a-signal-in-the-ve...
255•gedankenstuecke•13h ago•55 comments

Actinide is first startup to produce high-assay low-enriched uranium (HALEU)

https://www.actinideinc.com/press/actinide-becomes-first-startup-to-ever-enrich-natural-uranium-t...
153•dsalzman•11h ago•78 comments

IBM Unveils Next Generation Dual-Architecture Processor for IBM Z and LinuxONE

https://newsroom.ibm.com/2026-08-24-ibm-unveils-next-generation-dual-architecture-processor-for-i...
121•porridgeraisin•10h ago•84 comments

FDA approves first in class targeted therapy for metastatic pancreatic cancer

https://www.fda.gov/news-events/press-announcements/fda-approves-first-class-targeted-therapy-met...
203•leopoldj•14h ago•49 comments

Nebula Sans

https://www.nebulasans.com
399•GavinAnderegg•16h ago•147 comments

The Harness Is the Thing

https://scott-fryxell.github.io/blog/the-harness-is-the-thing/
99•sfryxell•14h ago•27 comments

Mold: A Massively Parallel Linker

https://arxiv.org/abs/2608.23228
116•matt_d•10h ago•16 comments

Serve Markdown to AI Agents with Accept Headers

https://acceptmarkdown.com/
122•tilt•11h ago•68 comments

The turbulent AI era is here

https://www.gatesnotes.com/a-turbulent-ai-era-and-critical-choices-to-make
217•LVB•15h ago•194 comments

Taylor Farms: How One Company's Reach Became a National Risk

https://farmaction.us/taylorfarmsreport/
268•speckx•16h ago•183 comments

Getting video models to learn better, faster

https://www.linum.ai/field-notes/data-filtering-gen-video
21•schopra909•5h ago•9 comments

Launch HN: Risklytics (YC S26) – Insurance brokerage for frontier tech companies

https://www.risklytics.ai/
50•AlexRisio•15h ago•19 comments

AWS Acquires DuckLabs

https://ducklabs.com/news/2026/08/26/ducklabs-to-join-aws
1031•onderkalaci•18h ago•303 comments

Tim Curry has died

https://www.theguardian.com/film/2026/aug/26/tim-curry-dies-rocky-horror-show-stephen-king-it-leg...
622•mykowebhn•15h ago•205 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.