Diego Garcia <
d...@chaos.info> wrote:
> On Tue, 25 Jan 2022 21:40:20 -0000 (UTC), Computer Nerd Kev wrote:
>>
>> That's my approach, except using Dillo, for viewing informational
>> websites.
>>
> Dillo is another excellent choice, except that it cannot handle SSL
> very well -- and evil Google, the self-proclaimed web authority, now
> mandates that all web sites must be SSL.
There are patches for the v. 3.1 development release which help.
Unfortunately 3.1 has some rendering bugs which turn me off so I
do just tend to use a HTTP - HTTPS proxy a lot with 3.0. There are
lots of forks on GitHub but as usual on GitHub the authors don't
bother summarising what their intentions and changes are so it's
hard to choose between them, or even to find the "real" forks
amongst all the non-forks (nothing changed) that GitHub always
seems to list. I'll have to dedicate a day to researching and
experimenting with them one day, but I'm about fed up with
researching and experimenting with web browsers after years of
similar stuff.
>> the mercy of the manufacturer and their specific website, which is
>> often full of Javascript. Then if I want to actually order it then
>> no doubt I'll need JS for PayPal or a third party Credit Card
>> processor.
>
> I have been paid ($$$) to write simple e-commerce web sites.
> Javascript is NOT required. But business owners are often at
> the mercy of developers who in turn are at the mercy of fashion
> and the fashion is javascript.
True, though if they wish to use PayPal or many CC processors it
is required at that stage because the payment processor designs
their own interface. Granted I do buy things from a few small
businesses by browsing their websites in Dillo and then placing
an order by email or phone.
> A browser is nothing more than a GUI interface that is wrapped
> around a rendering engine. Thus, there can, and should, be many,
> many alternative browsers without all the junk.
>
> A case in point was (unfortunately past tense) the Skipstone
> browser:
>
>
http://www.muhri.net/skipstone/
>
> Skipstone wrapped an early versionof the Moziila Gecko engine
> with a very simple, no-frills interface.
I'm of the opinion that to achieve similar performance to Dillo
and Links, you need to deal with the efficiency of the rendering
engine itself, so simply wrapping the engine in a different skin
doesn't cut it. The problem with that is the modern web is only
designed for the Chrome and (with luck) Firefox rendering engines.
So I'm just resigned to using Firefox for things that don't work in
Dillo because looking for slight improvements around the UI side of
things is only a minimal gain.
I did mess about with Fifth browser a few years ago (last updated
in 2016, which wasn't so long ago then). It was a FLTK-based
wrapper for Chrome's WebKit engine, and the experience helped me
form the above opinion. I'm not comfortable about relying on
Google's code anyway, mind you.