14 ms·
RenderingNG: An architecture that makes and keeps Chrome fast for the long term
- Traubenfuchs 5y agoHow come processors and browsers become faster every year but the internet feels as slow and bloated as ever? How long can this x% faster continue? There must be some theoretical optimum, how far are we away?
- theodric 5y agoChrome became so bloated and crap and slow that in 2020 I moved over to Firefox (which has been imperfect, but better), so my anecdata suggests that browsers don't actually get faster overall, but ebb and flow as feature creep and optimization compete for dominance.
- MayeulC 5y agoTyping this on Midori Android, it feels faast! I was using Firefox until a few days ago, but I feel I should change. That's on a Galaxy S4, mind you. Dillo is blazing fast on desktop, but doesn't support https very well. It also doesn't support JavaScript, which isn't a big deal to me.
- art0rz 5y agoTo me it feels like bloated browser profiles makes the browsers sluggish. I get annoyed with how slow Chrome is, so I switch Firefox. After a while the Firefox profile gets bloated and I get annoyed and switch back to Chrome with a clean profile and it feels really quick again. Ad infinitum.
- mavhc 5y agoThe fix for 99% of firefox problems is: firefox -p, make a new profile
- pabs3 5y agoThe Firefox profile manager and Chrome temporary files would let you test this theory.
- ksec 5y agoI dont understand how profile could make such a difference but that is also my experience as well. Everything is fast in a clean profile.
- jd3 5y agoOn Firefox, if you have an unbelievably large number of entries in your History, Bookmarks, and/or Downloads (your Firefox "Library" — chrome://browser/content/places/places.xhtml), you could theoretically become limited by insert/update performance in Firefox's embedded sqlite, I believe.
- sirk390 5y agoHttps multiplied latency by three when opening websites compared to 10/15years ago where many websites were http. And also many websites include more tracking, for example Google search results used to directly send you to the result page. Now they first send you to Google so that they know you clicked but it also adds noticeable latency.
- no1lives4ever 5y agoWith the advent of CDNs, edge routing and global hosting, things have actually gotten way better for those of us who use US based websites from the other side of the world. I am from India and back in 1990s the latency used to be huge because we had internet via satellite. Then we got internet via submarine cables but even with that latency is > 300ms for a server based in the US. Now in 2021, most popular websites use CDNs and have servers based out datacentres closer to India and the page load speed and latency has gone down significantly for us. But page bloat is a different matter, I still remember spending the greater part of a day (or maybe more0 downloading the MSIE 2.0 installer on a 1200bps dial up modem. Today page sizes > 1mb are common even on mobile sites.
- xnx 5y agoI'm pretty sure Google currently uses an async ping https://www.w3schools.com/tags/att_a_ping.asp https://www.w3schools.com/tags/att_a_ping.asp) instead of a redirect to log what's been clicked. It's been a very long time (if ever?) since they didn't have result click logging at all.
- sirk390 5y agoIndeed, I didn't know about the ping attribute. However, you will see they still do click tracking on the google image results for example. And if you check this article from 2013, you will see that they had it back then (I'm not sure when they removed it): https://chainsawonatireswing.com/2013/03/20/how-to-disable-googles-click-tracking-crapification-of-search-result-urls/ https://chainsawonatireswing.com/2013/03/20/how-to-disable-g...
- gostsamo 5y agoJevons paradox to the rescue: the more ads you can handle, the more you will be served.
- vultour 5y agoWhy is this comment flagged?
- Traubenfuchs 5y agoSome 10x rockstar developer with a wrinklebrain considered it low IQ rambling and got offended but got quickly btfo by fellow smoothbrain hackernews readers who share my sentiments.
- vbezhenar 5y agoPopular apps will be as slow as user can tolerate. Because if they're not slow enough, it invites developers to introduce another abstraction layer. Good thing is, that it's possible to create truly groundbreaking apps using non-conventional techniques, as web becomes faster and richer with new APIs. For example with Wasm and WebGPU it's possible to create AAA games running in the browser. Someone will do it. It'll be awesome. I have one example to prove my words. I used iPhone 4S. With iOS 6 I was able to use navigator software which worked very snappy and awesome. Few years later with iOS 9, navigator was very slow, forcing me to buy new phone eventually. With iPhone 8 it returned to blazing fast. But it did not have any new functions. They just started to consume more memory, just because they can. My UX did not change a little bit. I just had to buy new phone with infinitely faster CPU and loads of RAM, just to keep my UX from degrading.
- mofosyne 5y agoIf only we can charge a price for taking up too much ram or cpu cycles.
- eru 5y agoJust don't use it?
- flohofwoe 5y ago> For example with Wasm and WebGPU it's possible to create AAA games running in the browser. This has been promised since at least the WebGL and asm.js days. It still won't happen, but not mainly for technical reasons, but for business reasons. ...but of course also some technical reasons. Asm.js/WASM and WebGL/WebGPU are fine, but most other web APIs are a mess and the web is a highly unstable platform, APIs are deactivated or deprecated on a whim, APIs change behaviour unpredictably, behaviour differs between browsers, etc etc... TL;DR: the web needs a proper "DirectX initiative" like what Microsoft did in the late 90's to get Windows gaming off the ground.
- nsomaru 5y agoWhat are the business reasons? Surely the web is just a platform for delivery? Payment etc can happen through the browser.
- afgrant 5y agoIt has been for more than a decade: “What Intel giveth, Microsoft taketh away” https://en.m.wikipedia.org/wiki/Andy_and_Bill%27s_law https://en.m.wikipedia.org/wiki/Andy_and_Bill%27s_law
- flohofwoe 5y agoNot just the internet: case in point, the new Xcode 13 has some really embarassing performance problems on my mid-2014 13"MBP. I guess the Xcode team switched to shiny new M1 Macs between Xcode 12 and 13.
- realusername 5y agoIt's good I need to use the apple laptop & Xcode only just to build my flutter app, otherwise I would have given up just how slow it is, every click takes ~5 seconds.
- afgrant 5y agoI don’t intend this as facetious, but how many years do you expect closed-source OS vendors to support their first-party hardware?
- flohofwoe 5y agoThe thing is, this is in areas that worked fine for over a decade. Somebody must have decided that Xcode's text input code (that's one of the things that got slower) needs to be rewritten for no obvious reasons, but then didn't optimize it as much as the old code. What's the point of new hardware if the new software that's written for it makes it just as slow (or in this case: much slower) than the old hardware?
- ddalex 5y agonot OP, but for the lifetime of the hardware ? or, at least, should be specified in T&C when buying the hardware I am still pissed off that my 2012 Macbook Air is no longer receiving OS updates - compare that to Microsoft that allows me to run windows on basically any PC
- afgrant 5y agoThe “lifetime of the hardware” is defined by the lifetime of the supporting software, which ultimately boils down to the popularity of the platform you’re on
- easygenes 5y agoSometimes I wonder how much of this feeling comes from expecting more from more power/thermal/area constrained devices. My experience working with top-shelf workstation-grade CPUs in mid-tower cases with excellent cooling is far separated from my experience even with M1 Macs. Having 16 cores, 64GB+ RAM, and 300W of thermal capacity is a big improvement. https://nanoreview.net/en/cpu-compare/apple-m1-vs-amd-ryzen-9-5950x https://nanoreview.net/en/cpu-compare/apple-m1-vs-amd-ryzen-... Compare Zen 3 to M1... M1 is a generation ahead in lithography and enjoys an appreciable thermal/efficiency advantage resultingly. Zen 3 and M1 have neck-and-neck single core performance on many tasks. Yet Zen 3 can offer many more cores and make up for its efficiency in raw thermal envelope availability. Then also the expectation from older and more inexpensive devices. If one gets used to M1-level performance, a $200 CPU from 4 years ago starts to look quite slow; e.g., the Ryzen 5 1600: https://nanoreview.net/en/cpu-compare/apple-m1-vs-amd-ryzen-5-1600 https://nanoreview.net/en/cpu-compare/apple-m1-vs-amd-ryzen-... Once we start to look at the truly power constrained, say a mainstream phone from a few years ago; let's say the iPhone 8/X since it's one of the best selling in recent history. Then you're at about 50% of the single threaded performance AND working with fewer cores. https://en.wikipedia.org/wiki/List_of_best-selling_mobile_phones#2017 https://en.wikipedia.org/wiki/List_of_best-selling_mobile_ph... https://www.cpu-monkey.com/en/compare_cpu-apple_a11_bionic-1655-vs-apple_m1-1804 https://www.cpu-monkey.com/en/compare_cpu-apple_a11_bionic-1... There is another large factor at play in the past 20 years in particular though: that is the increasing predominance of "Python-like" languages. I mean that in the sense that more of the code we interact with on a daily basis is written at a very high level than 20 years ago. Python in particular is just about the least efficient of all the most widely deployed languages. Ranking Programming Languages by Energy Efficiency: https://haslab.github.io/SAFER/scp21.pdf https://haslab.github.io/SAFER/scp21.pdf 2021 Top Languages: https://spectrum.ieee.org/top-programming-languages/ https://spectrum.ieee.org/top-programming-languages/
- solarkraft 5y agoWhat the browser giveth, the web developer taketh away. I tremendously hate it and it’s not like developers are incapable of building performant software, quite the opposite. But that’s just not where the resources go. The common sentiment (I have heard this directly uttered) is “If the user has 8GB of RAM, why wouldn’t I use it?”.
- wahern 5y agoRecent exceptions: 1) Chrome in Android has recently begun to hang when trying to go back to a previous page. It's gotten so bad that I end up clicking multiple times, which all register in rapid succession. If I click more times than the history depth for the tab (say 3 or 4), I end up back on the home screen and a lost tab with lost (or at least not conveniently recoverable) history. 2) AMP. When Google began pushing AMP my objections were mostly based on principle; performance was mostly a wash for me. Now the AMP viewer is so slow and so crash prone that I'm conflicted. On the one hand, I'm glad to see that AMP is clearly failing. On the other hand, Android and Chrome still strongly favor AMP, and I'm too lazy to wrestle with Google over default settings, so when I don't have the presence of mind to explicitly open a web site (e.g. when using Google News) I'm left to suffer the poor performance and bugginess in addition to other intentional AMP headaches--lack of copy+paste, less scrolling and zooming control, etc. Not quite the same thing, but related, technologies like QUIC are really only beneficial in the context of a web ecosystem built by Google. QUIC shines on websites pulling in many resources from disparate hosts, which in most cases is a situation created by advertising and analytics services. IOW, these days much of the benefits of Google's work simply pays down the debts Google itself created or advocated. And while Google still stands out for the amount of labor it invests in open source security and performance, it's just a matter of time before we pass break even into negative return territory. That happened long ago with Google Search itself; Google Search results are as slow, irrelevant, and obscured by obnoxious and misleading advertising as the competitors it originally, rapidly displaced. Heck, when Google began those investments (Android, Chrome, OS security, etc) they were crystal clear why they were making them--to nurture and grow an ecosystem into which they could grow their advertising business, same as their rationale for making a snappy search service and a non-intrusive advertising network. There's a limit to how well they can improve that ecosystem, but the limit for exploiting that ecosystem can easily result into a situation far worse than the one Google originally saved us all from. Consider why rendering work is even relevant in 2021. It's not for the benefit of services like Netflix or YouTube, which already enjoy low-power hardware acceleration, and arguably not for games or similar interactive content. It's so they can continue shifting their advertising ecosystem from minimalistic text-focused display boxes to animations and videos peppered up, down, over, and under content views. They can't do that if advertising-laden web pages drain your battery in 15 minutes, as notorious Flash-based ads once did. Steve Jobs' famously removed Flash from mobile; Google, for obvious reasons, is taking the alternative path.
- cblconfederate 5y agoThe only solution to that is if the browser starts absorbing more of the stuff that developers now use javascript for, like UI components etc.
- otabdeveloper4 5y agoI haven't had a faster processor in years. (Maybe decades?) (But they get more power efficient and quieter, this is true.)
- justshowpost 5y agoDistinguish _to be_ and _to become_. The latter is only possible if you _are not already_. Safari is efficient. Chrome becomes efficient. The latter is only possible if Chrome isn’t efficient currently.
- no1lives4ever 5y agoI still dont understand why people call chrome a memory hog and safari efficient. Try loading Outlook on the web or confluence and you will see that both Safari and Chrome eat up tons of RAM and cpu.
- jamienicol 5y agoPerhaps the blame lies with outlook and confluence then?
- ithrow 5y agoIn general safari is more efficient for me unless I opened gmail, then chrome is more efficient, gmail must have some kind of memory leak in safari.
- LooerCell 5y ago“improves battery life by up to 0.5%” To me this line is quite ridiculous. We all know that Chrome is now the main responsible for battery consumption on any laptop and could be optimized much more.
- marginalia_nu 5y agoI kinda want to see a standard deviation on those measurements.
- moritonal 5y agoGenuine question: In what kind of places?
- yunohn 5y agoAt the scale that Chrome operates, 0.5% energy reduction globally is massive. All these small gains also add for individual devices as well.
- eru 5y agoIt's massive in an absolute sense, so it makes sense to have a few people dedicated even to such small improvements. But it's still tiny in a relative sense.
- omnicognate 5y agoYou mean the total energy saved across all devices? The only context in which anybody could give a fig about that is as it relates to total global energy consumption, of which it is an utterly neglible speck. Edit: Had a go at putting some numbers on that for fun, and will partially retract my comment (no I don't, see below). If it takes [1] around 0.01kWh to charge a smartphone, there are [2] around 6 billion smartphones, each is charged once a day and this saves 0.05 (wrong,see below) of that usage, the saving is on the order of 3GWh/day, i.e. around 125MW. Total global energy consumption is [3] around 20 TW, so the saving is around 0.0006% of it, and this is a very generous estimate (chrome isn't all the consumption of a smartphone, not all phones are in active use and charging once a day, etc). That said, in absolute terms it's more than I would have guessed - comparable to the electricity consumption of a small town (no, much less, probably less than the output of a single wind turbine - see below). [1] https://www.quora.com/How-much-in-kwh-does-it-take-to-charge-a-typical-cell-phone https://www.quora.com/How-much-in-kwh-does-it-take-to-charge... [2] https://www.statista.com/statistics/330695/number-of-smartphone-users-worldwide/ https://www.statista.com/statistics/330695/number-of-smartph... [3] https://www.theworldcounts.com/stories/current_world_energy_consumption https://www.theworldcounts.com/stories/current_world_energy_... Edit 2: On reflection, I think this is an big overestimate. I suspect the real saving is on the order of a few MW. Edit 3: As the reply says, I missed a zero, which brings it down to probably on the order of a MW.
- ubercow13 5y agoDoes this close the gap to WebRender? It’s a bit light on technical details.
- ishitatsuyuki 5y agoI don't get how they could get a chart that is so hilariously bad into a technical post. No numbers & no tick labels. It only shows that newer = better, which is pretty much obvious from the title.
- frankenst1 5y agoRendering is fast on Chrome, however latency is high: Chrome has 1 to 2 frames (17ms to 33ms on a 60Hz display) of additional, unnecessary input lag when compared to Firefox: https://bugs.chromium.org/p/chromium/issues/detail?id=460919 https://bugs.chromium.org/p/chromium/issues/detail?id=460919
- phoboslab 5y agoThe linked vsync-tester[1] is very cool. But it's sad to see that (at least on my system) nothing has changed since 2012[2] - Firefox still misses frames; Chrome consistently lags an extra frame. [1] https://www.vsynctester.com/ https://www.vsynctester.com/ [2] https://phoboslab.org/log/2012/06/measuring-input-lag-in-browsers https://phoboslab.org/log/2012/06/measuring-input-lag-in-bro...
- frankenst1 5y agoYes, it seems like smooth scrolling is prioritized over low latency. On Windows I even get 3 frames (48ms) of lag (presumably because of DWM).
- jd3 5y agoI use a wired mouse with a 1000hz polling rate on an M1 Macbook Pro with vsync disabled system wide (through Additional Tools for Xcode 13.dmg[0] => Quartz Debug.app => Enable Vertical Sync; it only actually disables vsync if you use an external monitor and close the lid of the MacBook). Like switching to the Classic Theme from Aero in Windows 7[1], as far as I can tell, this removes at minimum 1-2 frames of input lag (typing, mouse movement, etc.) throughout all of macOS. In Firefox's about:config, after setting user_pref("accessibility.force_disabled", 1) user_pref("general.smoothScroll", false) user_pref("general.autoScroll", true) , I'm shocked by just how slow and laggy Chrome's builtin smooth scrolling implementation feels by comparison. In fact, it's so bad that I now open Chrome and all Electron apps with open -a Google\ Chrome --args --disable-smooth-scrolling --disable-gpu-vsync --disable-frame-rate-limit open -a Slack --args --disable-smooth-scrolling open -a Spotify --args --disable-smooth-scrolling You used to be able to disable Chrome's smooth scrolling with chrome://flags/#disable-smooth-scrolling, but that flag was removed for whatever reason. I'm also surprised by how much faster Firefox's builtin middle mouse click autoscroll is compared to Chrome's ersatz AutoScroll[2] extension. [0]: https://download.developer.apple.com/Developer_Tools/Additional_Tools_for_Xcode_13/Additional_Tools_for_Xcode_13.dmg https://download.developer.apple.com/Developer_Tools/Additio... [1]: https://pavelfatin.com/typometer/ https://pavelfatin.com/typometer/ [2]: https://chrome.google.com/webstore/detail/autoscroll/occjjkgifpmdgodlplnacmkejpdionan?hl=en https://chrome.google.com/webstore/detail/autoscroll/occjjkg...
- aidos 5y agoI, for one, would like to stand up and offer a digital salute to the people that worked on this. This announcement doesn't do justice to the amount of work that's gone into Chromium for RenderingNG.
- chrishtr 5y ago(I'm the author of this blog post and lead for a large area of the work described): thanks!
- jasode 5y ago>A great way Chrome can render content faster is to take advantage of the multi-core CPUs and advanced GPUs present in today’s devices. Multi-core means we can do multiple kinds of work in parallel. For example, Chrome parallelizes running JavaScript, scrolling a web page, decoding an image or video, I've noticed that Firefox is not as smooth as Chrome when playing 4k video. This has been an ongoing issue experienced by many for several years: https://www.google.com/search?q=firefox+4k+video+stutters https://www.google.com/search?q=firefox+4k+video+stutters I just re-tested this on the latest Firefox 93.0 and while it pegs an entire cpu, the playback performance is still jerky and unusable. And changing the oft-suggested setting of "gfx.webrender.all = true" still doesn't resolve it. I don't know what Chrome is doing differently but 4k playback just works with the default settings.
- jamienicol 5y agogfx.webrender.all no longer has any effect, as webrender is enabled everywhere by default (if supported by your hardware, which it probably is) It would be very helpful if you could capture a performance profile while playing the video, by going to profiler.firefox.com and following the instructions.
- jd3 5y agoOver the past ~10 years, I've come to the conclusion that it's best to just pipe high quality video streams into a cross-platform external video player like mpv[0][1][2]. I can't remember what Firefox uses internally to decode/display different video codecs (ffmpeg like mpv? system builtins? hardware media encode/decode, like on the M1?), but I've always found that, through yt-dlp[3]/ streamlink[4] integration, a native external video player like mpv is better able to support high quality video streams without constantly dropping frames or tanking the performance of the tab/browser. I can't put my finger on exactly why browser video streams feel so bad to me, but they do. Maybe it's the DOM overhead, or maybe it's something else. My personal takeaway is that browsers still just aren't optimized enough for fast/performant video playback. [0]: https://mpv.io/ https://mpv.io/ [1]: https://github.com/grmat/play-with https://github.com/grmat/play-with [2]: https://addons.mozilla.org/en-US/firefox/addon/play-with/ https://addons.mozilla.org/en-US/firefox/addon/play-with/ [3]: https://github.com/yt-dlp/yt-dlp https://github.com/yt-dlp/yt-dlp [4]: https://github.com/streamlink/streamlink https://github.com/streamlink/streamlink
- nikolay 5y agoI think Chrome's biggest problem is being a memory hog, but having a slow renderer!
- fouric 5y agoChromium seems consistently faster than Firefox to me, and I'm pretty sure that many other people have noticed this, too. The Chromium development team intentionally optimizes for speed (at the expense of higher memory usage) more than the Firefox team does - and, if you want, you know, long battery life, this seems ideal.
- nikolay 5y agoYet, nothing beats Safari on MacBooks!
- fouric 5y agoI'm pretty sure because Apple is doing full-stack optimization. I'm willing to bet you that Safari has a worse trade-off than Chromium or Firefox on non-Apple platforms.
- nikolay 5y agoBut we're talking about drastic differences in memory and CPU usage, not minor differences.
- fouric 5y agoHow does that have anything to do with my point? I said that Safari has an advantage over Chrome on Apple hardware only because it has an integration advantage. Chrome is still faster on most other platforms... including non-Google ones, like Windows and Linux - which the majority of users use. That is impressive. Meanwhile, there is nothing special about a browser that does best on hardware made by the same developer as it. Plus, both Firefox and Chrome have significantly more useful features than Safari on all platforms. Safari only wins when you care about pure performance on specifically Apple hardware without concern for features or add-ons. Not commendable.
- deleted 5y ago[deleted]
- user3939382 5y agoOn the topic of improving Chrome — can we get it to stop making 2-4 attempts to put its updater in macOS launchd every time it runs? What’s the purpose of that? Obviously non-technical users didn’t remove it. Seems obnoxious.
- jansan 5y agoIt is a nice long term approach, but right now there should be more focus on the issue with service workers running amok and consuming a major part of the CPU without doing anything useful. The problem was worse in the past, but it is still not full ysolved and if you think about the huge number of Chrome installations running worldwide, is a huge waste of energy. Here is one issue from the Chromium issue tracker if you are interested in details: https://bugs.chromium.org/p/chromium/issues/detail?id=1231683&q=service%20worker%20cpu&can=2 https://bugs.chromium.org/p/chromium/issues/detail?id=123168...
- southerntofu 5y ago> Chrome parallelizes running JavaScript So i'm personally a NoScript (Tor Browser) user, but every single time i've enabled JavaScript in the past years, i wished it was not multi-threaded. Most times, a random tab will start eating most of my CPU, and i wish i had just one process-per-tab to kill to own my computer again. On lower-end hardware especially, multi-threaded client-side scripting can make your entire computer unresponsive super quickly. I wish browser/website developers made UX testing on actual hardware (not everybody owns the latest Macbook Pro) before shipping stuff. EDIT: To the downvoters, why? Am i missing something? Is there an easy way to make JS engines respect my resources and to keep my computer responsive when browsing the "modern" web?
- fenomas 5y agoDoes anyone here know whether/how this should affect WebGL rendering? I'm developing a browser-based 3D game, and since a week or two ago I've noticed the rendering on mac/chrome is way slower than before. In fact my game now seems to be GPU-bound, where up to now it's always been CPU-bound. I think this started right around Chrome 94 shipped, but it's hard to downgrade and check. This is only on mac; PC performance doesn't seem to have changed. TFA makes it sound like whatever is new in v94 is only about page rendering, not WebGL, but does anyone know for sure?
- flohofwoe 5y agoI've also seen a somewhat recent performance degradation on MacOS+Chrome in WebGL when the WebGL canvas is close to fullscreen size, and even for extremely simple scenes (it's inconsistent though, maybe related to remaining battery life?). My guess is that this is some problem in the interfacing between Chrome and macOS, or purely in macOS though, because other platforms are fine.
- chrishtr 5y ago(I'm the author of this blog post) The launch in Chrome 94 does not affect WebGL. It's just for HTML/CSS content. If you can reproduce the issue and can share a URL that does so, please file a bug at crbug.com/new for us to investigate.
- chrishtr 5y ago"should not affect WebGL" is probably a better way to put it. (No software has no bugs or unintended consequences...)
- fenomas 5y agoHi, thanks for confirming! The issue reproduces in Chrome 94 but not current mac/Firefox, so I think it's new (though with now way to downgrade Chrome it's hard to be sure). Unfortunately I don't have a shareable URL that reproduces it, but if I can find one I'll file.
- maskros 5y agoRendering fast is nice, but when are they going to make the rendering look good? Image scaling at non-integer scales in Chrome is atrocious -- either coming out a blurry or aliased mess. I almost always need to zoom in 20% to 50% because web designers love tiny fonts too much, and setting a minimum font size breaks their fancy layouts. This results in Chrome making a mess of all images on the page. Thankfully Firefox resamples images so they look good at non-integer scaling factors too.
- jd3 5y agoThis is only tangentially related (images vs fonts), but a small pet peeve of mine that kept me from migrating to Chrome from Firefox on my Windows machine back in the day is the fact that Chrome uses an internal text antialiasing engine that is, as far as I can tell, impossible to disable. Firefox, on the other hand, honors the system antialiasing settings. So, for example, if you disable cleartype on Windows, you will have crisp aliased fonts at default font sizes on Firefox, but you will still get blurry antialiased fonts in Chrome no matter what.
- chrishtr 5y ago(blog post author here) Could you file a bug with an example at crbug.com/new?