3 ms·

They must have written a s* load of code for this. Can't wait!

• tptacek 11y ago
  Yes, but it's all Golang, so you know 2/3rds of it is the same list management and sort code specialized for all our different structs, AM I RIGHT? I kill me.
  • karterk 11y ago
    Then, why Golang? Are there other things that make this duplication worth?
    • pja 11y ago
      Golang makes total sense for the kind of programmer who wants everything to be there on the screen in front of them. It’s like C in that regard - write code, the computer does what the code says, programmer is happy: No constructors, no destructors, no exceptions, no weirdness But C has weird bits & odd corner cases. C isn’t type safe. C requires you to do all your own memory management. C is in fact full of landmines for the ordinary programmer (which is all of us, even the very best on a bad day) to step on inadvertently. What if you could have a language that acted like C, but was type safe, did do memory management for you, and had a decent standard library so you didn’t have to spend time writing yet another linked list implementation? Oh, and the one true concurrency scheme (Hoare’s communicating sequential processes) is built right in to the language, so you can write type-safe asynchronous systems without tedious boilerplate. That language is Golang. Like C, it’s a wysiwyg language, unlike C it’s much harder to shoot your own foot off with it.
  • minikomi 11y ago
    Ah, but how many if err != nil 's?
    • baby 11y ago
      you mean _ ?