I'm glad you guys like the idea of this project.
I don't have a coprocessor. In fact, the development so far I did in BasiliskII, although I tested the program on a Mac Plus (which I don't have access to currently).
For a thin client approach, it would be interesting to have a special proxy server do the fetching, parsing, and maybe even rendering. It could pass paint instructions or text/rectangle data to the client on the mac. However, the browser would have to respond to scrolling and window resizing, so maybe the proxy server would just pass the style data and DOM tree to the client. I think (perhaps naively) that with a good design and implementation, the full browser could be made performant on old hardware.
Retro68k looks cool. I will look into using it for this project, or for compiling netsurf's dependencies.
I don't have a coprocessor. In fact, the development so far I did in BasiliskII, although I tested the program on a Mac Plus (which I don't have access to currently).
For a thin client approach, it would be interesting to have a special proxy server do the fetching, parsing, and maybe even rendering. It could pass paint instructions or text/rectangle data to the client on the mac. However, the browser would have to respond to scrolling and window resizing, so maybe the proxy server would just pass the style data and DOM tree to the client. I think (perhaps naively) that with a good design and implementation, the full browser could be made performant on old hardware.
Retro68k looks cool. I will look into using it for this project, or for compiling netsurf's dependencies.