Good Old Days

The evolution of asking for coding help in three stages: 1. Programming communities : "Have you tried Googling it?" *downvotes your question for being a duplicate from 2013* 2. Linux community : "I see you're struggling. Here's a 47-page manual and a cryptic one-liner that will either fix everything or format your hard drive. Figure out which!" 3. Web3 communities : "Hey fren! I can totally help! Just connect your wallet to this definitely-not-suspicious smart contract I made at 3am!"

Content THIS UI DOESNT LOOK GOOD IS SAME UI YOU APPROVED LAST WEEK IT LOOKS DIFFERENT WE WERE WORKING ON BACKEND, a WE DIDNT WORK ON UI UT LOOKS BAD YOU SHOULD HAVE WORKED ON UI

Content 2 Answers Active Oldest Votes Use shuf with the -n option as shown below, to get N random lines: 541 shuf -n N input output share improve this answer follow edited Jun 16 '16 at 20:48 DomainsFeatured 1,234 0 1 0 18 29 answered Feb 25 '13 at 11:03 dogbane 226k 69 351 388 35 This should be the accepted answer. Wow, shuf is sooo fast. - picking 10000 random lines from a textile with 40000 lines is instant. Trying to use 'sort -R' took so long I just CTRL-C it - carpii Jul 3 '15 at 20:10 2 If you just need a random set of lines, not in a random order, then shuf is very inefficient (for big file): better is to do reservoir sampling, as in this answer. - petrelharp Sep 6 '15 at 23:24 4 neither shuf nor sort -R are available for mac OSX. any suggestions? - Tom Smith Oct 6 '15 at 10:06 33 TomSmith On Mac OSX, if you are using Homebrew, you can get shuf or GNU sort by installing coreutils . More info here: apple.stackexchange.comquestions142860install-shuf-on-os-x - nofinator Oct 8 '15 at 13:11 7 shuf is fantastic. I tried in on a 78 Billion line text file and it did the job in less than 1 minute. - Ash Jan 19 '16 at 812 7 shuf is fantastic. I tried in on a 78 Billion line text file and it did the job in less than 1 minute. - Ash Jan 19 '16 at 8:13 78 Billion line text file The WHAT

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

Content Quack Overflow is listening... Explain your problem out loud. Speak naturally. Ask the duck! You'll need to explain your problem. Do you have a microphone? Yes No The duck is typing... "Quack" Quack Overflow says, "Whenever you're stuck, rubber ducking is a powerful method for solving even the most difficult problems. Insights are often found by simply describing the problem aloud." I have another problem I hate this duck

Content 100 likes on Instagram 50 upvotes on Reddit 5 upvotes on StackOverflow WF made with mematic