cpuguy83

11 ms·

151.
by cpuguy83 2y ago
Apple _shipped_ Metal in 2014. Kronos started their work in 2014 and wasn't even named as such until 2015. The full spec wasn't released until 2016.
152.
by cpuguy83 2y ago
Sorry no. Vulkan literally did not exist. That's not obfuscation. It didn't even exist. Had Apple adopted Mantle then where would they be now? Apple did what they do, took ownership of their own stack.
153.
by cpuguy83 2y ago
Metal predates Vulkan. But also I'm pretty sure Apple doesn't care if an app is portable.
154.
by cpuguy83 2y ago
The whole thing is, it's not basic. Loopback does things that Blackhole cannot, granted it requires a kernel extension. But if Blackhole does what you need, that's awesome!
155.
by cpuguy83 2y ago
I don't recall exactly my issues, but definitely found some things that didn't work this way. It's also a pain to set things up this way (compared to loopback or hijack).
156.
by cpuguy83 2y ago
Rogue Amoeba provides some really great software if BlackHole isn't enough for you. Loopback and Audio Hijack in particular.
157.
by cpuguy83 3y ago
Loved doing a degaussing.
158.
by cpuguy83 3y ago
Descent 3 had so many bugs on my graphics card... which I want to say was an ATI Rage. Consequently I played D2 more until we got our hands on a Voodoo3. gabbagabbahey!
159.
by cpuguy83 3y ago
Nausea no. Migraine trigger? Yes. :(
160.
by cpuguy83 3y ago
You might want to try the actions cache "--cache-to=gha --cache-from=gha", but still it needs to pull that stuff down, just that locality is likely better here. There's also an action out there "GitHub cache dance"
161.
by cpuguy83 3y ago
I'm not sure what you mean here. "RUN --mount type=cache,dest=/foo" is exactly for keeping a persistent cache on the host.
162.
by cpuguy83 3y ago
Was the 787 not a brand new plane? That got grounded in 2013 due to battery fires.
163.
by cpuguy83 3y ago
So the security policy is the headache then, not the containers or even Kubernetes?
164.
by cpuguy83 3y ago
Container processes are just processes running on the host.
165.
by cpuguy83 3y ago
Containers are just processes running on the host where the process has a different view of the world from the "host". The host can see all and do all.
166.
by cpuguy83 3y ago
You don't need to have these tools in the container to troubleshoot the workload in a container.
167.
by cpuguy83 3y ago
I've had to replace the charger on my kid's surface pro 3 times now in 3 years.
168.
by cpuguy83 3y ago
Not really defending Apple here since they do have an unfair advantage over on these trackers. But even the weather app triggers that same location pop up.
169.
by cpuguy83 3y ago
It's one of those things that you don't usually need to think about, so you don't. Not too long ago I hit this same realization with pipes because my "grep ... file | sed > file" (or something of that nature) was
170.
by cpuguy83 3y ago
I'm not talking about OCI images (again, that's the _output_). I'm talking about how they are built. OCI images are OCI images, they get extracted the same way no matter if there's conflicting paths or not. What I'm
171.
by cpuguy83 3y ago
https://github.com/reproducible-containers/buildkit-nix
172.
by cpuguy83 3y ago
docker build is backed by buildkit, which is available as a grpc service ("docker build" is a grpc client/server). Buildkit operates on "LLB", which would be equivalent to llvm IR. Dockerfile is a frontend. Buildkit
173.
by cpuguy83 3y ago
Even with the Dockerfile format you can union those filesystems (COPY --link). People use the Dockerfile format because it is accessible. You can still use "docker build" with whatever format you want, or drive it completely via A
174.
by cpuguy83 3y ago
I'm not exactly sure what you are referring to here. You can have as many "FROM"'s as you want. "FROM scratch" along with "ADD" is also valid (for non-image dependencies). From there you do not need t
175.
by cpuguy83 3y ago
You are describing the makeup of an OCI image, which is the _output_ of a typical docker build (and also the output of the nix image builder). While docker build can/does output OCI images, that is only an output. How that output come
176.
by cpuguy83 3y ago
Right, all builds are dependent on their inputs. Your inputs determine your outputs. If your input(s) change, then so does your output. We are saying the same thing here, I'm just trying to point out this is exactly how docker build wo
177.
by cpuguy83 3y ago
It's content addressable, just what are you addressing? The content address of a docker image is a json blob (referencing other objects). The content address of a Dockerfile "RUN" command is the content address of what came b
178.
by cpuguy83 3y ago
So, outside of the fact that a nix build disables networking (which you can actually do in a docker build, btw) how would you check all those build scripts in nix? You seem to be comparing 2 different things.
179.
by cpuguy83 3y ago
So the thing here is docker provides the tooling to produce reproducible artifacts with graphs of content addressable inputs and outputs. nix provides the toolchain of reproducible artifacts... and then uses that toolchain to build a graph
180.
by cpuguy83 3y ago
This is not how docker works. Docker, exactly like nix, is based on a graph of content addressable dependencies. What you are describing is chaining a bunch of commands together. Yes, this forms a dependency chain stored in separate layer

More ›