Conversation

Notices

1. LS (lain@lain.com)'s status on Thursday, 27-Feb-2025 14:02:29 JST LS
   package test;
   
   public class paulaBean {
   
   private String paula = "Brillant";
   
   public String getPaula() {
   return paula;
   }
   }
   • pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 14:07:09 JST pistolero

     in reply to
     @lain 20 years and I have just now realized that "Brilliant" was misspelled.
     LS likes this.
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: repeated this.
   • Mr Funk 🇦🇺 (sophistifunk@noauthority.social)'s status on Thursday, 27-Feb-2025 14:09:53 JST Mr Funk 🇦🇺

     in reply to

     @lain class names must be capitalised.

     LS likes this.
   • LS (lain@lain.com)'s status on Thursday, 27-Feb-2025 14:10:01 JST LS

     in reply to

     • pistolero
     @p that makes it even more brillant
   • barrett (barrett@shitposter.world)'s status on Thursday, 27-Feb-2025 14:15:55 JST barrett

     in reply to
     @lain
     
     ffmpeg -y -hide_banner \
     -i hotDog.mp4 \
     -vf "negate" \
     -c:v libx264 -preset ultrafast -crf 18 \
     -c:a copy \
     dogHot.mp4
     LS likes this.
   • pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 14:56:05 JST pistolero

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @lain Ah, right, yes! typo(1), that was the program.
     
     I think, like, most of the C programs that can be replaced by shell one-liners aren't worth porting: just shove it into a one-line shell script. Runs better anyway, half the time.
     † top dog :pedomustdie: likes this.
   • Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 27-Feb-2025 14:56:07 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • pistolero
     @p @lain Ah yeah, typo(1) worked like that, made me want to port it few times because it could also catch brainfarts kind of typos where you're using the wrong word.
   • pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 14:56:08 JST pistolero

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @lain I was reading TUHS and :mcilroy: is still on there and posts all the time, and he was talking about very early spelling checkers; you didn't have spare space for lists of all the words in the English language, so it would do something like¹
     
     :mycomputer: tr -c '-a-zA-Z0-9' '\n' | awk '{a[$1]++}END{for(i in a)print a[i], i}' | sort -n
     
     The reasoning was that most of the misspelled words would be relatively unique, so a word that only appears once is more likely to be a misspelling. This approach probably works really well for catching misspelled identifiers in codebases.
     
     ¹ This is an approximation; I don't remember the name of the spelling program. I dug up the C from one of the really old Unix source dumps, but it was nearly unreadable and didn't compile. Most of the old code still builds and is legible, like cal and ed, but this was kind of a mess. Apparently it got included in the Unix Writer's Workbench but wasn't written by Lorinda Cherry; statistics guys write really rough code for some reason.
     † top dog :pedomustdie: likes this.
   • Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 27-Feb-2025 14:56:09 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • pistolero
     @p @lain Part of why sometimes it's fun to run something like codespell on old codebases.