Hacker News new | ask | show | jobs
by jasonkester 4908 days ago
This thing gets a lot of love by a bunch of folks here, so I gave it a good half year of trying. But it's just too annoying.

Around 5pm, your display turns pinkish orange and it becomes a lot harder to see anything. Code gets harder to read, colors display wrong, video just fades to black. None of the advertised happiness ensues.

The second half-year it remained installed, my only interaction with it was to notice it screw up my display, then right-click the tray icon and disable it.

Needless to say, I didn't install it on the new box I bought this year. I don't understand why people like it.

22 comments

Whenever Flux gets mentioned, there's two groups of people:

1: Doesn't understand it, hates the "wrong" colors. Can't get used to it.

2: Appreciates the candle-like colors, says it helps them sleep in the evening or relaxes their eyes.

I wonder if there's some sort of genetic difference? Maybe some people just aren't sensitive to bright light in the evening?

I'm not sure it's a genetic difference. I used to be in camp 1, despite trying Flux many times, but now I'm firmly in camp 2. The change for me was due to a change in working environment, and I imagine that's the difference for a lot of people: if you're in a brightly lit room anyway, then the colours becoming weird is just going to be irritating. If you're in a room with a lot of natural lighting, or trying to work on a plane or a bus, it might be different. Of course, either way, it's not suitable if you're doing colour-sensitive work or if you just want to watch a movie, but for reading or text-editing there's no real downside other than taste.

I think I speak for a lot of Flux users when I say that the point you really notice is when you're working late at night, and you turn off Flux after your eyes have acclimatised and all of a sudden you feel like you're in a tanning booth.

I have f.lux on my [jailbroken] iPhone 4S and my desktop.

On the desktop I like it simply because it helps automatically "dim" my display in the evening. I don't use much artificial light in my room [it's basically a mancave after 5:00] so a bright display with the standard color temperature is just an exercise in eye-strain.

I can't be bothered to adjust my brightness, contrast, and temperature manually every evening to avoid eyestrain. Since my monitor doesn't have programmable presets, f.lux definitely provides a great [automatic] solution.

On my iPhone it's actually more of an issue, I find myself disabling it frequently. I think this is mostly because I use my phone in a wide range of "lighting contexts." I might walk from the man-cave to a fluorescent-lit kitchen, and then I'll go out into an incandescent living room.

In my car, I find the low color temperature kind of difficult to read, so I'll usually disable it for road journeys. (It probably doesn't help that I have a dark OS theme and my navigation application has a dark blue "night time" mode that is also time activated.)

f.lux does look wrong in a blue-rich lighting environment (like an office building after dark.) It looks ok in most people's homes.
You should set f.lux to match your ambient lighting. If the whites on your screen look more orange than the whites in your room, then you have it set too warm (no benefit from that anyway!).
Might there be a way to sample white balance throughout the day to calibrate it using a webcam and a white sheet of paper? I'd probably start using it again if I could avoid fine tuning color temperatures manually.
Yes we have three implementations of this, and they mostly work but only some of the time :)

Problems: in a lot of dim rooms, the monitor is the main light source, and some webcams have terrible auto white balance. If you're on a Logitech camera it's totally easy, and if you're on a cheap netbook, it's awful. Still, you can solve all that, and we probably will ship a version of this soon.

That's great to know. I could probably turn the screen backlight off for a second while taking the shot. I'll play around with some shots from my camera to see how they vary. I'm looking forward to hearing more about these sorts of features!
That doesn't surprise me. If you're in such an environment, I'd bet that the ambient light would overwhelm the benefits of a tinted display, anyway.
I can attest to this. It's exactly why I don't use it on my work laptop but can't live without f.lux at home.

Granted, I use and like warm lighting at home. I wonder what would be the effect in a house/room that uses daylight lighting.

You should check out Hacker Vision as see what you think: https://chrome.google.com/webstore/detail/hacker-vision/fomm...
I would take this a step further and say it happens when any project or software gets mentioned on HN. There are always two groups of people: Those who like it, and those who don't. Those who don't are usually composed of a lot of people who don't actually care, but just thrive on contradicting people.

