Conversation

Notices

1. Embed this notice
   φ (fiore@brain.worm.pink)'s status on Friday, 21-Feb-2025 07:12:46 JST φ

   • m0xEE
   • snacks

   @max @snacks @m0xee good article

   • snacks likes this.
   • Embed this notice
     m0xEE (m0xee@social.librem.one)'s status on Friday, 21-Feb-2025 08:19:09 JST m0xEE

     in reply to

     • snacks

     @fiore @max @snacks
     I agree! The main point: it's hard to move away from — that is indeed so and it's very important when you're using it commercially, as for other disadvantages — they have their counterparts in other languages, the article even gives a few examples of those.
     One other thing that strikes me: indeed, it has very opinionated defaults and your code is to be error-prone if you're writing it just by looking at others' code, which is important for junior devs…

     snacks likes this.
   • Embed this notice
     m0xEE (m0xee@social.librem.one)'s status on Friday, 21-Feb-2025 16:33:38 JST m0xEE

     in reply to

     • snacks

     @fiore @max @snacks
     You have to learn how to write *idiomatic* Go code (at least read The Go Programming Language), then a lot of mistakes are easy to avoid — and a lot of things start making sense, those that don't — never do 😂

   • Embed this notice
     m0xEE (m0xee@social.librem.one)'s status on Friday, 21-Feb-2025 16:33:38 JST m0xEE

     in reply to

     • snacks

     @fiore @max @snacks
     Indeed, the compiler doesn't warn you about shit… But in case with Rust you're in some cases doing things in a very inefficient way just to make the compiler SHUT THE FUCK UP — because you feel that re-writing it in an idiomatic way for Rust might make your head explode 🤯
     All in all, nothing is perfect, the article is absolutely right about that.

     snacks likes this.