edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
* [edbrowse-dev] High Hanging Fruit
@ 2018-05-14 20:02 Karl Dahlke
  2018-05-14 21:38 ` Adam Thompson
  2018-05-14 23:16 ` Kevin Carhart
  0 siblings, 2 replies; 4+ messages in thread
From: Karl Dahlke @ 2018-05-14 20:02 UTC (permalink / raw)
  To: edbrowse-dev

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

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.

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.

Karl Dahlke

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [edbrowse-dev] High Hanging Fruit
  2018-05-14 20:02 [edbrowse-dev] High Hanging Fruit Karl Dahlke
@ 2018-05-14 21:38 ` Adam Thompson
  2018-05-15  4:52   ` Karl Dahlke
  2018-05-14 23:16 ` Kevin Carhart
  1 sibling, 1 reply; 4+ messages in thread
From: Adam Thompson @ 2018-05-14 21:38 UTC (permalink / raw)
  To: Karl Dahlke; +Cc: edbrowse-dev

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [edbrowse-dev] High Hanging Fruit
  2018-05-14 20:02 [edbrowse-dev] High Hanging Fruit Karl Dahlke
  2018-05-14 21:38 ` Adam Thompson
@ 2018-05-14 23:16 ` Kevin Carhart
  1 sibling, 0 replies; 4+ messages in thread
From: Kevin Carhart @ 2018-05-14 23:16 UTC (permalink / raw)
  To: edbrowse-dev


> 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.

It may be true about the acidtests and spec.  What other sites are in the 
several, besides NASA and the baseball reference, that you have been 
pulling up recently? It also gets a little more specific where we have to 
identify what constitutes working since there are some where written 
content on the homepage works, but functional applications don't, or the 
means of navigating by forms and links don't, etc.


thanks
Kevin


---

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [edbrowse-dev] High Hanging Fruit
  2018-05-14 21:38 ` Adam Thompson
@ 2018-05-15  4:52   ` Karl Dahlke
  0 siblings, 0 replies; 4+ messages in thread
From: Karl Dahlke @ 2018-05-15  4:52 UTC (permalink / raw)
  To: edbrowse-dev

[-- Attachment #1: Type: text/plain, Size: 239 bytes --]

I think acid will be a big help.
I went through the first 192 lines, which is just prep, not even acid test 0, and I already found 3 things I was doing wrong, which I have now fixed.
So as time permits I'll move forward.

Karl Dahlke

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2018-05-15  4:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-14 20:02 [edbrowse-dev] High Hanging Fruit Karl Dahlke
2018-05-14 21:38 ` Adam Thompson
2018-05-15  4:52   ` Karl Dahlke
2018-05-14 23:16 ` Kevin Carhart

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).