4 ms·

I wrote a PDF parser in golang a few years ago and it was an extremely unpleasant experience. No polymorphism means I essentially have to cast everything to voi

I wrote a PDF parser in golang a few years ago and it was an extremely unpleasant experience. No polymorphism means I essentially have to cast everything to void* aka interface{}. Rewrote it in C (the rewrite was quite easy actually) which at least made the lib accessible to other languages.

codr7 7y ago
There's plenty of polymorphism in Go, that's what interfaces are for. In C you would typically use a struct stuffed with function pointers, how is that an improvement? Its still a better C in many ways, strings and character sets is a big one.
- pishpash 7y ago
  It's definitely a better C, but that's about it. Let's not kid ourselves. It's in many ways a language stuck in the past, for senile people, OCD's, or drones who are forbidden to produce non-uniformity and who want everything verbose and explicit.
  - camdenlock 7y ago
    I kinda think /you/ are kidding yourself by making such wild assertions. I certainly do not agree with them, and I see no clear evidence to support them. There are different languages for different tasks. Tradeoffs abound. Pick the right tool, that’s all.
  - codr7 7y ago
    Like C, you mean? How is it more verbose than C++, Java, Rust or Swift? You're not making much sense here, why do you feel so threatened?
    - wtetzner 7y ago
      > How is it more verbose than C++, Java, Rust or Swift? All of these languages have generics.
      - codr7 7y ago
        Indeed. The parent post was calling out Go for being overly verbose and explicit compared to alternatives. I was simply making an example to the contrary.