Yoshi’s Wooly World Cook’s Fuzzy Fone

A hash is at least consistent when given identical inputs. What they created is more like a digital incinerator.

Historical context, delivery, and handling.

HUP—hang up—is sent to indicate the TTY is closed.
TERM—terminate— is sent by request.

What happens when received is usually up to the process. Most of them just leave the defaults, which is to exit.

Username… almost checks out. It’s missing the leading /nix/store/.

I didn’t want to make it sound too scary 😉

Seriously, though, git really needs an option to treat --force as --force-with-lease. In the exceedingly rare occasion where I might want to completely overwrite a branch, it should be extra explicit by having to type something like --force-and-overwrite.

Solution:

git commit --amend
git push --force

Problem:

The process of discovering best practices on how to keep a clean git history is a goddamned challenge.

I’m surprised you didn’t stick with NixOS. After spending tens of hours learning how to use it, the sunk cost fallacy is strong.

I’d be surprised if it’s not easy to transpile a Markdown document into the format

By hand—if you have experience writing roff typesetting—it is.

Having a program do it for you… you’re going to get something, but it won’t be correct and you will need to fix most of it.

A few problems come to mind:

1. It’s a macro-based typesetting language. As a consequence, there’s a one-to-many association between representations in Markdown with some equivalent in roff. A Markdown paragraph is just a paragraph, but in roff it could be an un-indented paragraph, a paragraph with first-line indentation, a paragraph with line-wrap indentation, or a paragraph with a left margin.

2. Rendering a man page, you have multiple different implementations of man and multiple different implementations of *roff (roff, troff, groff, nroff). The set of macros and features that are available differ depending on which implementation, resulting in one-size-fits-all solutions targeting the lowest common denominator.

3. Ironically, the one-to-many association goes both ways. With Markdown, you have code fences, quotes, italic text, bold text, and tables. With lowest-common-denominator manpage roff, you have paragraphs and emphasis that will either be shown as bold or inverted. If you’re lucky, you might also be able to use underlines. If Markdown tables are no wider than 80 characters, you could preprocess those into plain characters, at least.

4. Despite being more structured with its typesetting, the contents of a manpage are mostly still unstructured. The individual sections within the page and its use of indentation and emphasis are entirely convention, and not represented in the source code by anything more than just typesetting macro primitives.

It could work out if you generate both the Markdown and man page from something with more explicit structure. If the plan is to go from a loose Markdown document into a manpage, you’re going to end up having to write your Markdown document almost exactly like a manpage.

Don’t forget to add incompetent leadership to that list. If feature needs to be shipped by some arbitrary deadline and the engineers are forced to rush through the design process, you end up with a patchwork hack of tech debt that leads to more tech debt.

How’s the weather up there, on your high horse?

Rust wasn’t meant to be the be-all, end-all solution to safety and soundness; it’s meant to be better than the alternatives, confining potential memory safety issues to explicitly-annotated unsafe blocks.

But, hey. That’s okay. With that kind of gloating attitude, I’m sure your code is 100% safe and vulnerability free, too. Just remind me to never step foot anywhere near an industrial system or operating system using it.

Well, now that’s just inaccurate. The hundredth-time programmer isn’t going to use a rake; the hundredth-time programmer is going to use a tool::basic_tool<tool::manual_operator<species::human_t>,tool::handle_type::wood,tool::pronged<5>>.

It doesn’t work like that. They use the self-reported user agent from the web browser that is requesting the page.

The phoronix comment section is a garden of rationality and level-headed thinking in comparison.

Any time Rust is brought up in Phoronix, half of the comments are bad-faith idiots making strawmen and whataboutism arguments amounting to “skill issue, C is 300% safe and nobody needs better” and thinly-veiled contrarian antagonism against Rust because it’s popular.

A comment section worse than that? Impressive.

OP frequently posts pro-Russia articles. I suspect they don’t want to see the difference.

The attack was coming from ::1

Or if that’s too unbelievable, fe80:: has some scary implications while also not likely to ever be a real device.

Contrary to popular belief, it is possible to write software in assembly that is very readable. It takes thought but assembly has the edge with its miniscule footprint and zero-dependency runtime.

“robots.txt files? You mean those things we use as part of the site index when scraping it?”

— AI companies, probably

If there is no way to do so in the GUI, it’s not getting fixed by them, they’ll take it to the Geek Squad if they even decide to fix it at all.

The best part is that Geek Squad probably won’t even fix it.

With the amount of time allocated to tasks and the lack of autonomy retail workers are given, the solution to anything not explicitly written in an employee runbook is going to be “we need to reinstall windows” or “it can’t be fixed, but we have a new computer you can buy”

Neither did I. Now I just don’t have time for sleep.

Used to. I gave up for the various reasons mentioned in my comment. But yes, that’s pretty much what I did. If you’re interested in trying, using WireGuard and iptables is relatively straightforward:

https://blog.arrogantrabbit.com/vpn/net/Wireguard-DNAT-and-IPTABLES/