VM, Containers, what's next?

VM, Containers, what's next?

Attached: file.png (1000x500, 43K)

Other urls found in this thread:

includeos.org/
twitter.com/SFWRedditGifs

hopefully programs with separate memory and state, but in environment with shared libraries and other resources

Containers are just glorified jails, change my mind.

Only need to sandbox secrets and restrict file system access to only what is necessary.

Pledge and unveil is the future.

containers inside vms anyway because they can't be trusted even after billions of dollars invested

MAC address blockchain

containers within vms under hypervisors running on "bare metal" that is actually subservient to platform controllers

ContainerScript

Serverless functions, maybe.

Literally this
t. Cloud computing engineer

exokernel revival

programs that compile into their own OS.

Half-assed reimplementation of Plan 9

includeos.org/

>have static linking
>invent dynamic linking to make it easier to distribute patches and reduce disk usage
>"oh shit now we have dependency hell"
>reinvent static linking
why do they do this?

proper microkernel multiserver OSs.
Refer to Genode with seL4.

Attached: 1534648720017.png (1920x1080, 2.09M)

Tubs, then tubsports

TempleOS glow in the dark netOS

Attached: 5A3DBDCA-1DF7-4105-952A-EA60922D6A96.jpg (640x736, 323K)

Fully integrated, sandboxed xenokernellic interfaces, supporting petathreading and 3.5D (binary+semi-quantum) graphics emulation.
Literally unhackeable. 200% impossible to break once installed and compatible with every single OS and architecture out there, even those who weren't created yet.

I hate containers so fucking much. They are fine for a bunch of static shit but everyone uses them incorrectly and wonders why 10x shit fucks up when the core fucks up then "we didn't have this problem ever before".

No shit you can't just assume docker is going to fix everything and it's fine to run test shit one because the other container is prod

CIA guy should have an obvious giant afro.

Attached: tyrone.png (1024x888, 31K)

I have some crazy idea for some literally 0 overhead thing called "process".
You just run multiple processes on the same operating system. Isn't that crazy?

Self-contained application packages like snap or appimage. That way you only have to maintain one OS but can have independently functional applications without conflicting libraries, etc. or the headaches of container orchestration.

>private virtual address space
>IO only possible through unified kernel API
>0 overhead
I guess you've never heard of context switching.

Fuck it, let's run everything in the kernel then. Bring back real mode.

>I helped build the Colosseum. AMA!

just use a single address space and load time relocation lmao

>I guess you've never heard of context switching.
Look up how fast seL4 is at context switching.
Then compare with Linux.
Then calculate how many extra switches you'd need to be doing to actually be suffering from overhead relative to Linux.
Spoiler: A lot.

Attached: 1553991847255.png (1920x1080, 1.73M)

sort of. but the major game is the easy of use in the tooling.

yes but also can provide libraries

Proof carrying code, so that you don't need to come up with increasingly deep sandboxes for attackers to play in. Badly behaved programs simply won't be allowed.

Software running directly on the hardware, without any OS

That's pretty cool, thanks for sharing n

A container factory factory
We need more abstraction
More bloat

We start writing everything as software drivers. Ship as source with a bat the downloads the compiler, builds the program, and installs it.

People can't even write a program the effectively utilizes 12 threads and you're going build an OS into every application?

That was the 1940s to late 80s.

What happened?

People started wanting their code to run on more than one machine