fishpen0 @ fishpen0 @lemmy.world

Posts

0

Comments

12

Joined

2 yr. ago

In this case it is a bad idea though. Wheelchair bound cripples and dementia patients aren’t going to farm a single crop no matter how many of them you throw into the fields. They’ll die there and the crops will wither away and feed nobody and make no tax revenue

Mostly not yet. They did restrict the bandwidth on relay, but anyone with half a brain can open a port and that still allows apps to direct connect without relay. Honestly I wish could just force it to never relay since randomly my iPad will use relay even when I’m on the same network but that’s more because the new iOS app since the rewrite is dogshit.

Lifetime pass since 2012 here.

The lone star tick actually usually does not carry Lyme, you are thinking of deer ticks. This is an entirely different condition that is caused by an allergic reaction to the lone star ticks saliva which your body confuses with carbohydrates found in most mammalian meats leading to a long term meat allergy.

Falls apart due to cave situation. No jarvis for first suit or mini arc reactor

The dude is an ex officer and a former world record holder, a 4 time world champion in shooting, has been top 3 in 27 european and world championship competitions, and has been competing for over 2 decades now. He won silver at the last Olympics

The woman recently won Gold at the Olympics.

The joke in the original meme is that she needed all that equipment and perfect form to beat a guy who literally walked on with a pack of ciggies and a tshirt and shot with both eyes open. It is very likely he is a much better shot than her in any real world scenario given he is also former special military. He probably wasn’t trying that hard at all.

Much like the guy, Torvalds invented Linux and Git may be one of the most influential minds in software in our lifetimes and he doesn’t have a desk full of blinking lights and $15000 desk setups. He doesn’t need a bunch of try hard poser shit to be great.

Broadcom knows they bought a dying platform. Their strategy is to isolate the customers incapable of ever migrating and charge them as close to near bankruptcy as possible. They’ll get their initial return on investment in under 5 years and then eventually just let VMware die because new businesses that are still nimble all moved to other platforms anyway. They’ll hit Lotto tickets with a few whales and keep 5-10 devs on to patch stuff for those whales and print 100-1000x return on costs in perpetuity.

This is why I said “most containers most of the time should”. It’s a bad practice to write to the inside of the container and a better practice to treat them as immutable. You can go as far as actively preventing them from writing to themselves when you build them or in certain container runtimes, but this is not usually how they work by default.

Also a container that is stopped and restarted will not lose its internal changes in most runtimes. The container needs to be deleted and recreated from the image to do that

Yes, technically chroot and jails are wrappers around kernel namespaces / cgroups and so is docker.

But containers were born in a post chroot era as an attempt at making the same functionality much more user friendly and focused more on bundling cgroups and namespaces into a single superset, where chroot on its own is only namespaces. This is super visible in early docker where you could not individually dial those settings. It’s still a useful way to explain containers in general in the sense that comparing two similar things helps you define both of them.

Also cgroups have evolved alongside containers at this point and work rather differently now compared to 18 years ago when cgroups were invented and this differentiation mattered more than now. We’re at the point where differentiation between VMs and Containers is getting really hard since both more and more often rely on the same kernel features that were developed in recent years on top of cgroups

A million times this. A major difference between the way most vms are run and most containers are run is:

VMs write to their own internal disk, containers should be immutable and not be able to write to their internal filesystem

You can have 100 identical containers running and if you are using your filesystem correctly only one copy of that container image is on your hard drive. You have have two nearly identical containers running and then only a small amount of the second container image (another layer) is wasting disk space

Similarly containers and VMs use memory and cpu allocations differently and they run with extremely different security and networking scopes, but that requires even more explanation and is less relevant to self hosting unless you are trying to learn this to eventually get a job in it.