I'd say it's more of a personality phenomenon, but acknowledge the possibility you present as well.

Part of the problem is the people who like it insist that everybody must like it and anybody who doesn't like it just doesn't get it. I don't get upset when people talk about things that made their lives better, I get upset when they make unqualified statements about my life.
And the majority of people aren't motivated enough either way to comment, so we listen to the vocal minority with extreme views. Like everywhere in life.
And those who do are often composed of people who just like to be excited by new things that seem cool. Or we could describe both populations in a more positive light.
Theoretically, we might only recognize about half of those contradictors at any one time.

If these theoretical contradictors are evenly distributed, spherical, and massless, then it seems natural that around 50% will be busy contradicting other contradictors, and writing well thought out and earnest posts about how great the software is.

One can only hope that they all get sent out into a vacuum.

I wonder if the two groups are

1. the ones who discovered the "Slow" setting in preferences, and

2. the ones who didn't.

When the transition is set to Fast, I find it very jarring. When it's set to slow, I barely notice it.

It probably doesn't help that it has bugs. Sometimes my netbook will go through a horrifically jarring transition full of banding and a very obvious change in tone, it seems like sometimes flux gets a little stuck and then rapidly catches up.

Flux on my MBP is if anything even less predictable.

I also found when moving to my netbook to my MBP that I had to make very big changes to how much flux could change the colours - I have no idea what makes my previous settings so annoying on this computer, there's too many diferences between them to be sure.

On my MBP I completely ignore their recommended settings for lighting type. I picked the tone by adjusting the settings until it didn't feel like the light from my screen was physically attacking my eyes, which required a surprisingly small change in colour.

I don't think it's the slow setting. I tried it for a few months, and I did use the slow setting, but just found the washed out colors annoying. Regardless of the lighting in the room. I even tried forcing myself to keep it on for a couple of weeks straight, figuring I'd get used to it. No dice. It was usable enough, I just missed the colors and didn't really notice any difference as far as eyestrain.
So you're proposing that everyone should like it?
Speaking of genetic differences, you see this same sort of split whenever "what music do you listen to while coding?" gets discussed here. Half the folks suggest music that makes them more productive. The other half say that any music at all distracts them to the point that they can't get anything done.

For anybody looking to correlate the two, I wrote the above and fall squarely into the "no music" camp as well.

Maybe we're just overly sensitive to any intrusion on our concentration. (I also prefer nobody throw hamburgers at me while coding, so there's a 3rd datapoint.)

I'm not sure there is much correlation between the two, at least in my case.

I fall squarely into the "no music" camp, and have since I was a child where music during study would drive me crazy. Music while coding is just a distraction to me.

However, I really love F.lux/Redshift. One of the most relaxing and productive things for me is to work in a dim or dark room with the display shifted to a fairly low color temp. By contrast, during the day I prefer fairly high contrast, using the VividChalk theme in Vim. In the past I would switch to a lower contrast theme like OceanDeep, but never found one to work well with red hues yet, which I prefer in dim light (partially as a throwback to old amber monitors.)

As a side note, I will agree with everyone saying the automated time based shifts are annoying. I usually find myself pausing or disabling it. Having it triggered off ambient light levels is the logical way, imho.

I also prefer nobody throw hambmurgers at me while coding, but if they want to toss them onto the corner of my desk for later consumption, I won't complain...

