Redmond Influenza strain 19H2 to be released in spring 2020
cf title
Microsoft enlivened an otherwise deadly dull Windows 10 Insider build by revealing the corporation now defines its own seasons. Other than the appearance of the Windows Subsystem for Linux (WSL) 2 in the recent weeks, the last few builds of Windows 10 20H1, due for release some time next year, have been notable for, er, not …
That should be
IF (DateTime.Now > Spring) { WHILE (Windows != Done) ++Spring; }
You don't care what the value of Spring was before you added 1 to it. You wasted CPU cycles, and possibly memory, making a copy of the previous value of Spring; and then you went and forgot all about it. It's a good job for you that computers don't have feelings; because if they did, yours would be well and truly pissed off.
Anyway, I shouldn't be here. I've got a beam to chase .....
Spring is going to overflow - the While clause will not terminate - the time comparison needs to be in the While clause.
Correct coding
WHILE ((Windows != Done) && (DateTime.Now > Spring)) {++Spring;}
=================
++Pedant;
However as Windows is never Done - the first clause should be
(Windows != PretendToBeWorking)
It's reading the value of Windows each time at the beginning of the loop; and as long as this is one of those system pseudo-variables that BASIC used to use, and responds to other pseudo-variables being written, it will work.
Actually, maybe the pseudo-variables update asynchronously and the redundant pre-increment copy is a cunningly disguised clock slide ..... and a nice little trap for the unwary future maintainer!
Only those who in their soul whishes to be a computer. Human beings are not case sensitive, nor their languages - even those languages that have stricter case rules are fully intelligible even when those rules aren't respected - as they are mostly "decorations" to make writings easier to read.
But I'm going to deliver a language that requires a specific font to be compiled, and the font will be one of the less readable ones... I guess I will find a lot of "real programmers" who will believe that's the way to do it....
Because unluckily too many are still confusing lack of memory and CPU cycles and shortcuts to make compilers code easier to write and less resource demanding as good design choices... that's explain a lot of actual IT, and very stupid UI designs.
???? Summer solstice is 20-21 June (Northern Hemisphere, 20-21 December on the other side) - where May ever enters in the picture???
Late August is full Summer indeed, as it lasts until September 22-23 (20-21 March)
I would suggest to read a good book about Astronomy, and avoid Google searches, and New Age/Wicca interpretations....
Because not everybody follow Keltic traditions where solstices/equinoxes where in the middle of their "seasons" - anyway the ancient "seasons" may depend a lot on latitude (and daytime length), natural events (rains, etc.) harvest times, religious beliefs, and calendar errors accumulated over centuries.
I.e. at high latitudes centering "Summer" around the period with the longest daylight make sense. At lower ones, the changes are less important, and harvests may last longer
Remember that both Cesar, Augustus and Gregorius had to fix the calendar that was drifting away because of bad precision.
Astronomer fixed seasons periods in a way that doesn't depend on local events, and is precisely measurable - and the Gregorian calendar ensures equinoxes and solstices happen in the same days.