craftkiller

So far I'm the only one here who has provided any numbers. All you and soperj have provided are unsubstantiated claims. Why don't you do some analysis on the "scope of all software" and get back to me? Given the scale, I imagine it will take you at least a couple of years.

> FBI should not run surveillance Ops on Right activists, J6 rioters

I think an important distinction here ICE is Immigration and Customs Enforcement, so they have no reason to be spying on US citizens unless we're harboring illegal immigrants.

The FBI's *is* the domestic intelligence and security service. So an angry armed mob smashing the Capitol building, threatening to hang the vice president, interfering with the lawful transfer of power, and attempting to gouge the eyes out of a police officer are absolutely something the FBI should be investigating and surveilling. If I merely posted online that I *wanted* to do any of those things, I would expect to be surveilled by the FBI. Actually doing those things is a guarantee.

Neither agency should be doing it for political affiliation reasons, but J6 was a lot more than people just "being conservatives".

I'd be willing to spend that much if it unlocked the ability to run top-of-the-line open weight models at their best quantization at a decent enough speed for personal agentic use. We're clearly not there yet, and I just can't imagine dropping the price of a brand new car on something that will only get me heavily quantized versions of the smaller models.

> A fully static binary can run in `FROM scratch`.

Not just `FROM scratch` but also in other contexts. For example:

I wrote my own password manager which lives on a USB drive. Since I compiled a static binary, I can execute it on any Linux machine.

Running static binaries in FreeBSD's Linuxulator is easier. The Linuxulator is a separate set of syscalls that get used when you attempt to run a Linux binary, so a static binary will "just work" for the most part (unless the program needs special filesystems like /proc or /sys). A dynamically linked binary means I need to make sure I have any necessary Linux libraries in the proper location and the Linuxulator's `ld` working properly. Updates to these libraries can then make something that used to work, suddenly stop working. Certainly not an insurmountable task, but there's so many fewer places where things can break when you're just running a static binary.

> Does anyone use/like touch on their windows (linux?) laptops

My retired parents. When they borrow my laptop, I see them trying to touch my regular non-touch screen.

> no contributions

That's just obviously not true. Check out the commit history on FreeBSD and look at all the contributions from Netflix. Off the top of my head they contributed kTLS and asynchronous sendfile which made it such that a single syscall could send the full contents of a file over a socket even with TLS.

Grepping through the git logs for the "Sponsored by" lines shows these top results:

  15925 The FreeBSD Foundation
   3738 Netflix
   2084 EMC / Isilon Storage Division
   1922 Rubicon Communications, LLC ("Netgate")
   1733 Dell EMC Isilon
   1550 Chelsio Communications
   1446 DARPA, AFRL
   1421 Mellanox Technologies
   1262 Klara, Inc.
    784 Arm Ltd
    729 iXsystems, Inc.
    707 Solarflare Communications, Inc.
    552 Netflix, Inc.
    477 Beckhoff Automation GmbH & Co. KG
    473 Microsoft
    421 Juniper Networks, Inc.
    411 DARPA, NAI Labs
    386 Stormshield
    385 Microsoft OSTC
    384 DARPA
    375 NetApp, Inc.
    358 Innovate UK
    355 DARPA, Network Associates Laboratories
    317 Yandex LLC
    299 NVIDIA Networking

One company that isn't in that list but shows up as an author is Datto which gave us native encryption on ZFS (shout out to Tom for writing that!)

Woah, TIL! My Alpine Linux world view has just been shattered. Static linking was frankly *the* selling point of Alpine Linux for me and it turns out I was just plain wrong.

Neat project. One thing I don't see covered: is everything going to be statically linked like it is on Alpine Linux? Is statically linking libc advisable on a NetBSD kernel? I know (unlike Linux) the FreeBSD kernel ABI can change every major release, but I'm not familiar with NetBSD's approach.

twitter format? I've never used twitter (aside from following links when they are posted on HN) so I have no idea what you're referring to. My only association with the phrase "twitter format" is the 140 character limit that I think they increased at some point.

Indeed, the one mistake I keep seeing new people make when writing Dockerfiles is writing them in a way that doesn't optimize for caching. For example, they'll copy their code into the container first and then start installing packages and dependencies. It's an easy mistake to make because the end result is still a functional Dockerfile, they're just wasting time and stressing the poor package servers unnecessarily.

> narrow tools specific things like ripgrep

Ripgrep has the `--pre` flag and `--hostname-bin` flag that enables it to execute arbitrary commands.

> finding files, [...]

Does that tool invoke the `find` command? Because `find` has the `-exec` flag which could then be used to invoke arbitrary commands.

I really think the only safe option is putting your agent in a virtual machine with only a copy of your code (sans credentials), let the agent work, and then copy it back and manually audit it.