Good Bye, Old Friend

Microsoft: "Upgrade to Windows 11 or face the consequences of unsupported software!" Developers with battle-hardened machines: "I'll take the entire deck of security vulnerabilities, thanks." The risk calculation is simple—potential system instability from upgrading vs. the guaranteed productivity loss from having your PC held hostage by feature updates for 3 hours. I've seen Windows 11 "improvements" and I'm drawing 25 cards until my hardware physically disintegrates.

Ah, the irony. Microsoft proudly announces 30% of their code is now AI-generated, while simultaneously shipping a Windows 11 bug that duplicates Task Manager when you try to close it. So now you need two 'X' clicks to kill the process that's supposed to kill other processes. It's like watching someone install a fancy smart lock on their front door while the back door is literally falling off its hinges. The future of software, folks – where AI helps you write code that breaks in spectacular new ways.

Content 10 WAYS TO TROLL YOUR DEVELOPER 1: CHANGE ALL CONSOLE SETTINGS TO BLACK ON BLACK. STRANGE... NO DEBUG PRINTOUTS 2: HAVE THEM FIX OLD CODE. 3: REQUIRE IT TO WORK ON ALL PLATFORMS. IT WILL HAVE TORUN ON IOS, ANDROID, WINDOWS PHONE AND THIS ROTARY FROM 1931. 4: HIRE UNQUALIFIED DEVELOPERS. CHAD WILLBE DOING UI. 5: DISREGARD ANY NEED FOR TESTING. A TESTING PHASE ISN'T REALLY IN THE BUDGET IT'S JUST GONNA HAVE TO WORK 6: REQUIRE IT TO WORK FOR ALL USER GROUPS. MR. NIBBLES SAID ITS VERY UNINTUITIVE. MEOW. 7: POP YOUR HEAD IN EVERY FIVE MINUTES TOROND OVER YOUR STUPID COWORKERS SHARON USES A QUESTION MARK WHEN SHE GOOGLES A QUESTIONI 8: BLOCK ALL ACCESS TO STACK OVERFLOW. NOW, NOW, NO CHEATING CELO 9: MAKE ALL TASKS TOP PRIORITY. THE DATABASE NEEDS TO BEUP AND RUNNING ASAP, AS WELL AS THE AUDIO ENGINE, CRITICAL AND ALSO 3D BUTTON SHADING. 10:ASK A DEV TO 'FIX YOUR COMPUTER' MR. NIBBLES WAS WATCHING GOOD WIFE AND SUDDENLY THIS BLUE THINGY CAME War and Peas

Content Just booted up my windows pc only to find out that Melinda Gates has already taken her half.

Content The Corporate Mindset The best solution! It has all features! It's cost effective! It's not from Microsoft... imgfiip.com

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