For people who light affects their sleep fall generally fall into two camps: those that are oversensitive to light, and those that are undersensitive to light. For the former, (as an extreme example) a flashlight might prevent them from feeling tired (since their body feels like it's day time); whereas for the later, you can shine a tungsten movie light on them and they won't wake up (I think I'm the later---I can easily sleep during the day).
Half the people in my office leave their laptop display at about 50% brightness all day. It drives me crazy -- I always want to go over and turn it all the way up. I like my monitors BRIGHT, but others say it bothers their eyes. You might be right...
That's kind of funny. I personally can have real issues with bright displays. Only in very light sun lit offices, I don't mind the brightness being up. When at home in the bat cave, I far prefer dimmer light. Some days my eyes are more sensitive, or perhaps getting used to dimmer displays make you more sensitive to bright ones.

I used to use the transparant filter with compiz, just to take the edge of some glare/brightness. I even tried a sepia/monochrome filter with some success. There was an error with compiz and my system, so had to give up on it.

Then I tried a light on dark theme. As I find the terminal comfortable, but I feel you need to match it across your desktop - otherwise it's jarring. That is going from light on dark to dark on light.

It seems support for darker themes is buggy at best on Linux. To the point that recently I had to undo my dark theming just because I need regular access to one spreadsheet.

Now I have a halfway house, browser is setup for light on dark, and the rest of my desktop is greyish. Still buggy though, something as simple as Google's search box is unuasable because I've a dark font on a dark background. And so it goes on.

I might give flux a go. I've installed redshift on XFCE - but it's not currently working. Edit: okay it took like 2mins to get it up and running. Not sure what to make of it. Will see.

I've got quite used to a light on dark them though to overcome brightness issues.

I've also found that having both a light and dark color theme is useful for your editor. I am currently using Solarized in Sublime Text.

It seems to work well, and if you read the description, it seems like a lot of effort has gone into matching the two versions.

http://ethanschoonover.com/solarized

Run redshift in a terminal to see what it is doing.
> 1: Doesn't understand it

That's a condescending interpretation. Just because someone doesn't like something doesn't mean that they don't understand it.

I think the people in group 1 didn't set F.lux up correctly. Twenty seconds is too short of a transition time.

If the same people are complaining about paper and other objects having the "wrong" colours at night, you might be onto something. I think that's highly unlikely though and I see little reason to seek a genetic explanation.

I wonder if there are also geographic differences at play? I love it during summer in Germany (= bright until ~10PM) but it annoys me when it turns dark at 4PM, while I am still at work.
I live in London and I have my location set to Recife, Brazil. That way I get 'sunset' around 9pm in the winter - late enough to let me continue working on a bright screen, but early enough to not blast blue light before going to bed.

The point for me is not so much matching the environment but not staring at a blue screen right before bed.

I find the same thing from Canada. Perhaps I'll try telling it I'm at a more equatorial location.
Seems like a simple fix to make it latitude-aware, if it's not already.
I'm definitely in the latter camp, though my working day starts at 6:00 AM and the softer, warmer light in the early (still dark) morning is much nicer than the harsh blue of a normal display. Interestingly, by the time the screen colour adjusts back to normal (variable based on time of year), I'm happy to see it adjust as well. Best of both worlds, as it were.
I've simply never been able to get used to the colours. When I bought my last MacBook I noticed that the brightness at even the lowest level is far too bright for usage just before bed. I ended up buying a 99c app on the MAS called Screen Shade that pretty much just overlays a transparent black over your entire screen. The first night I used it I thought 'well, this was pretty crap' but I've used it pretty much daily since. At night I slowly turn the brightness down and eventually switch screen shade on and adjust down as my eyes get used to it. It works amazingly well and skips the colour part. I realise that flux is probably better for my eyes, but I've never found myself in the habit of using it, whereas Screen Shade made it's way onto the new MacBook almost instantly.
Bordering on group 2 I can't say if it helps or not because I've never had any problems with my eyes. But I have not experienced any hate-issues towards it so I have left it installed on all my computers just in case.
It turns reddish gradually, so I don't really notice it. If I disable it at night, the sudden blueness hurts for a second, which implies there's some benefit to being redder.
In some WWII submarines, the sleeping room lined with bunks for the bulk of the staff, the lighting is red. Why? Because you can sleep in it easily -- it's always just red in that room because there are some day and night shifts even on a sub.
The story that I heard (from my army dad) about red lights for night work was that red lights cause less night blindness than white lights.

Wikipedia corroborates this story, but indicates that a Navy study (from the 1980's) didn't find strong support for the practice.

I've tried it once for a short while and sided with camp #1.

Going to try it out again, "forcefully", for a longer while to see how it works out.

I had to make the night time colors much cooler for me to be able to tolerate it. I felt like the default was far too red.
3: Hates how f.lux makes the display jumpy and slow when active. (Sorry, it's true, and once you see it, you won't be able to unsee it)
>I wonder if there's some sort of genetic difference? Maybe some people just aren't sensitive to bright light in the evening?

No, it's probably people not noticing that they have a problem and insisting that they don't. Happens all the time.

Maybe some things just aren't for everyone?
Things that depend on common human physiology rarely have exceptions...
(author of f.lux here) Color adaptation actually takes about 2 minutes, and we transition by default in 20 seconds (some video cards use a ton of CPU during the transition time, so we pushed it a bit faster.) The slow transition option should help some people.

Also a badly-calibrated monitor can give a very undesirable result color-wise, but a white page should look like your room lighting if we do things right.

Is the Android version still on your todo list? I was thinking about making something like f.lux for Android.
I love f.lux, thank you. It's on my Mac and on my iPad. It'd be on my iPhone too if I could jailbreak the thing yet.

Oh and here is a bug that's been niggling at me. If you have your laptop plugged into an external display after the evening light kicks in, then unplug the laptop, it's in screaming bright normal colors on its own screen until you quit and restart f.lux. Same if you plug in the external screen in the evening.

> a white page should look like your room lighting if we do things right.

as someone in the "those colors look weird" camp, this might convince me to give it a try. it implies that those i've seen using it have it set up wrong.

I wish there was something in between 20s and 60m. When I'm doing image editing, I don't want f.lux messing with colors, but I might not notice if I have it on 60m.... 2m would be better for me than 20s.
There's a button that completely disables it for color sensitive work. That's the best option.
I only see "Disable for one hour."
I used to have the same issue as you.

F.lux emulates an undergoing sun. That doesn't happen in 20 seconds. Set the transition time to Slow.

Also select the right type of lighting. If none of the types match your lighting, juggle a bit with the settings until your screen looks the same way a piece of paper would look in the same lighting.

If you do that, you won't notice it's running at all. The only reason I turn it off is when I'm watching a movie. The colours in a movie usually already take darkness in account.

I wish there were some way for it to detect the ambient light of the room I'm in. Late at night I prefer the warmest setting. But I feel like I'm constantly adjusting f.lux based on where I am. If I'm out, I can't control the lighting of the room. At home in the winter when it gets dark early, I don't want to turn the lights off at 5pm. But if I don't adjust f.lux, it hurts my eyes.

For the most part, though, I think it's great.

My grandfather had an ancient color TV with this feature. You could press a toggle button on the front that would open or close an iris over a sensor, and the TV would adjust the on-screen color to match the room lighting.
As long as it can be set by command line or has a simple config file it shouldn't be that hard to set up a daemon to take a picture with a webcam then munge the color temp and brightness and adjust f.lux accordingly.
It would be neat if it could auto-calibrate based on a reference image of what you look like sitting in front of your webcam.
My main issue with f.lux (and the reason I don't use it) is that you can't configure it to wait until a certain time to start with the transition. When I go to bed at 11 pm, I would like f.lux to start its one hour transition at 9 pm so that I don't see that much cold light the last two hours before sleep. And in the morning it should start directly with the settings for the day, without any transition.

Tying it to sunrise/sunset is what makes it useless. In winter it starts the transition at 4 pm while I'm still working. The amount of daylight I get in winter is already low enough, using f.lux would make the winter depression even worse. I could of course trick it by settings the location to place in the Southern hemisphere, but that won't help me during spring and fall...

More improvements in this area are coming. There are interesting trade-offs between productivity and good sleep, and our next version strikes a better balance.
I didn't set it to be in the Southern Hemisphere but just moved it further West. I never notice the transition from warm-to-cold anyway (not an early riser) and it delayed the cold-to-warm transition by 2 hours.
Unfortunately then I would have to disable f.lux every time in the morning because otherwise it wouldn't transition back until noon.
Similar issue here. I love it but it starts too early and clicking the "turn off for a hour" setting all the time was just a pain. I like that it initially tries to auto-tune itself, but I'd enjoy it even more if it had a customizable schedule.

And this might defeat the purpose, but if I could configure it to know what Spaces it was in in OS X, I could still design and not have to turn it off manually for just that one Space with the browser window in it, where knowing the actual colors is important.

Pick a location on the equator, and offset it to your preferred schedule instead of your actual sunrise/sunset time.
The right way to use it is to NOT use the default settings.

For me is: days, all the way to the right (bluish) and nights, about one third to the left (just a little reddish).

Also, make the transition last one hour (20 seconds is insane).

Also, I think it looks great only on HDMI, and ugly on VGA.

Well that's the thing, you need to adjust, not disable it. I found out that the slow transition over an hour is essential, otherwise it's too disturbing. It didn't work on linux for some reason though. I haven't had any trouble while coding with it, or see anything well enough. When you do some work where you need to see colors properly then it's not usable of course. But it's fine for late night reading.
Yeah, when I saw this post I doublechecked if I even had it installed. Yep. Installed and active. But with the super slow transition I'd only really see it if I turned it off.
You say around 5pm the display turns orange, are you seeing an instant change? Try the slow option that changes the colour over a longer period so you don't even notice it happening.
Did you play around with the lighting setting? I have it set for halogen and set the transition to slow (1 hour) and I don't even notice it.
I've only just installed it, and found that I need to disable it if I'm doing any serious work. However if I have some free time at night to go over pinned tabs or read some articles I leave it on and find I do get sleepier much faster, to the detriment of my open-tab count.
Is serious work == Photoshop or does it bother you when programming too? I only tolerate f.lux when programming, but it happens to be what I do every night :)
I can program for 30 minutes with it, but I get tired :) so if I am troubleshooting a problem that is going to take a while or a client indicates it is urgent, f.lux goes off.
Do you have flux set to slowly modify the white balance? If it changes over the course of an hour, then I find it's pretty difficult to notice the change.

Videos shouldn't be black though. Flux does have different white balance targets, have you tried selecting a different one?

I actually would get used to the new temperature, but working with Lightroom a lot, it became a hassle to have to constantly disable it.

Also watching videos/flickring etc needed it to be disabled to get the right colors on screen.

I highly recommend using the 1 hour transition time instead of the instant one. It feels much more natural as your screen essentially dims as the sun sets. I've found that it's quite pleasant on the eyes.
I love f.lux, I just wish it was adjustable for that exact reason. It is winter, it gets dark out early... I don't want it to shift to night time mode at 5pm. I find myself hitting "disable for an hour" 1-2 times a day before I leave work.

However, when I get home and get back on my system, then I'm ready for night time mode.

I prefer the 20 second switch over so I know to turn it off fast. With the long transition, I find myself being annoyed for a while until its enough for realize I need to turn it off.

I'd love a simple "activate at sunset, but not before X:XX".

Maybe set it it for a time zone a couple hours behind your location?
....I feel you're having trouble configuring the app.
I wrote a similar app called Brightness that lets you manually control display tint and brightness, instead of relying on a timed mechanism. Myself, and many other designers and developers, find it very useful.

https://itunes.apple.com/us/app/brightness-dimmer-tint-contr...

Part of it is having to change the color schemes you code in to pay nice with the tints applied to the screen.

You can also change the color of the tint based on the type of lighting you have in your room (halogen, tungsten, fluorescent, etc) which makes a difference.

Still, it just might not be for you :)

I have my lighting at night set to "fluorescent" and use the slow transition. I don't generally notice it turning on, and I use the "disable for an hour" setting if I'm doing anything where I need more color accuracy.
Yes, same here. Default 3400K is very uncomfortable on my eyes. 4300K fluorescent is bearable, but still annoying. I much prefer to change brightness if I need to ambiently adjust the screen.
I think it's because of the transition happening too quickly. If the transition took an hour, it would be great :).

edit: You CAN make it take an hour! Just installed again!

If you just set it to fade in over an hour, instead of instantly, you wont even notice it. That's how I do it.
for some reason it would continuously flick between on and off, even when i had it disabled, so i just gave up on it too
>Around 5pm, your display turns pinkish orange and it becomes a lot harder to see anything. Code gets harder to read, colors display wrong, video just fades to black. None of the advertised happiness ensues.

You know that you can tune the white balance to your preference in the program, right?