4 ms·

I love Caddy! It’s so much nicer to configure compared to Nginx. No plugins needed for automatic TLS certs – it’s bulilt-in. And it’s written in a memory-saf

• junon 5y ago
  Go is not memory safe, not sure where you got that idea. Go programs can absolutely succumb to nil pointer references, memory leaks, etc.
  • jrockway 5y ago
    Safety can include crashing. It's better than returning subtly incorrect results. Yes, there are nil pointers and unnecessary data structures that people keep around, but that's miles ahead of C where an HTTP request and a missing bounds check can inject new code into the application. If you have a Go program where user input can be executed as code (no cgo, no unsafe), I'd love to see it.
    • Zababa 5y ago
      > no cgo If you're not careful, you will use c code when using os/user and net according to https://www.arp242.net/static-go.html https://www.arp242.net/static-go.html.
    • junon 5y ago
      This is splitting hairs and arguing semantics. The absolutist statement "Go is memory safe" is simply incorrect.
      • mholt 5y ago
        > The absolutist statement "Go is memory safe" is simply incorrect. That absolutist statement is also incorrect. "Go has strong memory safety guarantees" is more accurate. But neither "Go is memory safe" nor "Go is not memory safe" are correct.
        • cpach 5y ago
          Ok, cool. TIL!
  • tcard 5y ago
    That's type safety, not memory safety. ... But no, Go isn't memory safe, insofar data races can cause memory corruption.
    • junon 5y ago
      That is a part of memory safety, not just type safety. Type safety could fix this form of memory issue, yes.
  • mholt 5y ago
    Memory safety is a spectrum, and Go is much higher on that spectrum than C/C++.