3 ms·
Beginner's rite of passage: 1. fmt.Sprintf("Why doesn't %s have %s?\n", language, feature) 2. fmt.Sprintf("Builds %s in %s\n", feature, language) 3. fmt.Spri
by tmpz22 7y ago
Beginner's rite of passage:
1. fmt.Sprintf("Why doesn't %s have %s?\n", language, feature)
2. fmt.Sprintf("Builds %s in %s\n", feature, language)
3. fmt.Sprintf("Realizes %s actually sucks in %s and there are some good reasons nobody built it in the first place\n", feature, language)
Generally I think it's awesome people go down this path because sometimes really cool things are built as a result, but when the project in question overlaps with on-boarding from another tool, its is rife for another beginner to adopt it and get it stuck in production just because they wanted a slightly quicker transition from their former toolchain.
- ascales 7y agoI had this exact experience with Go. I'd ask myself, why is this not more like {{otherLanguage}} and I'd install a package to solve the problem I thought I had. Really, though, it turned out that most things I saw as problems with Go aren't really problems at all, and I just needed to explore the ecosystem a bit more.