News for hackers. Stuff that matters.
Re:Pyrefly: Python type checker and language server in Rust by phplovesong on Thursday October 16, 2025 @10:38AM (#45605909)
Thats a bad analogy. A better one is should we check the breaks before (compile time) we start the car and drive down the highway (runtime).

At this point you either did check the breaks, or did not. If not you are out of luck if the breaks did infact not work.

Re:Pyrefly: Python type checker and language server in Rust by fastasucan on Thursday October 16, 2025 @04:32PM (#45610342)
Or you test the breaks as you stop to see that everything is clear as you exit your driveway and go into the street.
Re:Pyrefly: Python type checker and language server in Rust by phplovesong on Saturday October 18, 2025 @01:59AM (#45625277)
This sounds like the typical "its good enough" argument. Say we test the breaks manually nine times of of ten. This means we get really hard to diagnose bugs because "this did work when i tested locally". And users get more runtime errors because of half-assed development.

Type systems should be treated like maths, its either correct, or not. In the end, a typesystem is basically just that, its math behind the scenes, more specifically a genre of maths called category theory.