Presumably there is still the need to ventilate. So the concentration can also be measured more centrally. That is how the mechanical ventilation unit in my house works. For both humidity and CO2.
Our groceries from AH in NL come in foldable crates. The cooled items sit inside a plastic bag inside a foam box in the truck. The delivery person stacks the crates and foam boxes, brings them to your door, rings the bell. They hand the bag with cooled products to you and then you get the crates. You return the folded crates. This works just fine. They are also quite adept at filling the crates to a maximum. Unfortunately not always in the smartest way because they sometimes put the fragile things at the bottom and the heavy items like bottles of soda on top.
So this seems like a pretty solved problem. Of course you have to be home to receive the cooled products. There are some startups that sell cooled boxes that delivery persons can open with a code to put stuff in but they are not popular. Since Covid people tend to be at home more often than before.
AFAICT, they always run in the background anyway. CarPlay is mostly just a pass through canvas rendered on the phone. The system can decide at anytime to overlay something on the CarPlay canvas.
Yes. I think podlet was one of the tools that the output of podman, or the quadlet tool, suggested I use.
I will try again. Currently I have a systemd service that tries to start my services with `podman compose `. Sometimes this fails, when I start the service interactively it just works. Unknown what exactly is the issue.
Build as in building images or as in building a project when mounted in a container? I notice 3-4x performance degradation of our maven builds in containers. With golang I haven’t noticed much performance degradation, but that may be because it is fast enough anyway.
Do you have a good canonical source on this conversion? I’ve tried the conversion tools that came out around the release of podman v4 and again with v5. But somehow the files being generated contained deprecated features which pointed me to use different commands which led me to yet again different structures which when executed in systemd brought me back to what I originally had. I never got it to work fully.
I think a stronger brand name. Also on macOS I found Docker Desktop to be more straightforward. Also lately it has been very error prone. Randomly failing at mounting files, or cleaning up networking rules, or suddenly becoming bog slow so I have to restart the VM.
Podman on macOS feels miles less refined. Orbstack is a way better choice.
I only use podman on Linux and there it is blazing fast. Even so, most features seem to be geared to be able to replace kubernetes in combination with systemd. And then something simple as docker compose support is flaky and it’s TUI/ux lags behind the original.
What I noticed is that when the conversation starts the agent is pretty able to read from and write to files. As the conversation continues (and maybe sub agents are spawned) it forgets how to do this, complains, tries to resort to running shell or python code, sometimes it works. Sometimes it asks me to execute the code. If I refuse and point out it worked before than sometimes it remembers how to write, but mostly not and I need to start a new session.
When using Zed with the CoPilot integration I use Claude Opus and never had this issue.
I’m mainly looking at the 16” mbp because of the beautiful screen and the refined hardware. For the work I use the laptop on my lap for (or in the evening at the kitchen table) to compare products, research holidays etc, I notice that 13” is too small to comfortably hold two browsers next to each other plus room for notes.
Then sometimes when I’m on the go I like to play a game or two, but nothing seriously requiring graphics power
SSD speed and RAM speed start mattering when memory pressure is high. And when doing stuff with video and photo editing.
The storage price is indeed steep and now the RAM price as well. I wish I hit the buy button when I had the chance before the price increase.
I checked a 16” framework last week comparing to the 24/48GiB MBP. The ssd is significantly faster, the RAM is almost twice as fast, the CPU has more cores. The only benefit is having a dedicated gpu. At more or less the same price.
Admittedly, the screen ratio is better with the framework. But prefer the matte screen of the MacBook.
I was mostly going by the “far-right” classification in the title. If indeed the whole spectrum has switched it will be less extreme when viewed from within the spectrum.
Is it so hard to imagine that someone willing to take such a principled stance on privacy that they start a company to provide a privacy focused vpn company that they also hold other extreme views?
It takes a certain kind of personality to become a founder especially more do for such a strongly principled company and adhere to it.
Cars here are inspected yearly anyway or you go change winter tires for summer tires. (Because we lack the place to store them in typical houses.) So you are at the garage anyway every 6 months to 12. Then they can also do the other stuff
Really? Most hostile? I’ve only ever contributed to the comp sci topics on stackoverflow and visited the ones for math/physics and sysadmins. Were some replies a bit pedantic, yes. But I’ve also seen a lot of very extensive answers and helping out people. Maybe I’ve been lucky to use it in the golden age.
While it is true that some cars can brake harder due to downforce etc, the point from GP was that both cars brake/ decelerate at the same rate. Regardless of how exactly that deceleration is achieved.
It is instant for me when using podman but by no means instant when using docker. Docker on Linux native is stay way faster than on macOS and Windows. But so far running with podman has the lowest overhead I have seen.
Microsandbox claims to start faster than docker, and it is isolated from the host, and to work with OCI. Why would I still want to use docker? The only reason I can imagine is that I actually want to be able to dynamically share resources between containers instead of dividing up VMs a priori.