My mom asked me why all of the software systems are going down right now. I said it is because all software has been terribly broken for the entire history of software and that software engineering has never been a proper engineering discipline, and now it is forced to mature
With all the noise around formal verification today, it is easy to forget that the Lean or Dafny approach is not the only game in town. When you look closely at how different paradigms connect specifications, proofs, and executable code, four distinct philosophies emerge—each differing on who does the work of finding the witness.
1. Program, Then Prove (Lean, Dafny)
In Dafny or Lean, you write an algorithm that computes the value you want—the witness—alongside a proof that the witness satisfies your specification. In Dafny, the specification and implementation languages are distinct. Yet even in Lean, which fuses them via dependent types, the proof is erased at compile time; at runtime, the machine simply executes the deterministic algorithm you wrote.
2. Program Calculation (Squiggol / Bird–Meertens)
In the Squiggol style, you start with an obviously correct, albeit inefficient, executable program. There is no separate specification and implementation—the specification is the implementation. From there, you apply algebraic, correctness-preserving transformations (like fusion and promotion) to calculate an efficient algorithm. Every equational step is its own proof, though you are still manually deriving the algorithm that computes the witness.
3. Constructive Proof Extraction & Refinement (Rocq, Isabelle/HOL)
Rocq (formerly Coq) and Isabelle/HOL take this a step further through code extraction. In Rocq’s constructive logic, you don't even have to write the algorithm first: you can prove an existential theorem (∃ witness), and Rocq will erase the purely logical steps to extract the computational skeleton of your proof directly into an OCaml program. Classical systems like Isabelle/HOL achieve a similar result through stepwise data refinement, transforming abstract mathematical specs into executable code. Still, the human must construct the proof—and thus the underlying algorithm—ahead of time.
4. Proof Search as Execution (Logic Programming)
Logic programming collapses the entire divide at runtime. You state the axioms, and your query is the existential theorem you want to prove. Execution is the proof search itself, using unification and resolution to dynamically construct the witness you are after.
In the first three approaches, the human invents or vibe codes the algorithm (or proof) that produces the witness, and the machine verifies it.
Only in logic programming do you state what makes a witness valid and let execution itself find both the proof and the witness together—which is why logic programming is my favorite paradigm for formal verification.
Google is sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels. At the same time, Google is trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking. They're also trying to harm GrapheneOS directly.
@BAPearlmutter@bilskirnir3124@thsottiaux Linux has had an immense amount of resources put into security. Despite that, it now has at least a few remotely exploitable code execution holes found weekly along with hundreds of locally exploitable vulnerabilities. It's close to not even having any local security boundaries.
@ha__blr Ды неістотна, што там за жывёла. Як быць з тымі, хто на Сабаленку ганіць па-за хорам - ім камандуюць асобна, ці яны проста не здольныя каманду ўчасна выканаць?
@bilskirnir3124@thsottiaux Linux was created as a rejection of robust software architecture and tools. It's a monolithic kernel with no internal isolation written as memory unsafe code. A typo in an obscure driver for unused functionality can easily create a fully privileged code execution vulnerability.
@piercingsoskov@Walerian13@antdo5 Oh I don't know, how about it haven't started a first ducking war in Europe since WW2, a genocidal empire's boot-licking piece of shit?
На видео, опубликованном изданием «СарИнформ», один из старших казаков объявляет, что вместе с туалетом «передается воровская воля» и призывает младших в туалете «не срать, не ссать и в туза не долбиться», в конце кадеты поют песню Михаила Круга «Кольщик»