I go out of my way to find components that don’t have RGB lighting on them. When I use my computer, I want to be looking at the screens (the two-monitor part is true,) not the case.
I’ve got a piece of black tape over the power line on my computer, because it is too bright. And I have masking tape over the caps/num/scroll-lock lights on my keyboard; because they are also too bright. (The light is much gentler through the masking tape.)
Red is for performance. Green energy saving. Blue is not important for this argument.
And if it goes 16 bazzilion colors it is even more BS and nothing.
Goes magenta and you start going Bi. Next on? Pink - full gay mode. And as soon as you go white - back to straight again.
It might cause brain damage in the long term. Wear your socks guys.
Installing the 95/98 GTK theme by B00merang is one of the first things I do after a fresh installation of Linux Mint.
I do try other themes once in a blue moon. But I soon realise it is a downgrade and revert back. The last theme I tried was the Arc theme back in mid-late 2010s.
My biggest hurtle is why i can’t see files as thumbnails when picking a file to open or save. It works for file library but the file picker won’t show images as thumbnails. Only a list view with tiny thumbnails that sra too small to see the actual image
I would have stern words with John Riccitiello the ex Unity CEO who really neglected the core of their business for the years he was there. He was fired not too long ago. Games from scratch covered the conclusion of that train wreck. The new CEO seems to get that they need to refocus on the engine and making it better for developers versus chasing money. youtu.be/woTLLrgywwE?si=BIXTJGGMjpjv72vO
True but so do most computers. Computers have a database of timezones and time offsets around the world. Depending on the UTC date and time, and your current timezone it will look up what offset to apply to show the local time. The database is very gnarly since rules change over time, e.g. maybe in the 70s some countries had longer DST to counteract oil shortages.
The only code with timezones should be the bit squishy meat bags touch. Everything’s is should be UNIX time. Or it you are unfortunate enough to be on Windows, NT time.
Some unfortunate programmers already have to deal with the speed of time not being a constant. In a distant future, timestamps might always have a universal position (and speed), and is that much different from timezones?
Or we find some way of removing time distortion of physics. Find the universe’s real systick. 😃
I once developed an electronic program guide for a cable TV company in New Zealand and I’d lose my mind if I had to use timezones. The basic rule of thumb was:
a) Internally you use UTC religiously. UTC is the same everywhere on Earth, time always goes forward, most languages have classes that represent instants, durations etc. In addition you make damned sure your server time is correct and UTC.
b) You only deal with timezones when presenting something to a user or taking input from a user
Prior to that I had worked for a US trading company that set all their servers to EST and was receiving trades through the system which expressed time & date ambiguously. Just had to assume everywhere that EST was the default but it was just dumb programming and I bet to this day every piece of code they develop has time bugs.
Yep, case in point flipping between EST and EDT may be “insane” but that’s the default for systemd-timesyncd. So now you have to be 100% certain that it’s disabled on your servers, and on the remote hosts interacting with them.
Best I’ve seen is a process scheduled on UK local time (including hour changes) running on a server that maintains Eastern local (including hour changes) but the process logs in EST ( and does not move with the hour)
UTC always goes forward regardless of the timezone and local time. That is why you should use it. To take my EPG situation above, I stored program start / end times in UTC so they would render properly even if DST kicked in or not during the middle of the program.
Leap seconds still make time go forwards, not backwards. NTP clients would also resolve small time discrepancies while still advancing forwards prior to the next time sync.
Leap seconds can make time go both ways, but adding them makes time stop/go back because 24:00:00 cannot be represented as 1/86400 part of day N instead of day N+1 on major OSes. And they were only added so far.
It doesn’t work like that. UTC goes forward always. Leap seconds are scheduled and known in advance. NTP time services will just smear time advancement a little to account for an additional second. Time never has to go backwards. This is how Google does it.
It’s just for AI training. Opensource AI = good and allowed, commercial, closed source AI = bad.
I could look into poisoning their training set, but am too lazy atm. Maybe another time. Spoilers might come in handy for that. Maybe a spoiler like below would come in handy for now?
My case has RGB fans. Not because I wanted them, but because I wanted a PC between Covid lockdowns, had to pick from a small selection and RGB fans cost less than regular ones.
Flashing RGB light are legit the most annoying shit ever. I just have a black box for a case and my peripherals glow a dim solid color (so I can see them in the dark) if at all.
I largely mean flashing in general, it’s all just distracting to me. Also most people I know personally actually like the rainbow madness. Even if they try to match their keyboard and mouse, they’ll still often have a unicorn box. They also love putting their rainbow tower on top of the table, I really don’t get it. A friend’s uncle even has a case the height of a table, like bro… Is there no end to this?
I used to have a cheap mechanical keyboard that has side rainbow RGB panels that can’t be turned off. I thought that would be turned off when I turn off the backlight. Nope.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.