jgarzik
Joined 14 years ago
Joined 14 years ago
This generates ZERO passed bills, but lots of pre-election rage bait donations.
End-stage Alexis de Tocqueville material.
The Linux kernel has always been focused on outcomes and outputs, which is the right focus. Here's Linus: https://x.com/LundukeJournal/status/2110524360377458786
Outputs: Code quality and long term maintenance matters. Outputs: Serving users with correctness, security and performance matters.
Focus on "purity of input" is a faith-based political filter, not engineering.
Answering a FAQ: DuckDB is probably the closest analogue, yes.
Unlike duck, (1) sqawk preserves unchanged CSV rows, byte for byte (2) sqawk uses sqlite-like dynamic typing, which is great for heterogeneous, messy Unix text files (3) simpler, more flexible invocation model that does not require referencing file paths inside the query (4) no spilling externally, which can make things faster
Duck is better if the working set is larger than Ram, since it spills, and where columnar batches are heavy.
Primary question: Continue to implement legacy BASIC audio/video and select PEEK/POKE's, or no?