The Why of Go

Download the slides & audio at InfoQ: https://bit.ly/2pK6Uwi

Carmen Andoh provides the historical context around the technical decisions of the Go language to better understand its concurrency primitives, garbage collection, and small standard library.

This presentation was recorded at QCon San Francisco 2017.

For more awesome presentations on innovator and early adopter topics check InfoQ’s selection of talks from conferences worldwide http://bit.ly/2tm9loz

source by InfoQ

go programming language

Mourad ELGORMA

Mourad ELGORMA

Fondateur de summarynetworks, passionné des nouvelles technologies et des métiers de Réseautique , Master en réseaux et système de télécommunications. ,j’ai affaire à Pascal, Delphi, Java, MATLAB, php …Connaissance du protocole TCP / IP, des applications Ethernet, des WLAN …Planification, installation et dépannage de problèmes de réseau informatique……Installez, configurez et dépannez les périphériques Cisco IOS. Surveillez les performances du réseau et isolez les défaillances du réseau. VLANs, protocoles de routage (RIPv2, EIGRP, OSPF.)…..Manipuler des systèmes embarqués (matériel et logiciel ex: Beaglebone Black)…Linux (Ubuntu, kali, serveur Mandriva Fedora, …). Microsoft (Windows, Windows Server 2003). ……Paquet tracer, GNS3, VMware Workstation, Virtual Box, Filezilla (client / serveur), EasyPhp, serveur Wamp,Le système de gestion WORDPRESS………Installation des caméras de surveillance ( technologie hikvision DVR………..). ,

49 réflexions sur “The Why of Go

  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    I just stumbled across this video because I'm dipping my toe into the Golang waters. I don't know who this is, but she is a fantastic teacher. I love listening to someone who can explain WHY something is the way it is. That makes it so much more accessible.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    This talk seems to exude arrogance. I was surprised to hear the “appeal to authority” logical fallacy right up front. If go is designed for our new world of multi core and massive parallelism, why does this new and simple language devolve into the sync module and locking primitives to solve difficult problems? Why go?

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    There are not many videos that try to defend Go. So I appreciate this. I must say, I'm still not convinced, I'm skeptical. I could just as much use another language and turn off language features with a build plugin. OK, maybe concurrency is good in Go, but green threads are not unique to Go, nothing new there. Please enlighten me.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    With regards to utf-8 it's not always the best. utf-32 is better if you are working with a lot text in some Asian languages for example, since every character is the same width meaning you can index into an array and know where the characters are. You can't do that with utf8 and utf16.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    She stopped right at the point that she was supposed to tell us how better goroutine is compared to other thread model. Guess we need to read it ourselves, but then why I am watching this.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    33:20 yes nothing can go faster than light but as far as I know there isnt a whole lot of fiber optic in your CPU or ram isnt all data that goes through metal have to be electrons which are significantly slower than light which is why cpus aren't 4000GH/z

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    TLDR:
    hype
    appeal to authority
    it should be faster than a JVM
    straw man
    assumptions about simplicity

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    Is goal of this presentation to convince developers to use go? Is it about go ? I see bunch of random historical and "captain obvious" facts which does not tell exactly "why to use Go:" 🙂 This is presentation about everything and nothing. You can use this presentation, just change arguments to proof that any language is better than others. It's kind of typical to pepople who have some higher technology overview, they dont understand whats going on but they want to sell some idea. She has good presentaiton skills but I have feeling that she is going to sell me something I dont need. As a fan of go language I dont give a shit 🙂 Lost 40 minutes.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    don't waste your time. there is no concrete argument here. it's frankly all over the place.

    I came here looking for reasons to like go, she didn't help. What I would like to know:
    – In practice, what exactly are the benefits of green threads over async programming? I have never used green threads before so I'm very curious about how it actually works in practice.
    – How to handle errors? I do not exaggerate when I say I find it extremely tedious to check errors. This not only slows down my productivity, it also results in very complex code. There must be a better way of doing this (I'm a fan of how rust handles errors).

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    All programming languages are built-up abstractions over a set of basic operations. Choosing a programming language is accepting the abstractions presented in that language… Everything else is religion.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    I've been trying to spend some time to learn Go and I've been enjoying it so far. I see a lot of benefits with Go especially if you use Docker for your deployments. It's so easy to package up Go for docker deployments (because the compiled code is just a single executable lol) and the language itself is quite intuitive and simple. Love the emphasis on interfaces with structural typing over nominal typing. Also, it's performant, memory efficient and there's a lot that's provided out of the box for building any sort of application so it's definitely worth learning Go.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    Worst talk I've ever seen. So much bla bla no actual content.
    It's titled 'The Why of Go' not 'The great big history of everything surrounding Go but nothing about go itself'
    Good talk would have been:
    Show problem > show solution > explain solution > contrast solution with alternatives > Conclude and that's what Go is for.
    This kind of back and forth was a waste of time.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    All the Go's 21st Century Characteristics was addressed by Erlang in 80's /

    Heck maybe Joe Armstrong was a time travel!

    Répondre
  • Avatar
    décembre 21, 2020 à 9:34
    Permalien

    Don't waste your time watching this. Whatever she (and everyone else) is telling, the real reason behind using Go is the lack of C/C++ skills. Look at the slide at 11:47: all five points she makes is the manifestation of a C/C++ programmer's incompetence. And her smug presentation style is really annoying.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:33
    Permalien

    So go combines the best of event and threads because it has thread programming model (not callbacks as in event loop) but channels and green threads are much faster than mutex locks and system calls in threads. That took a long time to come out, I think.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:33
    Permalien

    This video got me thinking about a lot of things, very interesting to think of the design choices.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:33
    Permalien

    I think everything said here is correct, (and even if it isn't, with the massive weight of google behind golang, it is unstoppable,) and I don't mind that. {Please golang, save us from the lame duck that Gosling gave us.}

    Répondre
  • Avatar
    décembre 21, 2020 à 9:33
    Permalien

    You can see that Go was influenced by Modula-2, which also started out as a systems programming language.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:33
    Permalien

    She has an impressive ability to talk while saying nothing.
    But I've still watched the full 48 minutes.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:33
    Permalien

    Nowadays, the core war has been pumping those thread count #s up QUICK (i.e 64 cores on a single dye w/ 2 threads per core on a DESKTOP CPU WITH DESKTOP TEMPERATURES).

    Répondre
  • Avatar
    décembre 21, 2020 à 9:33
    Permalien

    I agree, simplicity makes way and gets you to do the thing you want to do instead of having to deal with side issues. You would have to be either a complete egomaniac or an idiot to fight against it or not see it in that way. Ultimately as programmers we all just want to get to the meat as fast as possible.

    Répondre
  • Avatar
    décembre 21, 2020 à 9:33
    Permalien

    This is not just a great talk.. it's one of THE GREATEST TALKS EVER. So well researched. So well presented. So well argued. If this was a Go file, we need to import "reaction" and use StandingOvation(). Thank you.

    Répondre

Laisser un commentaire