Earlier quoted context omitted.
I don't want my browser on my phone to require a gb of memory thank you very much. It's bad enough that desktop browsers like chrome are complete memory hogs without stuff like this, I hate to imagine what a phone browser would be like if "fuck it, modern phones have heaps of resources" was the approach to all decisions. Next you'll be suggesting a compression algorithm that only works anywhere near realtime when it…
Your phone won't require it. It will temporarily use slightly more memory (12MB is very little on modern Android phones), and it would decrease the time required to render the page (due to less CPU power required to compress then decompress over gzip -1).
> Memory usage isn't that big of a concern anymore