Conversation

Notices

1. Embed this notice
   muesli (fribbledom@mastodon.social)'s status on Tuesday, 10-Dec-2024 04:19:55 JST muesli

   • Daniel Terhorst-North

   @tastapod

   Since readability is Go's biggest strength, I'd argue that yes, it's probably a bad idea.

   • Embed this notice
     Marco "Ocramius" Pivetta (ocramius@mastodon.social)'s status on Tuesday, 10-Dec-2024 04:29:05 JST Marco "Ocramius" Pivetta

     in reply to

     • Daniel Terhorst-North

     @fribbledom @tastapod after 3 months of writing Go: no, it's not readable at all 😭

   • Embed this notice
     muesli (fribbledom@mastodon.social)'s status on Tuesday, 10-Dec-2024 04:32:53 JST muesli

     in reply to

     • Marco "Ocramius" Pivetta
     • Daniel Terhorst-North

     @ocramius @tastapod

     I'm sorry to hear that, but if that's the case I'd love (or hate) to hear what you consider readable.

   • Embed this notice
     Marco "Ocramius" Pivetta (ocramius@mastodon.social)'s status on Tuesday, 10-Dec-2024 04:39:01 JST Marco "Ocramius" Pivetta

     in reply to

     • Daniel Terhorst-North

     @fribbledom @tastapod this stuff, roughly: https://fsharpforfunandprofit.com/posts/recipe-part2/

     The entire for/select stuff is also very hard to both read and do right: also there, reactive programming operators are better than the imperative heck of #golang