home.social

#parentheses — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #parentheses, aggregated by home.social.

  1. Ah, the thrilling world of #parentheses 🤔! Because clearly, the burning issue on everyone's mind is how to "ungroup" expressions in #programming languages. Let's all pretend this is groundbreaking stuff and not just #overthinking #syntax until our brains implode 🧠💥.
    kellett.im/a/inverse-parenthes #ungrouping #tech #humor #HackerNews #ngated

  2. Ah, the thrilling world of #parentheses 🤔! Because clearly, the burning issue on everyone's mind is how to "ungroup" expressions in #programming languages. Let's all pretend this is groundbreaking stuff and not just #overthinking #syntax until our brains implode 🧠💥.
    kellett.im/a/inverse-parenthes #ungrouping #tech #humor #HackerNews #ngated

  3. Ah, the thrilling world of #parentheses 🤔! Because clearly, the burning issue on everyone's mind is how to "ungroup" expressions in #programming languages. Let's all pretend this is groundbreaking stuff and not just #overthinking #syntax until our brains implode 🧠💥.
    kellett.im/a/inverse-parenthes #ungrouping #tech #humor #HackerNews #ngated

  4. Ah, the thrilling world of #parentheses 🤔! Because clearly, the burning issue on everyone's mind is how to "ungroup" expressions in #programming languages. Let's all pretend this is groundbreaking stuff and not just #overthinking #syntax until our brains implode 🧠💥.
    kellett.im/a/inverse-parenthes #ungrouping #tech #humor #HackerNews #ngated

  5. 🎩✨ Behold, the mystical art of transforming #Lua closures into C closures—a riveting read for the 0.0001% who crave #APIs and global functions like their morning coffee! ☕🔮 Spoiler alert: you'll need a PhD in #tedium and an undying love for #parentheses. 🙄📜
    lowkpro.com/blog/creating-c-cl #Cclosures #Coffee #HackerNews #ngated

  6. Bozhidar Batsov, a self-proclaimed "Emacs fanatic" and "lover of #parentheses," spent 20 minutes convincing us why we should care about F#. Spoiler alert: it's mostly about parentheses. 😏 But don't worry, you'll only need a 15-year hiatus from sanity to appreciate it fully. 💤
    batsov.com/articles/2025/03/30 #EmacsFanatic #FSharp #LoversOfParentheses #CodingHumor #TechTalk #HackerNews #ngated

  7. Bozhidar Batsov, a self-proclaimed "Emacs fanatic" and "lover of #parentheses," spent 20 minutes convincing us why we should care about F#. Spoiler alert: it's mostly about parentheses. 😏 But don't worry, you'll only need a 15-year hiatus from sanity to appreciate it fully. 💤
    batsov.com/articles/2025/03/30 #EmacsFanatic #FSharp #LoversOfParentheses #CodingHumor #TechTalk #HackerNews #ngated

  8. Bozhidar Batsov, a self-proclaimed "Emacs fanatic" and "lover of #parentheses," spent 20 minutes convincing us why we should care about F#. Spoiler alert: it's mostly about parentheses. 😏 But don't worry, you'll only need a 15-year hiatus from sanity to appreciate it fully. 💤
    batsov.com/articles/2025/03/30 #EmacsFanatic #FSharp #LoversOfParentheses #CodingHumor #TechTalk #HackerNews #ngated

  9. Bozhidar Batsov, a self-proclaimed "Emacs fanatic" and "lover of #parentheses," spent 20 minutes convincing us why we should care about F#. Spoiler alert: it's mostly about parentheses. 😏 But don't worry, you'll only need a 15-year hiatus from sanity to appreciate it fully. 💤
    batsov.com/articles/2025/03/30 #EmacsFanatic #FSharp #LoversOfParentheses #CodingHumor #TechTalk #HackerNews #ngated

  10. > "They were so aggressive in their text!"

    < "Why, what'd they do?"

    > "They used an ellipsis!"

    Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]

    #aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk

    [1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".

  11. > "They were so aggressive in their text!"

    < "Why, what'd they do?"

    > "They used an ellipsis!"

    Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]

    #aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk

    [1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".

  12. > "They were so aggressive in their text!"

    < "Why, what'd they do?"

    > "They used an ellipsis!"

    Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]

    #aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk

    [1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".

  13. > "They were so aggressive in their text!"

    < "Why, what'd they do?"

    > "They used an ellipsis!"

    Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]

    #aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk

    [1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".

  14. > "They were so aggressive in their text!"

    < "Why, what'd they do?"

    > "They used an ellipsis!"

    Real conversation. I'm looking around for Alan Funt. I can't even imagine their reaction if it had been an octothorpe. [1]

    #aggressive #punctuation #trigger #ellipsis #octothorpe #ampersand #hyphen #caret #parentheses #brackets #braces #asterisk

    [1] Why yes, Firefox spellchecker, when I typed "octothorpe" I clearly really meant to type "#clotheshorse".

  15. @winniehell

    It is #unfortunate. It would be nice if we had a fourth member to go after #parentheses, #brackets, and #braces.

    I tend not to use set literals, preferring `set(sequence)`. Maybe it's because my brain insists they're broken #dicts.

  16. @winniehell

    It is #unfortunate. It would be nice if we had a fourth member to go after #parentheses, #brackets, and #braces.

    I tend not to use set literals, preferring `set(sequence)`. Maybe it's because my brain insists they're broken #dicts.

  17. @winniehell

    It is #unfortunate. It would be nice if we had a fourth member to go after #parentheses, #brackets, and #braces.

    I tend not to use set literals, preferring `set(sequence)`. Maybe it's because my brain insists they're broken #dicts.

  18. @winniehell

    It is #unfortunate. It would be nice if we had a fourth member to go after #parentheses, #brackets, and #braces.

    I tend not to use set literals, preferring `set(sequence)`. Maybe it's because my brain insists they're broken #dicts.

  19. @winniehell

    It is #unfortunate. It would be nice if we had a fourth member to go after #parentheses, #brackets, and #braces.

    I tend not to use set literals, preferring `set(sequence)`. Maybe it's because my brain insists they're broken #dicts.