chrisshroba

What do you mean by Permafable?

This article contains 19 em-dashes, as well as the following direct quotes:

Not X, but dramatic Y:

- "But the missing few percent are not marginal; they are precisely the hardest items"

- "is not an engineering detail. It may be the entire problem.

- "the galaxy may be quiet not because nobody tried, but because replication is harder than arithmetic suggests."

as well as at least two other longer "not X, it's Y" type phrases.

Also, melodramatic phrasing like "Replication must outrun degradation — and degradation never sleeps."

Yes, someone could have written these manually, but these particular patterns are the things I notice most commonly in LLM outputs that I don't see in known-human writing.

I have something similar, but it's a shell command which writes the command into a file then runs `print -z "$(cat /tmp/command.txt)"`, which prints the command directly to the command line input, so there's no copy paste step needed, it's just ready for me to hit enter (or adjust as needed). It's been wonderful!

This is such a breath of fresh air. I feel like I'm back on Club Penguin!

Can you speak to the total api costs to create one such game? Not looking for exact numbers but I'm curious if to create, say, that snowboarding game, it cost closer to $5, $50, or $500 in usage.

Sometimes your system doesn’t have a graphical session, like a raspberry pi with no x server running, or a cloud compute instance I’m ssh’ed into, or a docker image running on my laptop. Sometimes your system doesn’t have a (particularly usable) text system, like a work computer that disables the terminal or a family member’s MacBook who doesn’t have the time or space to install XCode terminal utilities to be able to use things like brew install.

My point is that it’s not a given that having one means you have the other.

TUIs are wonderful for the first case.

Processes by default get stdin and stdout. If you run a command interactively from your tty, the tty shows your stdout and collects stdin from you to pass to the process. But nothing about Unix prevents you from hooking something else up to stdin and stdout. As another commenter said, you could use sockets and have a completely generic input and output stream which an arbitrary tool could read and write to. Or you could spin up a websocket server that spawns the process and converts between websocket messages and stdin/stdout bytes. Or http requests and long polled responses. Or read input from a speech to text stream and push output into a text to speech stream.

I feel like OP’s main gripe is that persistent interactive sessions should be supported without a third party tool like tmux or screen or zellij, but one of the main strengths of Unix is that it provides platform building blocks which can be composed to create whatever experience you’re looking for.

The contract ends in 2083 (58 years), which even by conservative estimates is well after cars will be able to self-park

Do you have any repository of apps that support that? I’d love to browse them!

Except 91

> Bellwether, a moonshot at Alphabet's X, is using Earth AI to provide hurricane predictions insights for global insurance broker McGill and Partners. This enables McGill's clients to pay claims faster so homeowners can start rebuilding sooner.

Hm, I'm quite skeptical about this claim.