Amiga Web browser, is there any usable today?

[jcgeuze]

Originally Posted by Retro1234

NOT Saying it would be easy but easier then building a new browser.
You could make an app for displaying a specific web site like EAB. Download (using some Aminet app) the web page first then some app made in Amos or Blitz or whatever that simply Interprets and displays the web page. It would be lightweight would probably work on 68000. You could even do one for more advanced sites like BBC news etc. Big parts of the site would be pre done for something like EAB it would mainly be displaying text. Avatar etc could be pre converted/cached.

we need more internet connected apps on the amiga. Just connect directly to some api and you can do cool stuff even on an amiga.

[Marce]

today in 2022 there are not a fuccckking usable browser for winxp,
and I'm talking about winxp + new computer with a modern cpu + motherboard
simply there is no interest or nobody talented want or have the time to compile one

just imagine for the Amiga, the situation is worst

yet the most usable browser is ibrowse, you can join Aminet and other Amiga sites or old web sites designed long time ago with old HTML code

[stevelord]

Originally Posted by Retro1234

It would be lightweight would probably work on 68000. You could even do one for more advanced sites like BBC news etc.

The big stumbling block for 68000 is the lack of functioning IP stack. Technically there's AS225 and KA9Q NOS but neither are particularly well supported or well-suited to develop for. The second big stumbling block for 68000 is TLS, which is just too maths-heavy to work without hitting timeouts.

It's possible to overcome this by using a serial link to another box, and plenty of 68000-capable terminal clients. In theory, someone could write a proxy front-end that could handle connections, rewriting, TLS etc to a simplified markup and pass it over serial but that's not a small task either.

Email is slightly different because it can be done via UUCP, which opens up web page content delivery via email. That's on my list of things to try.

[Daedalus]

And then you've got the images. Even relatively uncompressed images like GIFs will take a bit of time to decode and remap on a 68000, JPEGs will take a lot longer. Try opening some sample images on a 68000-based machine and see, then look at how many such images are on even a relatively simple site like EAB.

Browser streamlining solutions like Opera Mini often work by compressing chunks of webpages as image maps - such a solution would be incredibly slow on a 68000.

[Retro1234]

I think for a site like EAB your be ok - images could have a link to convert etc. Eab logos and stuff like that would be part of the app mainly just displaying the text etc. I have to admit I didn't really think about TCP/IP stacks etc. But on a 68020 such an approach should fly.