Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It is not at all the point, the point is to provide a faster browsing experience, Opera servers rearranging the content is just a means to an end.


Indeed, if the iPhone was sufficiently powerful, it would be faster to do do the transformations locally.

edit: this is not a swipe at the iPhone, but support for the statement that using Opera's severs is not a functional requirement.


I don't think it's taken as a swipe at the iPhone, more that I think doing it locally would remove any performance/speed gains that it provides. Granted, you could still cache a certain amount of data locally, but browsers do that anyway.


That's rather my point. If the phone was sufficiently powerful, you wouldn't lose any performance gains. I'm implicitly defining sufficiently powerful to be however powerful the iPhone would need to be to see no performance drop.

Once we assume the CPU and memory of the iPhone can handle it, doing it that way would be faster since there would be less latency involved.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: