> The full menagerie of shapes is too diverse to get a handle on, so mathematicians tend to focus on convex polyhedra
The phrase "tend to focus on" suggests it's not an exclusive thing. However, you're right -- it appears that the Rupert property only applies to convex polyhedra, so the article title and text is at the very least incomplete given that a sphere is a shape.
> Serverless Advocate: Yes, but instead of paying for infrastructure overhead and hiring 5–10 highly specialized k8s engineers, you pay AWS to manage it for you.
This argument lost me. If you’re running your own k8s install on top of servers, you’re doing it wrong. You don’t need highly specialized k8s engineers. Use your cloud provider’s k8s infrastructure, configure it once, put together a deploy script, and you never have to touch yaml files for typical deploys. You don’t need Lambda and the like to get the same benefits. And as a bonus, you avoid the premium costs of Lambda if you’re doing serious traffic (like a billion incoming API requests/day).
If you buffer starting with the ( character, then you'd still send the [text] part of the link, and worst case is that with no matching ) character to close the link, you end up buffering the remainder of the response. Even still, the last step is "flush any buffered text to the client", so the remainder of the response will be transmitted eventually in a single chunk.
There are some easy wins that could improve this further: line endings within links are generally not valid markdown, so if the code ever sees \n then just flush buffered text to the client and reset the state to TEXT.
There are a few things in our implementation that make a more general solution unnecessary. We only need the output to support a limited set of markdown which is typically text, bullet points, and links. So we don't need code blocks (yet).
However, the second thing (not mentioned in the post) is that we are not rendering the markdown to HTML on the server, so []() markdown is sent to the client as []() markdown, not converted into <a href=...>. So even if a []() type link exists in a code block, that text will still be sent to the client as []() text, only sent in a single chunk and perhaps with the link URL replaced. The client has its own library to render the markdown to HTML in React.
Also, the answers are typically short so even if OpenAI outputs some malformed markdown links, worst case is that we end up buffering more than we need to and the user experiences a pause after which the entire response is visible at once (the last step is to flush any buffered text to the client).
Maybe as an eventually consistent life form using extremely slow message passing. Though gravity becomes a major factor that would limit the size unless it’s incredibly sparse.
One of my favorite episodes of Love, Death, & Robots is “Swarm”. Worth a watch.
While the search offered is handy, I watch logs on multi-pod workloads via:
kubectl logs -f -l app=api --max-log-requests=50
This follows along all pods with the given label (app: api) for up to 50 pods or however many you want. Quite useful when I'm looking for specific output such as ERROR logs to just pipe it to grep like this:
The revenue milestones appears to show annual revenue goals rather than monthly. For example, if you have only 1 plan at $1/month, the $1000/month target shows you need 84 subscribers.
Fun fact: it's a different device, but the principle is the same as the device used in the documentary Tim's Vermeer. It results in the images overlapping between your left and right eye and you simply paint until the difference goes away.
> However, if it's inside a plastic case that blocks light, it doesn't.
You want an ordinary diode to allow current to flow easily when it senses light? Simple: shine a powerful laser at the plastic-encased diode and it will melt the plastic and liquify the metal, fusing it together and allowing current to flow again. See? You just needed to try harder.
> Seems like all these other factors should matter too!
The way I read it was that there are some minerals that are no longer there to begin with because they're simply not in the soil. For nutrients (like vitamin C) created as part of the growing process, speed is the only factor that matters.
So yes, it does matter but unless you have a way of knowing which farm(s) the produce came from and what their soil mineral content is, that's not something you can factor into your purchasing decision.
> I think an IDE, a keyboard, and a projector are better than printing code blocks at a specific revision which is identified by a computer-readable id, and which must be given a new ID and a new printed page every time you want to try executing a new version.
You're making several incorrect assumptions here:
1. That you can't interactively try out the code as you're editing it.
2. That the system as implemented is the final vision of how the system ought to work forever.
From https://youtu.be/5Q9r-AEzRMA?t=150 "Anyone can change any program at any time and see the changes immediately", which demonstrates live editing the code and seeing the projected flow lines change color. So you can keep editing and iterating on the program, trying out your changes without ever having to print anything. Once you are satisfied with your improvements, you then "commit" the code, which results in the system printing out a new page with its new identifier.
And if any part of your expectations isn't how things work, it's likely because this is a research project and nobody has written the code to make it behave the way you'd like. Since Realtalk is built on itself, one would only need to make the appropriate changes to improve the system.
> "This is a big object. An object of this size is going to have the equivalent impact energy in the hundreds of megaton approaching a gigaton," Brown said. "That'd be a regional impact. It's the sort of thing that if it hit the east coast of the U.S., you would have catastrophic effects over most of the eastern seaboard. But it's not big enough to affect the whole world."
> And so I would say, in response to what’s often asked, which is: If depression isn’t simply an abnormality in serotonin, why would you prescribe an SSRI? And I think the answer is that through serotonin and norepinephrine, we can promote the brain’s capacity for resilience against the adverse effects of stress and depression on the brain.
I suspect a lot of people overestimate how special their code is. Also, if your code exists in a private repo on GitHub, then you're already trusting the same third party when using GitHub Copilot.
If some company’s alcoholic beverage doesn’t get approved, you wouldn’t say “finally some faith in the firearms system” just because the Bureau of Alcohol, Tobacco, Firearms, and Explosives handles both.