GopherCon 2019: Optimizing Go Code Without a Blindfold - Daniel Marti

Поделиться
HTML-код
  • Опубликовано: 31 дек 2024

Комментарии • 6

  • @ronminnich
    @ronminnich 21 день назад

    Excellent talk, very helpful to me.

  • @andreasmalmqvist7900
    @andreasmalmqvist7900 5 лет назад

    What wm is that ?

  • @jameshwest
    @jameshwest 4 года назад

    Good topic and presentation reduced by the execution. First, do we really need the mascot and the speakers head taking up the presentation real-estate? Doing this reduces the space available for the valuable stuff (the presentation)
    Over all Daniel did a good job with the presentation, but the impact was limited by having to watch him debug his code live. He could do a dry run before the presentation and save off the files that have the correct code for each next step. By doing this, there is less code to debug live (not that this isn't interesting, but it takes away from the main topic)

    • @phanirithvij
      @phanirithvij 3 года назад +1

      You're just nitpiking. All talks, no matter the conference have at least the speakers in the view, keep in mind most of the online viewers did not attend the event, they provide slides to download anyway in the gophercon github repo for every talk. Debugging live did not force an early end of the talk so I don't see how this takes away from the main topic when the main topic was done by the time the live demo started.

  • @blizzy78
    @blizzy78 5 лет назад +2

    All this talk about laptop overheating... Why not use a proper machine to do your benchmarks?

    • @AdityaFingerstyle
      @AdityaFingerstyle 3 года назад +4

      Because a normal developer doesn't have a "proper machine" lying around to do benchmarks. Daniel showed a solution to tackle the issue.