Re: [edbrowse-dev] High Hanging Fruit

[Adam Thompson <arthompson1990@gmail.com>]

On Mon, May 14, 2018 at 04:02:09PM -0400, Karl Dahlke wrote:
> I fear we have reached a point in edbrowse where all the low hanging fruit has been plucked.
> I have several sites that "don't work", yet evoke no js errors as they run.
> That means all the javascript executes, but doesn't do everything it is suppose to, or does something slightly wrong, or lacks a connection to our nodes in the edbrowse world, or some such.
> Some of these sites have 20 js files, some have 50,000 lines of js code.
> Most of the js is minimized, and even if you deminimize it, it still has gross one letter variables and no comments, and no way to know what it is suppose to do,
> as compared to what it does in edbrowse, and where the paths diverge.

Agreed.  Unfortunately most of the time I find something that doesn't work
it's part of some incredibly complicated code and there's no easy way to find
the breakage.

> We can only hope to run into some simpler websites that don't work, I call these middle hanging fruit,
> and maybe we can find and fix a problem, and that will fix the other site over there, where the fruit is way up high.
> Other than that, I don't know what to do.
> 
> Another approach is to plow through the 100 acid tests, which is where we started almost a year ago.
> The js is clear and readable, although there is a lot of it, and maybe the time has come for that.

Yeah, I suspect we're approaching that point.  That and also going through some
of the DOM spec and comparing with what we have and probably coming up with a
roadmap to fill in gaps.

As always I wish I had more time to help with this.

Cheers,
Adam.