The insane amount of backward compatibility in Google Maps

Re:The insane amount of backward compatibility in Google Maps by floatboth on Saturday February 10, 2018 @05:47PM (#16350086)

"more pixels" is quite an understatement. From 320x240 and 640x480 to 1920x1080 and beyond (Sony made a 4K phone!).

But from EDGE to LTE, from weak single core processors to 64-bit 4/6/8 core beasts, from no GPU to what would be considered desktop grade back in the day, from shitty 3gp 144p videos to hardware accelerated 4K H.264/5/VP8/9…

Yeah, people still do messages, but messages now include high quality multimedia edited on device.

Also, web surfing rules. Opera Mini on J2ME and others sucked, it was nothing like the modern mobile web.

[ Parent | on HN ]

Re:The insane amount of backward compatibility in Google Maps by digi_owl on Saturday February 10, 2018 @08:51PM (#16350719)

And here i still find myself preferring OMini set for single column, as it also strips out all the "modals" and JS bloat found on this "modern" web of yours.

As for editing videos or such on a mobile device, bah humbug. The interface is not there in any more than the most rudimentary way. If anything it has regressed unless one happen to have a Galaxy Note, as fingers simply do not offer the precision.

[ Parent | on HN ]