> A tool for creating and running Linux containers using lightweight virtual machines on a Mac. It is written in Swift, and optimized for Apple silicon.
I may be missing the point of this, other than maybe being able to bypassing some network filtering. At first I was excited, thinking perhaps it's browser based and that it somehow bypassed CORS. But upon further inspection, it's piping everything through their domain. I have no idea whether or not they're trustworthy. I would not be submitting any credentials with this.
I browsed the documentation and saw no references to provisioning database compute/memory resources. Is the persistence serverless, autoscaling, and scale to zero?
Yes but it says nothing about cpu/ram and/or memory/storage/io optimized hardware, cost per hour, or anything like that. Does it scale to zero? Does it autoscale? Will it throttle with spikes in load?
Thanks for the good question! Our free tier offers fixed resources per application (under the hood, a Firecracker microVM with 512 MB of RAM and 1 vCPU) that scale to zero when not in use. For paid users, we'll offer autoscaling per application--we'll share more details on that soon.
It's less "anti Javascript" and more against "it's a great idea to base the entire web around loading completely unverifiable and uncontrolled executable code from anywhere in the universe."
Javascript is a reasonably nice language for what it does, and if it was all still mostly inline or browser managed packages or whatever the modern ecosystem would likely be significantly less of a user-hostile dumpster fire.
Like millions of others, this site looks great in a text-only browser that has no Javascript support.^1 If automatically running other peoples' Javascript or some other "feature" of a popular browser^2 is preventing someone from viewing the text, and the only way to avoid this annoyance is to disable the feature, then the problem is not necessary the feature, but how the feature is being used. People who disable or avoid the feature are not necessary anti-[feature]. They are trying to avoid the effects of how that feature is being used by web developers.
Rendering the primary text content and being able to collapse comments are not on the same level of functionality.
(Though for this particular website, I can see the text just fine with JS disabled in firefox, so I'm not sure why it doesn't work for CaliforniaKarl.)
apple.github.io/container/documentation/
reply