HN Theater @HNTheaterMonth

The best talks and videos of Hacker News.

Hacker News Comments on
GOTO 2018 • The Robustness of Go • Francesc Campoy

GOTO Conferences · Youtube · 4 HN points · 3 HN comments
HN Theater has aggregated all Hacker News stories and comments that mention GOTO Conferences's video "GOTO 2018 • The Robustness of Go • Francesc Campoy".
Youtube Summary
This presentation was recorded at GOTO Copenhagen 2018. #gotocon #gotocph
http://gotocph.com

Francesc Campoy - Gopher, Host of the Just For Func Podcast, and VP of Developer Relations at source{d}

ABSTRACT
Go was designed with Google's needs in mind, and when you're running software at the scale that Google does robustness is of prime importance. In this talk we will cover what design decisions of Go help building robust programs, but also those parts of the language can cause problems that one needs to be aware and what techniques to apply to avoid risks.
We will also compare Go robustness to Erlang, probably the most robust runtime [...]

Download slides and read the full abstract here:
https://gotocph.com/2018/sessions/613

https://twitter.com/gotocph
https://www.facebook.com/GOTOConference
https://www.linkedin.com/company/goto-
http://gotocon.com
#Golang #Programming #ProgrammingLanguages #Erlang

Looking for a unique learning experience?
Attend the next GOTO Conference near you! Get your ticket at http://gotocon.com

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
https://www.youtube.com/user/GotoConferences/?sub_confirmation=1
HN Theater Rankings

Hacker News Stories and Comments

All the comments and stories posted to Hacker News that reference this video.
the question is if an early stage start-up with 4-5 devs where they typically already struggle to get basic CI in place ... and where 1 of the devs loves K8 and the others don't really know it (but don't object because it's nice to have it on the CV), whether they should really already focus on orchestration and scaling before they even have a MVP.

I'm not against k8 per se, but its complexity isn't something to ignore. It's all good if you have the people to run this but most places I know don't.

I think we have reached peak k8-hype last year when F. Campoy at GOTO suggested to wrap K8 around GO to make Go as resilient like Erlang/BEAM (see video below ...) https://www.youtube.com/watch?v=ScE9TnoWltA&t=1437s

as for ML I really think there are cool use-cases, but why would a pre-MVP start-up already be talking about hiring data scientists, ... when they don't even have any data (exception being they are an analytics start-up obviously).

this is how you get ants.

geezerjay
> the question is if an early stage start-up with 4-5 devs where they typically already struggle to get basic CI in place ...

Nowadays it's super easy to setup a CICD pipeline. The basic settings and intro examples alone are enough to build and publish container images to a container registry.

> and where 1 of the devs loves K8 and the others don't really know it (but don't object because it's nice to have it on the CV), whether they should really already focus on orchestration and scaling before they even have a MVP.

That doesn't make any sense. Developing services to run on kubernetes is a software architecture problem, one which only affects some minot dev level details such as supporting env variable settings. Devs can be entirely oblivious to kubernetes and still be effective.

> I think we have reached peak k8-hype last year when F. Campoy

That's largely irrelevant and misses the whole point. Just because some people present some gimmicky take on a technology it doesn't mean the fundamentals are not good. Kubernetes allow distributed services to be deployed transparently across multiple providers (thus you are not held hostage by a seller), and allow services to automatically scale horizontally with demand and within resource limits gracefully degradate after that point. That doesn't go away if someone decides to reenact Inception with buzzworthy technologies.

Here is talk that elaborates it. It's obviously not 1-to-1, and there's other gotchas but there's convenient tables comparison linked directly.

https://youtu.be/ScE9TnoWltA?t=1792

just use Erlang/BEAM[0]. I love Go but it's a poor[1] tool for building truly resilient distributed systems. the workaround suggested by F Campoy seems to be to wrap K8 around go to make it more like BEAM (see second video below ...)

[0] Erik Stenman - BEAM: What Makes Erlang BEAM - Code Mesh 2017 https://www.youtube.com/watch?v=FonRzASOkZE

[1] GOTO 2018 • The Robustness of Go • Francesc Campoy https://www.youtube.com/watch?v=ScE9TnoWltA&t=1437s

May 05, 2019 · 4 points, 0 comments · submitted by cconroy
HN Theater is an independent project and is not operated by Y Combinator or any of the video hosting platforms linked to on this site.
~ yaj@
;laksdfhjdhksalkfj more things
yahnd.com ~ Privacy Policy ~
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.