Re: [edbrowse-dev] Threads

[Kevin Carhart <kevin@carhart.net>]

Congratulations on the great work!  And commendations to Geoff also.  I 
would be a candidate to compile for Windows but I think the expense 
of the commercial compilers is probably what has stopped me when I 
have occasionally thought about doing it.  It says "visual C studio is 
assumed on Windows."  I never knew what to do when I read this.  I'm 
sorry to ask this in a sleepy way after there was probably a thread about 
it a while ago, but is there any chance of (a) cygwin or (b) DOS/CMD? 
These environments are both a natural analog for CLI unix, are they not?

I was just telling Geoff offlist that edbrowse would be absolutely lovely 
and useful at my new job, so this could be the moment when I become the 
guinea pig (and even work on it during the day a little?  :)  ) and it 
will redound to the firm's benefit, I'm sure.

Either way, thank you Geoff, Jim and others.  Tidy5 developers should be 
commended early and often, it's such a crucial backbone I hardly think 
about it anymore!




  On Tue, 27 Aug 2019, Karl Dahlke wrote:

> There never has been an edbrowse windows user and there may never be.
> As others have pointed out on this list, edbrowse dovetails with other command line tools in a unix or even mac environment,
> and isn't nearly as useful on windows.
> In other words, it is sometimes edbrowse plus other things that provides the power.
> So why did we bother one might ask?
>
> Well, at times I had dreams of getting grants, actually getting paid to work on edbrowse, and maybe subcontracting to some of you as well,
> and grants are easier to get if you can claim your software runs on every platform.
> Believe me the whole blind industry is windows centric, jaws, nvda, window eyes, on and on.
> Rehab and employment centers teach windows and only windows.
> So it was mostly for marketing.
>
> But it turns out I can no more get a grant than I can swim the ocean.
> It's just not one of my skills.
> So if we give up on that, then I really don't worry about the windows port much any more, unless it is easy to maintain.
> I've learned a lot though from it, and I thank you for all your hard work,
> plus your continued tidy support.
>
> Certainly switching to threads and away from fork and processes and wait and so on makes it easier.
>
> An easy test is
>
> edbrowse www.nasa.gov
>
> That exercises all sorts of stuff, including a dozen javascript files which are fetched and loaded in parallel by threads.
> If you get about 170 lines of stuff
>
> =
> 170
> ,p
>
> then it's all good.
>
> You can watch the fetches in parallel and other things at debug level 3
>
> db3
> ub
> b
>
>
> Karl Dahlke
>