Light mode is the best and I think a significant number of people who oppose it are students or hobbyists who only program outside of typical work hours. During work hours, I want bright light to keep me alert. And I work in a well lit office and home mostly during the time of day when there's lots of sunlight. Dark mode just doesn't make sense for professionals.
Plus, if even a single documentation site or Google search uses a light theme (and many do, especially by default), you risk blinding yourself with the sudden flash to light. By comparison, if I'm using light mode and something else is in dark mode, it doesn't hurt me at all.
You can use Dark Reader for those sites. But I do get where you're coming from.
I'm not in an IDE all day every day, but there are dashboards that I keep in light mode to subconsciously signal to myself to be extra careful in. It's like how some Linux admins set their production shells to bright red.
Dark mode just doesn't make sense for professionals.
Come on.
I use a dark, low contrast theme and work in a nearly unlit room with my monitors on nearly minimum brightness. It's comfortable and totally efficient. I understand wanting to switch to bright mode and use higher contrast when reading unfamiliar material, but code is not that. It is highly structured, repetitive (syntactically) and organized. So you can usually have a clear idea of what you're looking at without relying much on visual details.
you risk blinding yourself with the sudden flash to light
Only if your monitors are way, way too bright for your environment.
Joke's on you, first thing I do is closing the blinders in my office, when I come in to work.
But really, I just prefer dark themes. I can and will totally work with bright themes, if the GUI supports it, but if I have the choice, I chose dark themes wherever possible (e. g. Not for applications in bright sunlight). And yes, I work during daylight hours...
Light mode is the best and I think a significant number of people who oppose it are students or hobbyists who only program outside of typical work hours. During work hours, I want bright light to keep me alert. And I work in a well lit office and home mostly during the time of day when there's lots of sunlight. Dark mode just doesn't make sense for professionals.
Plus, if even a single documentation site or Google search uses a light theme (and many do, especially by default), you risk blinding yourself with the sudden flash to light. By comparison, if I'm using light mode and something else is in dark mode, it doesn't hurt me at all.
You can use Dark Reader for those sites. But I do get where you're coming from.
I'm not in an IDE all day every day, but there are dashboards that I keep in light mode to subconsciously signal to myself to be extra careful in. It's like how some Linux admins set their production shells to bright red.
I don't care what you prefer. But:
Come on.
I use a dark, low contrast theme and work in a nearly unlit room with my monitors on nearly minimum brightness. It's comfortable and totally efficient. I understand wanting to switch to bright mode and use higher contrast when reading unfamiliar material, but code is not that. It is highly structured, repetitive (syntactically) and organized. So you can usually have a clear idea of what you're looking at without relying much on visual details.
Only if your monitors are way, way too bright for your environment.
Joke's on you, first thing I do is closing the blinders in my office, when I come in to work.
But really, I just prefer dark themes. I can and will totally work with bright themes, if the GUI supports it, but if I have the choice, I chose dark themes wherever possible (e. g. Not for applications in bright sunlight). And yes, I work during daylight hours...
What, you don't skateboard down the hallway to the server room?