sgsag33

You could create that test environment image beforehand, mirror it and use it for the job that needs it. No need for adding another container within a container.

I would do that up front with a tailered CI job image I would reuse instead of creating it each time again?!

But even if I run in a container e.g. a Github actions runner I can use buildah to build my image right? So no need for another container. Why is there another layer needed?

I guess the business opportunity is to offer a cheap extension to share the account with 3 more concurrent devices for an increase of only 50%. Dang°!

What is the use case for a container in a container?

Why do we even need banks? If they make money by lending money that mostly belong the people (state/feds) anyways, I guess we all would be better if banking was just a state monopol. I guess I'm just missing some points here so maybe someone can help and explain me why this is a bad idea?!

Ofc just download and install the package from the repository as well.

I don't understand your point. There are dpkg and rpm which do exactly that.

They don't last? At least aluminum frames last quite some time. That you have ti replace a component over the years is normal. IMHO.

Which is the logic board aka mainly the computer itself... that's not very sustainable for sure.

Officially? Would be surprised as its soldered to the motherboard!

I would never buy a Apple laptop.

You don't know what it does as its a closed system. But even heavier for me counts the fact that you can't replace its hdd which will fail after years of usage no matter what. Also you will not receive any security updated after seven years.

Don't give up your freedom just because of laziness!

That`s just wrong. If e = mc^2 THAN m is NOT accelerated e...

Amazon as well coming with 18k layoff

Most content that is actively consumed is produced by human - if you claim otherwise please provide some proof at least.

Err why should I want my UI eat up my RAM - it's a resource. I also don't buy this argument that its OK for modern OSes to eat up 3-4GB of RAM and that it doesn't matter and that it frees it if you need it...

In my experience over time dev teams stop looking at that metrics on a board and all we really need are proper monitors/alarms that cover all relevant cases of our domain and writes a slack message or sends an email... KISS!