Joined October 2013
·
Posted to
Adding Console2/ConsoleZ to folder context menus
over 1 year
ago
I've updated the comment with snippets above.
Posted to
Adding Console2/ConsoleZ to folder context menus
over 1 year
ago
The setup is ConsoleZ wrapping Git Bash, which is in turn reading my .bashrc (located in user directory) with settings on how should the prompt look like.
- Font: Source Code Pro Medium
- My bash prompt: http://snippi.com/s/hiycvq4
- My ConsoleZ color map: http://snippi.com/s/ctbxtmq
Achievements
205 Karma
6,308 Total ProTip Views
Charity
Fork and commit to someone's open source project in need
Altruist
Increase developer well-being by sharing at least 20 open source projects
Honey Badger 3
Have at least three Node.js specific repos
Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Lemmings 100
Write something great enough to have at least 100 watchers of the project
Kilo of Lemmings
Establish a space in the open source hall of fame by getting at least 1000 devs to watch a project
Forked 100
Have a seriously badass project that's been forked at least 100 times
Forked 50
Have a project with a thriving community of users that's been forked at least 50 times
Forked 20
Have an established project that's been forked at least 20 times
Forked
Have a project valued enough to be forked by someone else
Cub
Have at least one original jQuery or Prototype open source repo
Honey Badger
Have at least one original Node.js-specific repo
That's incorrect. Every time something visual changes there has to be a repaint. That's how you can see those changes - the bitmap you are looking at has to be modified, i.e. repainted.
What you are observing is that when you use opacity that is between 0 or 1, you introduce an alpha channel to the element. Chrome will try to optimize this by compositing this element on GPU. The GPU composited layers show up when the "Show composited layer borders" is enabled, but not in "Show paint rectangles", as latter is showing only stuff that is rendered by CPU.
Overall, using non floating opacity is definitely faster.
When elements has a 0 opacity, Chrome can just ignore it when painting. When it is 1, it will just paint. but when it's a floating point, it has to also paint what is behind the element, than composit it on GPU, apply alpha channel, and overlay it. That is a lot more costly than just "ignore" or "paint".
You are doing yourself a disservice and lowering the performance of your site by using floating opacity values when they are not needed.