@wanninger

What if we build a browser ecosystem from scratch with a fresh perspective?

I want to be able to have thousands of browser tabs running concurrently.
The modern hardware can handle this load if we build the browser with this goal.

How does Erlang handle thousands of "processes" easily? I know they are not real processes but the ideas from the Actor Model and Erlang can revolutionize how we create browsers.
.
Surely there can be a common system which handles thousands of "processes" as browser tabs.
Sharing common immutable data/code would help immensely if there was such a system.

Basically, a browser built on Actor Model, with high density bytecode and which shares code/data as much as possible.
Performant functional data structures and structural sharing systems will be written once as a common subsystem. That is not a concern.

I want these personally as a browser user (and someone with a computer engineering degree) who wants to experience the full power of modern hardware. Currently, most modern software is written sloppily.

If we care enough when creating software, the results might surprise us.

@wanninger How much RAM does security really need? It doesn't seem like it uses much in OS kernels.
How much would it use if it is taken to its practical minimum limit while preserving all its aspects?
Assets and even browser, JS code should be lazy loaded. I think that would help immensely.
JS code and data should be securely shared when its possible.
Ideas from Functional Data Structures can enable an efficient way for sharing (e.g. structural sharing).
The interpreter code and immutable data can be shared.
A new tab shouldn't use any RAM for JS if it doesn't have mutable JS data or code.

Even 3rd party code can be shared securely. Copy-on-write semantics can be used if it's modified by a tab.

If we share every possible code and data in a secure and efficient manner with every system/subsystem, and don't load any code or data until it's necessary, I think the RAM usage will drastically reduce.

How can I precisely and easily inspect how much RAM each part of browser's subsystems use?

@vy

Different axioms can be found. That would make that theorem irrelevant.

Micro-kernels have good ideas but the kernel I talked about doesn't have to be a micro-kernel.

A micro-kernel like efficient kernel.

Maybe it will be radically different than what we call kernels. Thus, no current limiting theories will hold.

@vy

I think, with all the knowledge and experiences we accumulated, we can achieve it now.