The Why of Go 

Unfortunately green threads are not the be all end all - they have their own issues. Early Java had them, and abandoned them. Other newer languages too, e.g. Rust tried them and opted for actual threads too.

Yeah right. No generics, inefficient utility-functions for basic things like finding the length of a slice, horrible code origanization (everything that has to do with text, both io and basic strings is containted in the same module), insanly rigid and basic concurrency model, and it's simply just ugly, like python. Who the hell would put Python in the cathergory of great programing languages. Also, nil everywhere. It has no exception nor error handling so you have to return errors everywhere and check for them. To even suggest it is a great language, what were you thinking? At best, it is an ok tool for small apps for people who like corky weird stuff that is very imperfect in nature. The this needs to stay as a niche and never ever be considered in real app development.

Rust > Go

@@uziboozy4540 rust is pozzed

@@TroenderTass What do you prefer over it?

@@pubsvm7355 ☕ my dear friend

the 1st rule of PCJ is you don't talk about PCJ outside of PCJ.

1.25? Noob! Pros go 2X

@@taliluvhengo5928 2x??? Amateur, gods use video speed controller chome plug in get on the 3x speed or more, time has invaluable don't waste it watching things at 2x

@@hipstergod haha cool. Will check it out

same. I set it to 1.25 and then forgot that it's already at 1.25

God bless you sir, I was about to close the video :D

True about node. Java is so bloated and being run by oracle is a big turn off for a lot of developers.

I might wonder what made it so slow. Have you tried the same with swoole Coroutine?

tbh, you very rarely need to pick a character by its absolute index or offset. Most real world text processing tasks need iteration, one character at a time, and in this case there's almost no difference. For UTF-8 it would require a bit more processing (like calculating whether it's the last byte of the character) but it's negligible and can be hidden in the iterator logic. Go's range does exactly that (in the form of "for _, c := range str" where c gets the next rune aka unicode character) and it's implemented in the language syntax itself, not even in the standard library.

Well said broski

All religions are built-up myths over a basic set of life questions. Choosing a religion is accepting the myths presented in that religion. Everything else is programming.

Gerard Gauthier absolutely not, metalanguages and LISP dialects operate are entirely different than static languages. The difference between dynamic and static languages; intermediate verifiers and proof oracles, makes each language a different ‘flavor’ of the IPS

Wrong, "accepting the abstractions" is a way not a whole story, there are much more properties to consider. You have a very narrow understanding of the subject.

@@dracoford755 Oh yeah! I keep forgetting that LISP resides in the realm of magic and not algorithms and hardware. Like I said... religion.

If you are interested in more content about Go you can check out the dedicated page on InfoQ www.infoq.com/golang

Bruh

You don't have to change your stack. Have it as one of your tools.

How Carmen Andoh say in this talk "Go isn't about revolution. It's about simplicity.", I think this pretty well sums Go. If you need language that is clean, simple, elegant Go can be very good choice. If you want something new, you need to check other languages. "I could just as much use another language and turn off language features with a build plugin." I guess that createors will respons along this line. "Yes, you can. But this is unelegant workaround, also can be very unstable. We want elegant language from the start.".

you are correct, but simply "turning features off" is not really something you can expect when dealing with someone else's code. the point of go's forced simplicity is meant to facilitate maintainability and readability, not only when revisiting your own code 1 year later but also to pick up other people's code.

Just try it. Simple language, way more than the sum of its parts. Learning it is more exciting than you would think. It doesn't need defending.

Go to other languages is like comparing CISC to RISC or is it RISC to CISC?😊

A good PHP programmer can, (with a little effort) become an adequate golang programmer. (I doubt that they would ever manage to become a good Erlang programmer.) If amazing things like Erlang, Haskell and Scheme were easy then we wouldn't need the {idiot} "languages" for children like PHP and node.js

​@@recklessroges care to elaborate why these are "children" languages? you know that there are billion dollar companies running on this langs, right?

People give props to Erlang all the time. That’s a lot different than saying others should use it. I would personally say Elixir is more receivable by a wider audience but it still doesn’t have as much weight behind it or anybody pushing it or … essentially marketing.

oh yeah this channel is so crowded

_lol_

Oof!

why?

Spaghetti code language

Not in the map but she talks about it. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-bmZNaUcwBt4.html

god bless her

Go has pointers.

@@RyanMartinRAM Yes of course, you can just write p := &i to get pointer p. But it dosen't have pointer arithmetics so code like varArray := [3]int{0, 1, 2} p := &varArray p = p + 2 shouldn't work.

Wow. That’s what I was thinking 😂

She hasn’t provided any coherent logic behind WHY. Yet the talk seems interesting 😝

Hello Zen Shinmae. About your first question, they both solve different problems and you can actually implement many concurrency models in Go. Language supported green threads however create a common language for implementing many concurrency models, it's a productive system together with channels, and they enable you to write your code synchronous first. It's encouraged in Go to write all your code synchronous when possible, which makes it trivial to make sure it's correct. Then making it work async is something you can do really simple with the Go language support, similarly to running a task in the background in Bash. About errors, it's tedious but extremely necessary, and it avoids your code blowing up all over the place. That said, your prayers are heard and a first implementation of a less tedious way of handling errors without giving up the safety Go errors give is in the works for Go 1.14. But also, Go errors are just values, so you can program with them and handle them however you want. Rob Pike has a great article about this. It all boils down to many things she said in her talk, but you will have to try out and experience the difference to know that she is not talking nonsense.

You clearly missed the point

You're right. But to her defence, she's more on the business development side of things and not the design and architect side. Her speech is more like a college essay and presentation.

Rust people be like 😂😂👌

@@ezengondolkozom3700 To be fair we have all control flow as expressions :D

Fuck you and the memes

pokemon GO to the polls

Agree with you sir ☺

Good luck with your C++ servers and your dangling pointers mate.

It's not a great speech but that wasn't her entire point.

1. - "The real reason..." How do you know that? Your fragile ego of a self-claimed C++ guru doesn't automatically makes it "real". 2. Apart of your passion to some nerdish stuff and eltism of all kinds, your whole point makes no sense here (again), hence Go has NEVER been positioned as one to replace C/C++. That's why: Go: readability; maintaiability, fast compile/deployment time, simplicity, robustness etc Vs C++: relatively hard to read; HARD to maintain; slow to compile and a way harder to deploy(no single-file binary privilege); R E D U N D E N T ; extremely easy to break things etc * Go has a GC which makes using it for performance-critical parts of an app even more absurdish. 3. Your ignorance multiplied by arrogance is really annoying, not the talk she gave. 4. Go is the reason I'm going to spend more time enjoying my life, instead of sitting in a shape of an S debugging some 30-y-o legacy code 🤣🤣🤣

C and C++ are definitely not the answer to write correct and safe programs simply. Whether Go delivers on that promise is an entirely different topic but the motivation behind it is more than justified