Even though I really appreciate the idea behind it, I was never all that comfortable running f.lux on my Macbook. I never understood why it was free yet closed-source. It made me suspicious in a way, if that makes sense.
After a while I just gave up and uninstalled f.lux. Instead, I created a 4500K white point copy of the default color profile and manually switched to it at night, which seemed to have the same effect. It also prevented those big flashes whenever switching to and from full-screen apps.
I'm grateful that f.lux has pushed this issue to the point of getting traction as a built-in feature from Apple (and I do hope Apple brings it to OS X at some point), however unless f.lux becomes open-source, I don't plan to reinstall it.
You support (via hardware purchases) a powerful company that demonstrates overt hostility towards openness whenever it suits them, but won't use close source f.lux?
>I never understood why it was free yet closed-source. It made me suspicious in a way, if that makes sense.
Unless binary builds are verified against the source code (or the code is reviewed and compiled locally), security is not a criteria that's benefited. The gitian process in bitcoin is an interesting solution on how to verify builds.
After a while I just gave up and uninstalled f.lux. Instead, I created a 4500K white point copy of the default color profile and manually switched to it at night, which seemed to have the same effect. It also prevented those big flashes whenever switching to and from full-screen apps.
I'm grateful that f.lux has pushed this issue to the point of getting traction as a built-in feature from Apple (and I do hope Apple brings it to OS X at some point), however unless f.lux becomes open-source, I don't plan to reinstall it.