4 ms·

Nonsense. I love it and I've been programming since the 80's. I watched (and used) C++ as it grew into the monstrosity it is today. I've written and maintain

by bmurphy1976 4y ago

Nonsense. I love it and I've been programming since the 80's. I watched (and used) C++ as it grew into the monstrosity it is today. I've written and maintained production code in F#, C#, Python, Ruby, Perl, Java, JavaScript, Go, PHP, Lua, VBScript, Visual Basic, C, and C++ and every variant of shell scripting imaginable. I've spent time working with Erlang, Haskell, Rust and a variety of other exotic languages because I found it interesting. I created a port of Clojure's Transducers to C# because I could. I am not afraid of abstractions, functional programming, or complicated CompSci concepts. And yet I keep going back to Go.

booleandilemma 4y ago
I like Go as a language in the abstract sense, but the experience of writing Go code is so tedious to me. Refusing to compile if there's an unused variable or unused import is too harsh - at least give me the option to make these things warnings.
- s_c_r 4y ago
  My usual approach is to comment stuff out while debugging/developing. Works well.
- sidlls 4y ago
  Having unused variables or unused imports makes the code dirty and should be treated as errors. It's one of the (few) good things about Go.
  - IlliOnato 4y ago
    In production code? Absolutely. While you experiment, write throw-away code, debug? Hell no!
  - wtetzner 4y ago
    Sure, but it’s a lot of extra friction when iterating/debugging.
titzer 4y ago
PL arguments are like: "I like icecream." "You idiot! I hate icecream and think everyone who likes icecream is a raging moron who deserves having their teeth rot out of their head! I wish their teeth would rot out tomorrow because I am so sick of waiting for it!"