gopher (1676)

Signed up 509 days ago

  • This is a fairly balanced overview - he uses both, but appreciates Go because it's a bit simpler. Scala sounds interesting and far more concise than Go, but I'd be worried about whether my future self would understand what I'd written 6 months ago.

  • What is the performance like with just regexp?

  • A few things which are not quite right:

    > The biggest difference between the two languages is that compilation for the destination architecture has to be done on that same architecture.

    Go supports easy cross compilation, I'm not sure why people choose to compile on the destination hosts rather than just deploy a binary.

    > By contrast, Go has no way of tracking the execution of individual goroutines.

    As he goes on to say you can use channels for this, so it's a little disingenuous to claim that you can't track errors on goroutines.

    Really interesting comparison though. Thanks for the link.

  • I'm seeing a weird cert error in Brave, anyone else seeing that?

  • Took a while to get to the bit about go, but there is lots of detail on their setup in this talk.

  • One thing that is broken by this release: js microtemplates no longer work with html/template if their delimiter uses <>, as they are escaped by the parser as text (they used to be treated as js).

  • This was quite fun but I do find the UI with multiple overlapping windows a bit confusing and difficult to navigate, particularly when you click on a type definition and open another file. Does anyone know what UI library it's using? I'd prefer to see a list of the files and then be able to go into each one individually, as it is there is a lot more clicking with the mouse than I'd expect with a CLI.

  • From this tweet by Brian Ketelsen:

  • This is a really good article from someone who knows a lot about this stuff (works at cloudflare), I didn't know about the timouts.

    I do wish they could change some of the defaults in the stdlib.

  • Great advice here on making code readable - it's definitely easier to decode what someone is thinking if the happy path is always on the left, and errors are dealt with and returned. Most go code I've seen adopts this style.