I'm using https://coder.com for all my development containers. I've got mine hooked up to a k8s cluster, but anything that you can provision with Terraform can be used (e.g. docker containers).
My local library has some dead tree format books with a 500 year support window. Or dead animal or dead reed format books with more like a 2000-year support window.
Unless they are very popular books, they will be weeded (thrown out or or sold) in a matter of a few years though. People imagine that libraries are infinite storehouses of material, but except for places like the Library of Congress they really aren't. There is limited storage space, and in order to get new books they need to discard the old ones that were rarely checked out. Even the example of old books on parchment aren't immune to this trend -- the books we have from Ancient Greece or Rome are just the really popular ones that were copied over and over again, and the vast majority of works from those times are lost.
Your local library keeps papyrus scrolls on open stacks? I mean, sure, yes, there are libraries that haves such things (the university I work for does), but generally they will be kept in special boxes and you need to ask nicely to get to see them. And don't get me started about the crapitude of your average new book these days. Personally, I prefer print books too, but lasting forever is not really why.
Err, no. Something “existing” is not the same as something being supported. Is the original printer still providing free translations to modern languages? Fixing typos and other mistakes? Adding chapters on a regular basis?
It’s kinda ludicrous to call the fact that a thing didn’t spontaneously disappear “support”.
And that fact is also true for all of the books on all of the discontinued Kindles.
Given, the kindle won't last 500 years, but the support window is in some senses longer than for those 500-year-old books, which never received a single security update.
I think the bigger issue is that there's market segments that old product reached and that newer ones don't... and you are locked into their devices by the content you've "bought."
14 year support window is pretty good. Not being able to get a modern device with buttons, and having no way to read your books with buttons, isn't.
Can you cite this? It's not YAML execution syntax, surely Github doesn't do it, the only vector I can see is if you put it unquoted into a shell script inside of a GHA yaml.
All you need is user content containing `backticked`, and a github action referencing that via eg "github.event.issue.title" where the shell would normally execute `backticked` as a command (like echo, cat, etc).
That doesn't feel like a repetition at all? You said that the first time there was "traffic loss but without the extra google money", but that this time there's no extra google money either way.
https://www.eastoftheweb.com/short-stories/UBooks/TheyMade.s...
reply