> E: I forgot about the mobile Opera ports, that also tracks - I'd love to read about the engineering that went into them!
Can't really meaningfully expand on that, most of that happened before I joined in 2004, but I can tell you that the fact that Opera was extremely memory efficient made Opera Mini (250M monthly uniques, 150k web page transcodes/s) economically possible starting 2005.
We needed to keep the browser/window state around for each user until they clicked the next link. If we threw it out, any javascript state would be lost.
Re:Hacking the Nintendo DSi Browser
by strangecasts on Saturday March 04, 2023 @09:55AM
(#35021158)
That's fair - those are very impressive numbers!
Reading about Mini doing layout specifically for devices with <128px wide displays, I wonder how well today's responsive design frameworks would deal with that...
Re:Hacking the Nintendo DSi Browser
by orangewindies on Saturday March 04, 2023 @03:01PM
(#35023957)
Mini did some tricks so the "display" was much wider than the device display but text columns were wrapped at device display width. So you you could zoom out and see the whole page but the text was readable when you zoomed in.
The Wikipedia page [1] claims* they had an MMU on the expansion cart - so they could have taken your advice :)
* I couldn't find a source, and AFAICT the DeSmuME emulator [2] seems to treat it like a big chunk of linear memory?
[1] https://en.wikipedia.org/wiki/Nintendo_DS_Browser#Memory_Exp... [2] https://github.com/TASEmulators/desmume/blob/master/desmume/...
E: I forgot about the mobile Opera ports, that also tracks - I'd love to read about the engineering that went into them!