>Plus, I don't understand why u shouldn't believe Fab when he says that his MOS version >is faster than AROS one ?
I see this video from Fab when load http://www.cnn.com and with AROS OWB i get same times(7-8 sec) to show page first.safari/chrome is lots faster around 2-3 sec.netsurf on my winuae need 4-5 sec.not optimal, but better as OWB on AROS, netsurf Team is working to add a cache.I think when its done, netsurf is speed up.
http://fabportnawak.free.fr/vids/cnn.mpg
sure he tell situation is not optimal, but normaly i think when doing a vídeo before first try once and then do it again to see if time is same and reproducable.and when his OWB really is so fast as firefox or other windows webkit browsers, then its clear notice if a browser need 2-3 sec to show a page or 7 sec.
Also you can see on Video, he do no reload.he type the name in, its possible that there is something on cache.
When my router is responsive, cnn displays in 3-4s. But should we remind you once again that network speed and latency is a *very* important factor in this kind of benchmark?
And no, there was no cache involved in my test.
but still, it run slower because of slow internet,OWB load too much data from internet before he begin to show the page.also when press the page back button the load of the last page is same slow as a full load.this i see on 68k OWB and AROS OWB.
normaly when press page back the page is show in around 0,5 sec complete.On netsurf some pages are show fast some not, but as netsurf Team told teh cache is currently broken and is rewritten to do disk caching too.
There's a page cache in WebKit, that just happens to be disabled by default in OWB (understandable considering their embedded orientation). When page cache is enabled, it obviously displays in a fraction of second, if the page is still in cache.
I dont know, i have not compile it.there is a AROS version from 2006 nobody use.and now when somebody really need cairo, he need the newest version, maybe here is change something.Or where is the source for MOS Cairo
Cairo is a backend and i think it need some platform dependent graphic stuff.
But i remember when firefox change to Cairo render it get too slower.I think best is use SDL and fix teh scroll problem by using HWsurface and sdl blit command.
Cairo/Pixman straight-compiles (unless you add hw acceleration of course, then it's a lot more work). And there's a reason to use Cairo over SDL too. In OWB, they also moved from the SDLgfx graphics backend to Cairo one, because WebKit just needs a capable gfx library and SDLgfx isn't up to the task. So in current OWB SDL implementation, rendering is done with Cairo and the result is blitted with SDL.
i think on 68k there are more devs that can do it.But there seem no perfect browser for amiga currently here.
the browser thats done on MOS or OS4 are done from the OS Developers.On a commercial OS its important to have a better than nothing solution as fast as possible to sell more systems.
but developers that develop for fun, want do something better usefull or when they get money(see AROS Port)
And as can see, for 68k there are no bounties or something else as on AROS or OS4 or MOS.
I'm not sure what you imply there, but should I remind you I didn't charge nor ask anything for OWB? It wasn't a bounty either.
Also, to me, it seems OWB+SDL and NetSurf+SDL ports are closer to the "better than nothing" quick hacks than the other NetSurf or OWB ports on OS4/MorphOS. At least, there was some real work involved in the latters to build a GUI around the engine, unlike SDL ports.
@0amigan0
Fab already said MOS OWB is faster. I say: let's trust his words.
Actually, I didn't say MorphOS OWB was faster than OS4 OWB. They're roughly the same I'd say, both faster at scrolling than AROS or Linux ports (which is normal, since they lack a proper scroll method). The main difference would be MorphOS port uses a thread for network, which avoids blocking UI.
