Chrome issues

Chrome issues

dchanco:

I have to agree with @parislemon on this one. Chrome has become very bloated. I can see it from the amount of memory it requires just to have a few tabs open (ok, some people in the office will argue that very often I have more that “a few” tabs open, but still).
I also found that Chrome is being very aggressive with it’s caching strategy. When developing locally, it’s pretty annoying when even a hard reload will not re-fetch all resources on your page. In my experience (and I know at least a couple of people in the team with the same problem), it takes closing and re-opening Chrome to clear whatever Chrome think it should cache.
Please don’t make it go back to Firefox for everyday browsing.

Originally published at Traackr Engineering.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.