Why write code when you can turn the transistors on and off yourself? I have a few thousand buttons connected to the CPU, and some homies and I open or close them on each clock cycle to feed it different instructions and inputs.
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...
I know it's been around for a long time now and offers some features that people like but I'm completely content with the simplicity that notepad provides.
I spent 45 mins with ChatGPT trying to give me the quick resolve for something querying with M.
It ended with me telling ChatGPT that if it worked for me, it would be fired because it kept trying to reoptimise my query, resulting in syntax and load errors, then "fixing" them by ignoring my query's criteria.
I ended up going old school and taking an extra 30 mins to just figure it out myself. Now that I know how it's done, it's surprisingly easy to understand.
So I took that as a compliment; or ChatGPT just sucks at PowerQuery.
It probably learned, though. If anyone has transform queries around multi-level filtering criteria and ChatGPT helps, that's because of my suffering.
It will eventually incorporate user inputs in the model. So yes it won't learn in real time from other users, but at some point those inputs will be fed back into itself.
In each session, the last several thousand words (from the user and AI) are kept in a context buffer to be used as additional inputs for the neural network. But I don't think ChatGPT lets you choose the AI's responses for that buffer, so you can't really "train" it in any sense of the word. If you want that functionality, use LLaMa.