Feelings about GopherCon VietNam 2019

GopherCon VietNam 2019

2019-11-02
Capella Gallery Hall

The most interesting topic for me is "CloudRetro." Thanks speakers!

I'm very surprised. In Gopher con VietNam, most of the speakers have presentations in English. Most of the questions and answers are also in English. I can understand easily because the speakers talk in English. Awesome! But the reaction of attendees is better the speaker in Vietnamese 😅

People in the booth ask something to me, but Vietnamese is difficult 😓
A few attendees use their laptops. There are desks only the front row.

Tanuki

Tanuki is one solution for dependency hell. https://github.com/sausheong/tanuki

In my understanding, the speaker wants to talk about "the Unix philosophy."
But this approach seems each handler has dependencies. This means each handler has its own dependency hell. This is still thought experiment.

SRE

The fundamental introduction of SRE: Google - Site Reliability Engineering

We need to understand "error budgets" more.
5 key principles for SRE

• Metrics & Monitoring
• Capacity planning
• change management
• Emergency response
• Culture

Start with Service Level Objectives
SLO and/or error budget

CloudRetro

This topic is crazy 😍
https://github.com/giongto35/cloud-game/wiki/FAQ
We can play a video game on the cloud server via a web browser, and the server encodes video and audio, then we can see this video. We can share the game state by permanent link.

Open-source Cloud Gaming Service For Retro Games
Video demo: https://www.youtube.com/watch?v=GUBrJGAxZZg
giongto35/cloud-game Web-based Cloud Gaming service with Retro Game

Comments

[giongto35]

I just joined Dev.to today. I'm really happy when I saw your review about my work in GopherCon.
Thank you very much.
I spent a lot of time and effort working on that. You motivated me to continue working on this project.
It's nice to know that you are also in Vietnam, Ho Chi Minh. Maybe we can schedule to meet someday :D

[Bradley D. Thornton]

Why do they call it Gophercon when it's not about Gopher or the Gopher protocol, servers, or clients at all?

It's about Go, right? So shouldn't it be called something like GoLangCon instead, to avoid confusion with Gophercon events that actually are about the Gopher Internet protocol that's been around and going strong since RFC-1436 with the IANA assignment of TCP port 70 ???

Don't get me wrong. I like GoLang, and there's a couple of Gopher servers and clients written in it, but other than that, Go has nothing to do with Gopher.

[Freedom]

The mascot itself is a Gopher and it will also explain the historical way back you probably never knew, me too.

blog.golang.org/gopher

[Bradley D. Thornton]

And then there's this, designed by the Gopher folks themselves:

Developed by Mark McCahill, Paul Lindner and Farhad Anklesaria from a Campus-Wide Information Service, Gopher was named both for the University of Minnosota mascot, and after “go for” meaning fetch.

gopher://gopherspace.de/0/menu/WIKI/GopherCon/94/Agenda_in_detail_FINAL.txt

thepracticaldev.s3.amazonaws.com/i...

thepracticaldev.s3.amazonaws.com/i...