Google Chrome 34 Is Out: Responsive Images, Supervised Users
An anonymous reader writes "Google today released Chrome version 34 for Windows, Mac, and Linux. The new version includes support for responsive images, an unprefixed version of the Web Audio API, and importing supervised users. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome."
In case anyone wanted to know what responsive images are, I googles this imformative article on the subject:
http://dev.opera.com/articles/...
Bye!
A "responsive image" will load either a small or large version (or multiple versions) depending on the browsers's screen resolution. To do this, it makes an extra request to the server before requesting the appropriate image size.
(The referenced Opera article prattles on and on - Google's faster.)
It is in the works. You can check their progress by opening chrome://flags/#high-dpi-support and enabling the experiment.
I have a dream... Where, instead of learning to support some new "responsive image" paradigm, the web designers of the world focus their efforts on learning to make use of the responsive vector images that browsers already support.
Chelloveck
I give up on debugging. From now on, SIGSEGV is a feature.
True, with IE for XP officially dead, it's finally safe to use SVG on the vast majority of browsers. But good luck efficiently vectorizing a photograph received through a camera lens.
Wow, that's surprising. Chrome eats memory on Ubuntu 12.04. Using version 34, with 19 tabs open, I'm using 2.9GB of private memory and 1GB proportional. This page is using 150MB for me. Maybe it's a 64-bit thing? After a day or so memory usage will approach 6-8GB.
I've found gmail to be particularly bad. My gmail tab is at 400MB right now, but within 24 hours it will balloon to 1GB and then keep growing. I think it usually ends up around 2-2.5GB after a few days, but I've seen it higher. I think there must be some kind of JS memory leak or something.
That said, it's not usually that big of a deal for me. I have 16GB of RAM, most of which is just cache unless I load a VM. Chrome's memory leaks do force me to close the browser and restart it though when I need to free up a few GB for running multiple simultaneous VMs.
You can update to the latest release now using the browser's built-in silent updater
Whoa, whoa, slow down... could you walk me though that?
32-bit Windows -- chrome taking 256MB...at first. Has shrunk down to 165MB a few minutes later. Not my idea of acceptable memory usage.
Opera, with 17 tabs, and it has been running for a few days, is only using 323MB
I come here for the love
when they add a menu bar. Until then, I have ZERO interest in Chrome.
I'm not trolling. I'm completely serious. Removing a standard UI component "just because" is an absolute deal breaker for me.
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano