Re:Goodbye to the C++ Implementation of Zig
by titzer on Thursday December 08, 2022 @06:49PM
(#33915486)
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!"
Re:Goodbye to the C++ Implementation of Zig
by booleandilemma on Thursday December 08, 2022 @06:13PM
(#33915101)
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.
Re:Goodbye to the C++ Implementation of Zig
by sidlls on Thursday December 08, 2022 @07:27PM
(#33915833)
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.
Re:Goodbye to the C++ Implementation of Zig
by IlliOnato on Friday December 09, 2022 @07:05AM
(#33920370)
In production code? Absolutely. While you experiment, write throw-away code, debug? Hell no!
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.