The bigger problem is when people fib about their usage. Saying you only used it in college when you’ve used it more recently is something people do fairly often, and seemingly are encouraged to fib about.

These days I don’t think that happens with digital records. Omitting that incident would almost certainly cause more issues than not now as I’m sure they’d turn up in the investigation. If not included on your sf86 you’d likely be grilled about it.

Investigators are usually reasonable in my experience. If you omitted it because you earnestly forgot because it happened when you were 12, they’d likely understand if you were forthcoming about it during your interview. Investigators are human though so it depends on how they feel.

What they really care about is stuff to try to purposely hide.

> I cannot install it as nonroot user

You still need root privileges to install podman initially.

There’s also some issues with large Results, though I think you have to manually enable that. From their site

> CAUTION: the larger you make the size, more likely will the CRD reach its max limit enforced by the etcd server leading to bad user experience.

And then if you use Chains you’re opening up a whole other can of worms.

I contracted with a large institution that was moving all of their cicd to Tekton and they hit scaling issues with etcd pretty early in the process and had to get Red Hat to address some of them. If they couldn’t get them addressed by RH they were going to scrap the whole project.

That isn’t a core misunderstanding of Go, that’s a core misunderstanding of programming.

About the only code example I saw in here and thought “yeah it sucks when that happens” is the accidental closure example. Accidentally shadowing something you’re trying to assign to in a branch because you need to handle an error or accidentally reassigning something can be subtle. But it’s pretty 101 go.

The rest is… questionable at best.

I value out of the box stuff that works most everywhere. I have a fairly lightweight zsh config I use locally but it’s mostly just stuff like a status like that suits me, better history settings, etc. Stuff I won’t miss if it’s not there.

Like… yes running a process is going to have whatever privileges your user has by default. But I’ve never once heard someone say “full server privileges” or “full nodejs privileges”…. It’s just random that is not necessarily wrong but not really right either.

It uses memory ballooning as its dynamic memory management. Managing this balloon requires some custom implementations if you want to do things like reclaim memory from the guest.

If a large file is created and deleted within the host that disk space stays claimed until the VMs disk is deleted.

No GPU support.

I used to run Arch on my work laptop but getting sleep and hibernate was such a pain I never did get it working quite right. My battery life was not great, partly due to the difficulties getting the system to prefer the iGPU over the nvidia GPU — however poor battery life is something I also experienced with windows laptops.

I’ve been running a MacBook since they switched to Apple Silicon and it would take a lot for me to switch back to a different laptop.