jgarzik

Yet more meaningless political theatre.

This generates ZERO passed bills, but lots of pre-election rage bait donations.

End-stage Alexis de Tocqueville material.

Anti-AI is rationally and logically incorrect, because it focuses on inputs, rather than outputs.

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.

Testing and feedback welcomed, heading in to 1.0 release soon.

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.

Humbly requesting feedback and testing from users and their agents.

Primary question: Continue to implement legacy BASIC audio/video and select PEEK/POKE's, or no?

Skeptical of their engineering, with replies to questions like this: https://x.com/jgarzik/status/2031312666036146460?s=20

Rough draft for comment - passes core cpython 3.12 tests with an inspired design.

Does it isolate keys away from bots?

Already done, months ago, with better taste: https://github.com/rustcoreutils/posixutils-rs

I needed this for experimenting. Sharing with others. Please file issues, to extend.

The next iteration of awk?

Passes 100% of userland tests, supporting 99% of linux syscalls (though very few filesystems!)

Early boot and early page table setup, logging single characters to simulated serial console.

Then keep adding tests/features/tests/features/...

I always wanted a kernel where I can experiment with the device driver model, eBPF, device tree and more. Now I've built one:

Somewhat related, a kernel in Rust: https://github.com/jgarzik/hk

Accelerated by Claude Code, leashed tightly by unit and integration tests, and test-driven development.

Speaking as a compiler and kernel expert, the productivity boost for domain experts is real.

Compiler status: Full C99 compliance, test suites pass, alpha-beta stage, starting to test on Gentoo and open source package builds "real world builds"

Posixutils status: Very close to 1.0 (all POSIX utils, all POSIX util features, tests pass)

enums > defines

Love this! I had the same idea, and was pondering funding apps like this. Was going to call it "SimpleFree" and focus on privacy, offline, mobile, games.

Thanks! There is very little info available on useful, working Veo 3 techniques, so I cobbled together what I could find, with my own experiments: https://x.com/jgarzik/status/1926496820311605577

No, not using sqlite under the hood.

This is using Rust's native sqlparser crate, which is quite powerful, plus an internal memory database.

We can extend this beyond what sqlite SQL supports.

Suggestions welcome!

posixutils is far, far more utils than coreutils. posixutils includes awk, m4, a C compiler, etc.

At the same time, as you note, this does not include GNU extensions inside each utils.

The posixutils-rs project just merged a full, POSIX compliant shell.

By amusing coincidence, I wrote a Redis clone in Rust: https://github.com/bloq/memds

It is hoped that posixutil's awk's bytecode-based modern design should keep performance high, theoretically higher than ancient C-based awks.

Inspired by Ray Gardner's "wak" awk implementation https://github.com/raygard/wak

A volunteer benchmarking our awk on a 1-billion line text file would be welcome.

I wouldn't assume. The awk implementation likely stands up well for a 1-billion-row challenge, with its thoughtful bytecode-based design.

Redditors ran some quick performance tests on parsing, also: https://www.reddit.com/r/rust/comments/1fd7qgl/comment/lmelo...

Updated in 2024, no less! (2024 version still has UUCP though, heh)

Most people really, really do not understand the large amount of military traffic on Telegram, and the consequence of that during wartime... and how valuable that is to multiple nation-states around the world.

Strategic comms, soldier command and control, battlefield drone command and control, intel asset management.

Armchair analysts need to put on their big-boy military pants.

DKBTrace and POV-Ray were my introduction to CGI.

Open source meant it was possible for an Average Person with No Budget to do CGI animations and stills.

The entire repo is written in Rust. bc is one of 145 utils specified by POSIX.

posixutils is something more. (see README.md)