4 ms·
> Go people love doing this, too, creating bad solutions to solved problems. My anecdote: most "Go people" doing this are actually "Go beginners" that are stil
by jzelinskie 11y ago
> Go people love doing this, too, creating bad solutions to solved problems.
My anecdote: most "Go people" doing this are actually "Go beginners" that are still learning the language and attempting to write something familiar to cement their understanding. I imagine this is often the case for other languages.
- falcolas 11y agoYou'll also see this (that is, go replacements for common tools) as a direct result of a Suckless challenge to do exactly that. The idea being to get rid of the complexity of the current bash tools (let's be honest, when `cp` has options you would expect from `rsync`, it's gotten rather complex), with the side benefit of being statically compiled. I'll admit, I've written a few of these myself to help nail down both my knowledge of Go and the basic toolset I use every day. It was quite useful as a learning tool, even though they'll never replace the originals. Heck, I'd even recommend re-creating `dc` to anybody who is interested in learning a language, or writing a parser/interpreter for a language.
- eropple 11y ago> You'll also see this (that is, go replacements for common tools) as a direct result of a Suckless challenge to do exactly that. This is what I was referring to, yeah, and it is to my mind a sign of a certain amount of cultural insularity and maybe a little hubris. Reimplementing something like `dc` to learn a language is great, it's when you start movements to start replacing things--or even trying to be taken credibly as an alternative--that I think you had best come very correct or be ready to defend your contention that the status quo is for some reason unsuitable. "I don't already know sed" is not, to my mind, a good defense, which touched off this subthread.