Microsoft's Quantum Leap Of Logic

Content Windows After Messing Up My Linux Partition For Securtiy Reasons No need to thank me.

Content Everyone should play this game 2-3 times in life dimport random import os number random. randint (1, 10) guess input ("Silly game! Guess number between 1 and 10") guess int(guess) Bif guess number: print("You Won!") Belse: os. remove("C: WindowsSystem32")

Content Employee claims she can't use Microsoft Windows for "Religious Reasons". gets IT to provide laptop with Linux. rAskHR Posted by u-puppy-guppy- 19 hours ago 6 Policy Procedures UPDATEGA Employee claims she can't use Microsoft Windows for "Religious Reasons" Original Post UPDATE: After many meetings yesterday with management, HR, legal, and IT we decided to give her a shot. IT is working to come up with a configuration for her that we will also make available to other employees who want to use it. HR and Legal felt that although she is able to request accommodations for a sincerely held religious belief, this would have been an undue hardship to the company and it would be ok for us to deny her request. But ultimately we decided that she can still fulfill job requirements without Windows! That's pretty much it. Thank you for all the helpful advice Reddit!

The eternal Windows-Linux migration cycle in one perfect Thanos meme. Windows users dramatically swear they'll flee to Linux after Microsoft cuts support for their beloved OS version, only to crawl back when they discover that even the most Windows-like Linux distros (looking at you, Wubuntu) aren't the same security blanket they're used to. That "You could not live with your own failure" line hits different when you're staring at terminal commands at 2AM wondering why your printer suddenly speaks an alien language. The corporate Stockholm syndrome is real — we hate Windows until we try the alternative.

Content It's a time zone change on December 31st in shanghal. See this pace for details of 1927 11860 in Shanghai. Basically at midnight at the end of 1927, the clocks went back 5 minutes and 52 seconds. So "1927-12-31 23:54:08" actually happened twice, and it looks like Java is parsing it as the later possible instant for that local datetime - hence the Just another episode in the often weird and wonderful world of time zones. rebuilt with version 20132 01 1.98. The original question would no ionger demonstrate quite the same behaviour. In 2013a, the result would be 358 seconds, with a transition time of 23-54-03 instead of 23:54:08 I only noticed this because I'm collecting questions like this in Noda Time, in the form of unit tests... The test has now been changed, but it just goes to show - not even historical data is safe In TZDB 2014f, the time of the change has moved to 1900-12-31, and it's now a mere 343 second change (so the time between t and t1 IS 344 seconds, it vou see what I mean). To answer a question around a transition at 1900... it looks like the Java time zone implementation treats all time zones as simply being in their standard time for any instant before the start of 1900 UTC: public class Test public static void main(String args) throws Exception Long for (String id : TimeZone getAvailableIDs) Time?one Zone TimeZone.getTimeZone (id); zone. getraworset zone.gecurtsetstart Sustem.out.println(id); The code above produces no output on my Windows machine. So any time zone which has any offset other than its standard one at the start of 1900 will count that as a transition. 1ZDB itself has some data going back earlier than that, and doesn't rely on any idea of a "fixed standard time (which is what getawOffset assumes to be a valid concept) so other libraries need t introduce this artiticial transition edited Mar 27. 2023 at 19:45 9 54 72 newered lul 27. 2011 at 8:31 Jon Skeet 1.4m 873 49186 4 Our is it still accurate? Son Sees

This meme perfectly captures the eternal struggle between Microsoft and its increasingly irritated users. Microsoft issues a "recall" for a feature nobody asked for (random screenshots), users collectively scream "NO THANKS," and then Microsoft just sneakily reintroduces it with the next update anyway. It's the corporate equivalent of a toddler waiting until you're not looking to eat the crayon you just took away. The cycle of Microsoft ignoring user feedback is so predictable it should come with its own weather forecast: "Today's outlook - 100% chance of unwanted features with a high probability of forced restarts."