Journey from OO language to Golang - Sergey Kibish @DevFest Switzerland 2018

[@MrBumbolt]

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".

[@TechdubberStudios]

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

[@jackalhu8228]

08:10 Inheritance 09:50 Polymorphism

[@sunilkum84]

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

[@rikyhidayat]

This means a lot for me, Thank you!

[@mauroanselmooliveira]

Very good ! Thanks !

[@t0x1cF4rt]

Here before 2022

[@pengdu7751]

great talk!

[@wizardofb9434]

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

[@kamilziemian995]

Very good talk.

[@mishasawangwan6652]

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.

[@murugansundararaj5002]

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

[@suikast420]

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

[@VictorMartinez-zf6dt]

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

[@dmitrychurkin4077]

Definitely, we must to find and punish him :)

[@Rambou92]

Or maybe the opposite IMO. The question was simple why to use GO instead of JS with NodeJS for server stuff. Sergey seemed unable to answer with confidence that question. The answer hides deep inside the technology between NodeJS and Go. Also the argument that "Go is Safer" was just a "mambo jumbo" answer :)

[@bakedbeings]

@@Rambou92 afaik it’s safer than pure JS in that it’s typed and compiles, giving you compile time errors. Typescript exists for that reason if I’m not mistaken.

[@ppang]

IMO he failed to respond with a better answer. The most critical advantage golang has over js is better multicore utilization, static binary generation, cross compilation for multiple architectures.

[@arcticape445]

@@ppang i would argue Typescript is even safer due to it’s much stricter and advanced type system and algebraic data types

[@user-qt4ml9ft9e]

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

[@lorenzopiersante8791]

Yeah i was testing it and this code just does not work at all lol You cannot instantiate a struct with unexported fields outside his package. And if you are inside the package unexported properties are accessible anayway so you are not encapsulating anything with the getter method but just duplicating stuff for whatever reason

[@nuno2324]

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

[@shashankbarthwal8547]

Thanks for this! :)

[@kevinjom1117]

Not a bad talk but quite biased

[@albertgao7256]

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

[@kamilziemian995]

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.

[@TheDiveO]

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.

[@bradleyheath7277]

sorry to be offtopic but does someone know a way to get back into an instagram account..? I stupidly lost my account password. I appreciate any tips you can give me.

[@bradleyheath7277]

@Onyx Harper it did the trick and I actually got access to my account again. I'm so happy! Thanks so much you saved my ass!

[@onyxharper6538]

@Bradley Heath happy to help :)

[@Faruox]

GUI

[@wWvwvV]

We use QML+GO as an OpenGL GUI for POS (Point of sale). Cheap hardware but still fast.

[@csgrinds]

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.

[@shiskeyoffles]

Well, it's the ability to cross compile and make it work seamlessly

[@csgrinds]

@@shiskeyoffles Pls qualify

[@user-dz6il2bx5p70]

SerGAY