What an interesting presentation by one of the GOATS

This means a lot for me, Thank you!

This Talk is a very simple and easy way of explaining the core concepts

SerGAY

this is just plain beautiful.... sort of like duck typing

Here before 2022

This talk helped me to pick up some first steps in Go by comparing it with my current main language (java). However I think that in this talk is comparing apples and oranges. We're comparing a full blown spring boot implementation with a pretty plain go implementation (as far as I can judge that). So a bunch of the arguments made feel "forced". examples: - In java / spring you can just return a string (an array of bytes) in a rest controller - You're not forced to use the annotations you can use ResponseEntity to gain more control and if you like even deeper control, hell just program against the http connection if you want. - The package/folder structure of the java application is pretty dated package by component and not by layer, you're not forced to use service, controller, dao naming. The displayed implementation is far from OOP. If it would be object oriented i'd see a domain object on which you invoke methods to execute logic. You can create meaningful components and give them a decent interface, make your code transparant by e.g. a ports and adapters architecture. Point being here, I don't feel like this is caused by the language but rather by the inexperience of developers in the design department. I can make shitty designs in any language. (could be because the talk is from 2018, but i doubt it) I just feel like the delivery in this talk could be better by not going so black and white. Needing to make false statements to make a point when there is none to be made. Anyhow, I took a couple of things away from this talk so thanks for that! And take the above as honest feedback, I'm in no way trying to defend "my language". I'm looking into learning go, so it's too soon to say which one i'll like better. The most correct answer to that question is probably "it depends on the use case, i just have one more tool in my toolbox".

Very good talk. But why not use frameworks if they makes life easier 😑. At least logging and opentracing is a must be imho

Very good talk.

26:15 Only problem that I have with this talk is that this code is so small and hard to read that I must guess some part of it. Otherwise, very good talk.

How someone dare to say kids language and all, about Golang. See it is 100 times faster than Python with built in concurrency. It is kind of C language of modern times and see the great people behind i.t

The recommended Go talks in one playlist: kzbin.info/aero/PLJSvlSLaxm_qEGubbNodHDEzCH3TbSYsO

Not a bad talk but quite biased

Nothing magical about Java annotations - if you understand how they work and the underlying e.g. GOF patterns. The "Java bad" slide really doesn't wash at all. BTW compiling to a little binary is so 1989.

37:15 recommended KZbin talks: Go Proverbs by Rob Pike 7 Common Mistakes in Go and When to avoid them by Steve Francia Best Practices for Industrial Programming by Peter Bourgon Advanced Testing with Go by Mitchell Hashimoto Things in Go I Never Use by Mat Ryer Programming in Go by JustforFunc Francesc Campoy Go Lift by John Cinnamond Twelve Go Best Practices by Francesc Campoy

Very good ! Thanks !

LOL Go is a kids version of javascript. Try write a kubernetes in Javascript

seems like some things in the talk are not a true. He said you have to use interfaces in order to override "parent" methods, but how about methods shadowing? It works well without interfaces. The question about constructors and "why Go works well without it" it's a bull**it, because he didn't show a default value for pointer, he created a new instance of the Car structure and took the address to it (car := &Car). var car *Car; printSpeed(car) will throw a panic because the variable car is nil and this is a true usage of default values in this example and there is no difference with Java

whomever commented on Go to be a kids language... maybe writes Assembly x86 manually for food.

great talk!

The guy who asked the first question showed a tremendous lack of knowledge and was very condescending calling Go a kids language.

08:10 Inheritance 09:50 Polymorphism

though i do believe there’s no such thing as a ‘bad’ question, that dude’s question at the end came off as very ignorant, arrogant and disrespectful - a ‘kids’ language, seriously? please: enlighten us simpletons with what your definition of a so-called ‘kids’ language, even is. i think he just wanted to hear himself talk, just like i want to see myself write this stupid comment.

Great talk: why apples (the fruits, not the lifestyle corp) are better than oranges. It would have been a big improvement to the talk if the speaker would have explained that there are different flavours or interpretations of oo, but unfortunately he seems to be stuck in Java? Another big improvement would have been if he would have applied Go's interpretation of oo (and it is also oo, unless you only see exactly one narrow version of oo as oo) to different types of projects. Then suddly the Go way isn't as easy, as some years of industrial and post-industrial practise might have to,d him before. Imho, a mediocre talk that does Go more harm than good. But time will tell.

Nice comparison. The speaker is good at explaining the differences and why Go is better.

getting a lot of inspiration and direction from this talk. Thanks DevFest

GUI

Cross platform still requires the developer to learn java/kotlin and Swift/Objective-C when handling NATIVE APIs like bluetooth,gps,connectivity, battery,nfc, and etc. I'm working on a project that can access Google Assistant and Siri in a Memo App. I had to work up with the Android & iOS integration using platform channels. I'd recommend cross-platform for UI-Logic Based apps

Great speech about an important topic many organizations take for granted.