3 ms·
I think we've seen a proliferation of one concept, often disguised as many things: the container for a program. A long time ago, the program was your whole OS,
by evv 8y ago
I think we've seen a proliferation of one concept, often disguised as many things: the container for a program.
A long time ago, the program was your whole OS, you'd boot into it. The computer is the container.
Then we introduced operating systems, allowing a safer container for bad programs. The program is the container.
One type of program became extremely popular because it enabled delivery of a program via the internet. The web app is the container.
In the web world, frameworks like React have become incredibly popular because they allow people to break up apps into smaller components that can be shared. The component is the container.
Of course, on the back end, similar needs have led to Docker/K8s. The container is the container.
Given that everything in our world is a container, you'd think we would have better tools for composing them. As a web developer, I should be able to embed other web apps and communicate with them like I do with my React components. And I'd also like to be able to boot directly into a web app, and embed native programs and virtual operating systems.
Even when it comes to basics: most operating systems other than Chrome still have yet to natively support the web as a peer of traditional programs.. Electron should't be necessary. Likewise, environments like Docker and VirtualBox should be baked in to the OS that we boot.
The point is, as an industry we need to collectively pull our heads out of our asses, and realize that we'd be much better off refactoring our magnificent existing containers, rather than attempting to invent new ones. (I'm looking at you, iOS/Android..)