Skip to main content

Timeline for Weirdest obfuscated "Hello World!"

Current License: CC BY-SA 3.0

18 events
when toggle format what by license comment
Jun 17, 2020 at 9:04 history edited CommunityBot
Commonmark migration
Mar 5, 2014 at 11:20 comment added F. Hauri - Give Up GitHub @Quincunx It's the reason because I've edited original post... Unfortunely, comments stay hard to read (selection and copy seem correct)... Maybe the best is simply to drop them?!
Mar 5, 2014 at 4:47 comment added Justin @F.Hauri How is it possible that these comments go for so long before line-wrapping? (screenshot: i.sstatic.net/YzkhP.png)
S Mar 3, 2014 at 1:35 history suggested F. Hauri - Give Up GitHub CC BY-SA 3.0
Simplify and justify code
Mar 3, 2014 at 1:29 review Suggested edits
S Mar 3, 2014 at 1:35
Mar 3, 2014 at 0:10 comment added Digital Trauma @F.Hauri please go ahead! I'm open to any edits on this one, so long as no alphanumeric characters or quotes are introduced (and the program remains correct).
Mar 2, 2014 at 21:35 comment added F. Hauri - Give Up GitHub @DigitalTrauma Could I edit your answer to add a justified version with no more than 79 columns and 15 lines, more suitable for cut'n paste... (I dislike long line with 285 characters)??
Mar 2, 2014 at 18:26 comment added Digital Trauma @devnull Sorry, no prizes, other than a smug sense of self satisfaction ;-)
Mar 2, 2014 at 18:21 comment added devnull Any prizes for spotting eval? Brace expansion, err...
Mar 2, 2014 at 18:18 comment added devnull @DigitalTrauma I know that. Just wanted to point out the obvious issue. That said, it's very pretty. Nice!
Mar 2, 2014 at 18:18 comment added Digital Trauma @devnull as for 1), I never made any claims of portability ;-). What is the problem in BSD - dependence on /proc/$PID/attr or something else? I'd love to figure out how to do this in a portable manner, but I haven't figured out how to get past the /proc/$PID/attr dependency yet.
Mar 2, 2014 at 18:16 comment added Digital Trauma @devnull 2) is easy to fix - just run the : command to clear any previous error conditions reported in $?.
Mar 2, 2014 at 18:14 history edited Digital Trauma CC BY-SA 3.0
added 7 characters in body
Mar 2, 2014 at 17:14 comment added devnull This is pretty. But there are a couple of problems: (1) it isn't quite portable, I can't get it to run as is on BSD. (2) the script assumes that _________ would be set to 0 (what would happen if the script were sourced instead after an error?).
Mar 2, 2014 at 10:12 comment added F. Hauri - Give Up GitHub or worst: \\${_________}$[${______}${____}#${_____[${___________}+${__________}]}] make an exclamation point too;-)
Mar 2, 2014 at 10:05 comment added F. Hauri - Give Up GitHub There seem to be some limitation on SO rendering: I said that last line could begin by ${__[${____}]}${__[${__________}]}${__[${_______}]}${__[${___}${____}]} -${__[${____}]} (echo -e) and replace ! by \\${_________}${____}${___}
Mar 2, 2014 at 0:31 history edited Digital Trauma CC BY-SA 3.0
added 74 characters in body
Mar 2, 2014 at 0:25 history answered Digital Trauma CC BY-SA 3.0