This is sad. I grew up with him as a columnist in like MacWorld or MacUser, to later on see him become an Apple troll. I think he broke his hand off patting himself on the back after his prediction of Apple moving to Intel chips came to fruition.
I was sad when he got fired from PC Mag over that 5g column.
Split horizon DNS is not something I'm willing to do.
I'll just rock out with .internal or .home.arpa, have step-ca and bind communicate to each other, either in step-issuer in kube or maybe even rfc2136 if i feel like a bit of the dns-01 strategy is in order. I slap the internal ca root certs everywhere, and keep my home infra out of the crt.sh logs.
I get it, I could just do *.mydomain.com and slap that wildcard cert everywhere, but it's still in the public logs..
Heh. Copy that floppy. I remember being in the computer labs in high school in the mid to late 90s seeing posters saying "Don't copy that floppy" with strong anti-piracy warnings.
What is with the phrase "increase spend"? It just seems gramatically .... off. Why not say "Apple partners with Broadcom to produce billions more US chips".
This is specifically finance language for budgeting and one of the better ways to speak about this given the public disclosure of this information is substantial for their publicly traded stock.
In English (is it worse in American English?) we frequently convert gerunds into simpler forms of the word. The spending turns into the spend. Related,the request turns into the ask (although this example turns out to have a strong anglo saxon linguistic bias).
It sounds off because “increase” can be a verb or a noun and “spend” can also be used as a verb or a noun (but is more often used as a verb) so you’re brain is trying to parse the sentence with dual meaning terms
Using the infinitive rather than gerund form of a verb to reference a an instance is a common pattern. "I went for a walk," instead of "I was walking."
I think it is interesting to attempt understanding people's choices to shorten "spend" rather than "spending," or to use something longer like "methodology" rather than "method" when they describe the method not a study of methods.
I can’t speak about orbstack, but I’ve worked with docker desktop and podman desktop for years on macOS. Those programs start up a virtual machine that consistently eats ram regardless of whether or not you are running containers in it. Apple container looks lighter weight. In the age of ridiculous ram costs, you gotta save resources.
In addition to memory saver that another person replied about, Docker Desktop also has an MCP server functionality and marketplace (almost all free) and huge AI focus. You can hardly compare it to the others at this point.
I was doing the following at the same time on my MBP this week:
* running a bunch of containers + MCP servers for Claude and Codex on Docker Desktop
* heavily using Claude Code with Fable and packer to build cloud marketplace images
* having Codex write some tests and git flows and reviewing the work in vscode
* automating a character in a Wine-based 1st party RPG in the background running at full resolution
* watching anime on Plex in between Claude Code prompts
It's all about your machine. Docker Desktop is not my worry and if you're a Dev you should have a nice laptop with 32-64GB or more, Apple Silicon Max CPU, etc. This goes for Fusion or UTM also if you want to run a Linux Desktop.
I use docker CE with all container/tui interfaces on all of my Linux systems, but Docker Desktop is nice for macOS or Windows. I almost forgot about Docker Desktop's Gordon, and the AI assistant will do things like analyze your Dockerfile or compose.yml. Super handy.
Docker Desktop's memory saver shuts down VM when containers are not running.
Additionally, Docker/Podman/Orbstack start a single VM, where memory is shared between containers.
On the other hand, Apple Containers create a separate VM for each container, which results in higher memory usage due to Linux kernel overhead, as well as the fact that kernel will try to use most of the available memory for file caching.
reply