Threads for blackflicker

    1. 6

      Why would you tag the explanation of a trivial language feature with “AI”? Is “AI” the new “VR” in the buzzword hierarchy?

      1. 3

        I put that tag incorrectly, may bad, sorries.

    2. 1

      I feel like this would benefit from an ontology that indicates how these are related to each other.

      1. 1

        Hmm, can you give an example?

        1. 1

          An example of an ontology?

    3. 1

      The problem with the example implementation of String() is that it needs to be kept in sync with the set of values in the enum type.

      1. 2

        I don’t know if this was updated after your post, but he does introduce the stringer tool. Which I realize is a little ridiculous as a language tool, but thought I’d point it out.

        1. 1

          No, Stringer recommendation was there.

          In the post, first I’m trying to explain how enums work rather than the best practices. Then, I widening it more about what to use for enums. Including stringer and iota.

    4. 1

      I’ll be writing new articles to my Go programming blog.

    5. 1

      I enjoyed your post but the auto-adding of browser history items makes me rage inside! I had to rage quit to get back to lobsters!

      1. 1

        Thx! I don’t understand what you mean, sorry :-( What should I do better?

        1. 2

          There’s some javascript on the page that breaks the back button.

          1. 1

            Hmm, that must have been because of Medium.com. Can you send me a screenshot so I can tell them about the problem?

            1. 1

              It would just be a screenshot of your article with me, offscreen, futilely typing Alt-Left.

              And is sounds like qbit may have had a different problem where the js used history.pushState() incorrectly and there were too many items to go back through. Again, won’t be visible in a screenshot.

              1. 1

                Hmm, ok, I’m telling them about this problem. I hope they’d fix it.

                1. 1

                  They said:

                  We’re not seeing any problems with this on our side. I think in this case it would be best if you could ask the user who is experiencing problems to write in to yourfriends@medium.com where we can troubleshoot this directly with them.

                  Oops :(

                2. 1

                  The issue I had was basically exactly what pushcx explained. Every heading I scrolled past added an entry via history.pushState(), so every press of the back button just went up to the previous heading.

                  1. 1

                    If you can’t email them, I can try again. Which browser and device you were using when you had the issue? Thx for your help btw!

    6. 1

      While I like the “humanized” approach, it does seem rather specific to language that have the same sentence structure as English.

      1. 1

        Wow, good comment! I hadn’t looked at it from this perpective. My native-language isn’t English btw, however, I used to English, so it comes natural to me in Go.

    7. 4

      Looks like a good primer to Go - thanks!

      Smaller number of packages as compared to other ecosystems like Node.js and Ruby. However, it’s increasing.

      I’ve heard this as a criticism before, but as a person who did quite a bit of Ruby, I think this isn’t a downside but is instead an upside ;)

      Consider some of the most frequently downloaded Ruby gems. Lots of these are right in the Go stdlib:

      Is this just a case that Go has more batteries included than Ruby or Node.js?

      1. 1

        Yeah, exactly! I know what you mean, I came from both Nodejs and Ruby communities to Go. And, millions of fragmented packages bit me too…

        I put it there in disadvantages however I don’t think most of them as disadvantages, only that, people can may judge it that way, I’m not sure.