> Pretty shocking to see the lack of basic thought going into writing what is meant to be critical infrastructure
uutils did not start off as "let's make critical infrastructure in Rust", it started off as "coreutils are small and have tests, so we're rewriting them in Rust for fun". As a result there's needed to be a bunch of cleanup work.
Okay, thanks for the context, but aren't distributions eager to adopt these? Are current GNU coreutils a common vulnerability vector?
> For fun
My idea of fun is reviewing my code and making sure I'm handling errors correctly so that my software doesn't suck. Maybe the people who are doing this, for fun, should be more aligned with that mentality?
"""When we receive a request from a government agency, we send an email to the user account before disclosing information. If the account is managed by an organization, we’ll give notice to the account administrator.
We won’t give notice when legally prohibited under the terms of the request. We’ll provide notice after a legal prohibition is lifted, such as when a statutory or court-ordered gag period has expired.
We might not give notice if the account has been disabled or hijacked. And we might not give notice in the case of emergencies, such as threats to a child’s safety or threats to someone’s life, in which case we’ll provide notice if we learn that the emergency has passed."""
Yeah, I remember when the "Twitter Files" were being released and it turned out that Twitter was illegitimately censoring leaked nudes of Hunter Biden. Whyever would non-consensually posted nudes be taken down other than the suppression of conservatism?
They were also censoring Biden's ties to Ukraine. If you'd actually read any coverage on it that wasn't left wing, you would have known that instead of spinning up this strawman version of what happened.
I'm not making a strawman, there were specific post IDs cited by the Twitter Files as being illegitimate suppression, you could stick them into the Wayback Machine and see that they were literally just photos of Hunter Biden's dick.
More info in the GitHub repo, in the reports folder (sorry, I'm not sure I can add the link here without being flagged).
"Codex + Edgee consumes roughly half the fresh tokens of the normal Codex baseline. Output tokens are marginally higher (+3,312, +19.5%), suggesting the Edgee scenario produces slightly more verbose responses but dramatically reduces context ingestion."
I think the problem being given to Codex for the benchmark is the one in the attached video, where two Codex run side-by-side, working a "standard" dev thingy
Still requires using rust compiled against their llm fork. 'espup' makes it easy if you're okay with using it.
Other than that it works pretty well. This is if you run ESP-IDF, with bare-metal rust it's either best thing ever or meh. Rust community seems to use stm32 and picos more.
I assume their chips don't really exist until they're actually supported by ESP-IDF. The ESP32-C5 was announced in June 2022, received initial support in -IDF in August 2025, and more complete support in December. It seems to have only recently started getting third party dev boards.
uutils did not start off as "let's make critical infrastructure in Rust", it started off as "coreutils are small and have tests, so we're rewriting them in Rust for fun". As a result there's needed to be a bunch of cleanup work.
reply