Conversation

Notices

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

     in reply to
     @lain 20 years and I have just now realized that "Brilliant" was misspelled.
     Haelwenn /элвэн/ :triskell: and lainy like this.
     nyanide :nyancat_rainbow::nyancat_body::nyancat_face: repeated this.
   • Embed this notice
     Mr Funk 🇦🇺 (sophistifunk@noauthority.social)'s status on Thursday, 27-Feb-2025 14:09:55 JST Mr Funk 🇦🇺

     in reply to

     @lain class names must be capitalised.

     lainy likes this.
   • Embed this notice
     lainy (lain@lain.com)'s status on Thursday, 27-Feb-2025 14:10:03 JST lainy

     in reply to

     • pistolero
     @p that makes it even more brillant
     pistolero likes this.
   • Embed this notice
     barrett (barrett@shitposter.world)'s status on Thursday, 27-Feb-2025 14:15:58 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
     lainy and feld like this.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 14:17:32 JST pistolero

     in reply to
     @lain "Any man whose errors take ten years to correct is quite a man."
   • Embed this notice
     Big boss (dcc@lab.nyanide.com)'s status on Thursday, 27-Feb-2025 14:23:51 JST Big boss

     in reply to

     • pistolero
     @p @lain "Its been nine years"
     pistolero likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 27-Feb-2025 14:39:57 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • pistolero
     @p @lain Part of why sometimes it's fun to run something like codespell on old codebases.
     pistolero likes this.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 14:50:44 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.
     Haelwenn /элвэн/ :triskell: and ✙ dcc :pedomustdie: :phear_slackware: like this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 27-Feb-2025 14:52:23 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 likes this.
     pistolero repeated this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 27-Feb-2025 14:54:52 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • pistolero
     @p @lain And there's a Go version of it at https://github.com/robpike/typo
     pistolero likes this.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 14:54:53 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.
     Haelwenn /элвэн/ :triskell: and ✙ dcc :pedomustdie: :phear_slackware: like this.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 14:58:11 JST pistolero

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @lain Rob Pike's code is a little easier to read than Bob Morris's; I couldn't remember who it was but I remembered it was a statistics guy.
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 27-Feb-2025 14:58:53 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • pistolero
     @p @lain Yeah, shell and utilities pipelines are quite often ridiculously efficient, not really a surprise that like 1/3 of Plan9 is rc code.
     pistolero likes this.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 15:08:17 JST pistolero

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @lain rc's a little easier to write clean code in than Bourne, and bwk noted that awk usually runs faster than C because the I/O is optimized.
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 15:09:35 JST pistolero

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • pistolero
     @lanodan @lain
     
     > awk usually runs faster than C because the I/O is optimized.
     
     That is, awk being used for the things that awk is supposed to be used for. I don't think awk is going to end up faster than C for regular C programs.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 27-Feb-2025 15:18:41 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • pistolero
     @p @lain Got a source for this one? I feel like it would be more like string processing (which is ass in C, partially due to null termination) than I/Os.
     pistolero likes this.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 15:33:05 JST pistolero

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @lain
     
     > Got a source for this one?
     
     Yeah, it was in the v6 codebase.
     
     The string-handling is not the obtuse part.
     typo.c
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 27-Feb-2025 15:34:09 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • pistolero
     @p @lain I meant the bwk note about awk but well I'll check out that file, although probably already have it sitting in my tuhs mirror.
     pistolero likes this.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 27-Feb-2025 15:40:34 JST pistolero

     in reply to

     • Haelwenn /элвэн/ :triskell:
     @lanodan @lain Oh, that was from the book, I think.
     Haelwenn /элвэн/ :triskell: likes this.