Live data from Hacker News

Infinite loop in macOS Night Shift in the summer near the Arctic Circle

twitter.com

141–150 of 175 posts

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#141
post #78

Earlier quoted context omitted.

Because there is neither a 12:00 am, nor a 12:00 pm. One is 12 noon, the other is 12 midnight. AM and PM are "ante meridian" and "post meridian": before" and after . But 12 is on* the meridian; neither one. You can meaningfully say 12:00:01 am, or 11:59:59 pm, but for 12 sharp nobody can say whether am or pm is dark or day. Airlines schedule flights at 12:01 for this reason.

Meridian in this context is noon. 12 “anti meridian” is 12 hours before noon. 12am. Which is exactly correct. I’m no domain expert but I’m guessing flights are scheduled at 12:01am because people are bad at time. For instance some people would think 12am is the last minute of the previous day instead of the first minute of the next day. 12:01 removes the potential ambiguity.

You've just completed GP's point perfectly though - 12 hours after noon (post meridian) is midnight too.

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#142
post #25

Earlier quoted context omitted.

Not really. All he's shown is a behavior (high CPU) and is equating it with the latitude he's at. When he turns off Night Shift, the daemon process for the feature stops consuming as much CPU, from what I gathered. Nowhere does he provide evidence that there is an infinite loop calculating the sunrise/sunset. And I really don't want to be a stereotypical poster by simply degrading what he did, so I will give credit t…

You’re splitting hairs and failing at it. They have clearly found a “bug” if Night Shift is consuming 100% CPU without end, even if their hypothesis for the reason might be wrong.

>They have clearly found a “bug”...

This depends on your definition of "bug". I think, in the classical sense, a bug is something that you understand both the cause and the resultant undesired behaviour and, as of consequence, you can reproduce the chain of events.

Given that definition, I would be disinclined to agree with calling it a "bug".

However, I would also like to point out that we're getting so nuanced in terms that we're, quite literally, dropping the notion of lauding the attempts of the OP to go down the road of wanting to deduce the problem, themselves.

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#143
post #56

Deep in the twitter replies: > Now, is this a corner case, an edge case or a boundary case? And does the answer depend on whether you are a flat-earther or not? That was too funny.

Personally I believe that earth is flat disk carried by 4 elephants, which are standing on the back of a giant turtle

The Turtle Moves

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#145
post #139

Earlier quoted context omitted.

Personally I believe that earth is flat disk carried by 4 elephants, which are standing on the back of a giant turtle

You’re wrong. I know for a fact that there are 7 elephants, one of them is white.

One for each continental plate? Adding explenation power and prediction to flat earth science. Its good science, if it can be used to predict and test against ;)

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#146
post #56

Deep in the twitter replies: > Now, is this a corner case, an edge case or a boundary case? And does the answer depend on whether you are a flat-earther or not? That was too funny.

Personally I believe that earth is flat disk carried by 4 elephants, which are standing on the back of a giant turtle

Wouldn't we have eight seasons then?

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#147
post #135

Earlier quoted context omitted.

I wonder how long time it will take to forget DST if it is abolished. Will that messy spaghetti code be ripped out and never seen again.

Most standard libraries still have support for the Julian calendar. That stuff is never going away.

I doubt it's "most". Python, Javascript, and C++ don't seem to. The only ones I found that do seem to are C# and Java.

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#148
post #78

Earlier quoted context omitted.

Falsehood #2: Every day starts at 12:00 am midnight.

Because there is neither a 12:00 am, nor a 12:00 pm. One is 12 noon, the other is 12 midnight. AM and PM are "ante meridian" and "post meridian": before" and after . But 12 is on* the meridian; neither one. You can meaningfully say 12:00:01 am, or 11:59:59 pm, but for 12 sharp nobody can say whether am or pm is dark or day. Airlines schedule flights at 12:01 for this reason.

This is the reason 24hour clock is the way to go. 23:59, 00:00, 00:01, ...

0 was invented for a reason. This am/pm stuff is so confusing.

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#149
post #73

reminds of the Computerphile Tom Scott video "The Problem with Time & Timezones" https://www.youtube.com/watch?v=-5wpm-gesOY and why I will never implement datetime myself

Nobody ever got fired for using the provided datetime.

What is the standard for using datetime libraries?

Use the one that comes with each language, or use some UTC library?

Re: Infinite loop in macOS Night Shift in the summer near the Arctic Circle

#150
This is a beautiful example of the importance of diversity on a team. I have no idea how diverse the team is and I am not speaking of racial or sex diversity... this is the core of the discussion, having people with varying life experiences prevent obvious bugs like this or innovative ideas that no one person could think about. This is a fun bug
Post reply on HN