[Edbrowse-dev] One program Two processes

[Karl Dahlke <eklhad@comcast.net>]

Well as we consider various architectures
I always keep in the back of my head that we're a couple of volunteers in our spare time.
(I wonder how many fulltime people work on Chrome, or Edge.)
We may not have the resources to do it the best way.
In fact this year has been an anomaly, with Geoff and Kevin joining us,
and really making good progress.

> That's cool, but what if async starts taking a long time,
> like some sort of exponential algorithm or something?

Then it takes a long time.
It shouldn't, unless the js page is badly written, but if it does, then so be it.
I'm not trying to be glib, just saying we don't have the time or resources
to build a preemtive time slicing operating system in edbrowse,
that can context switch in and out of js sessions,
in an engine independent fashion, or even within the constraints of a fixed engine -
I think we're just not going to have the time for that.
Pieces of js run under the ospices of the engine,
without preemption, in their particular context / window,
and we just hope they are sane.
On a modern computer, a js computation would have to be insane
to last more than a millisecond, and sure it could happen,
and if it does edbrowse might not react as well as Chrome,
but sometimes we're trying to get it functional,
without necessarily covering all the corner cases.

P.S. If my finances continue to nosedive I might have to return to the work force,
and that's one less edbrowse developer.
Let's hope that doesn't happen.

Karl Dahlke