go is great i hate it

you can deploy go lambda functions with sst now

[@radfordmcawesome7947]

I hate being bipolar, it's AWESOME

[@fadichamieh]

I love hating this

[@QuebnQ]

I still dont know why dax doesnt have a yt channel.

[@ypathan420]

bro's busy building actual stuff

[@iykazorji8171]

Thanks Dax, just convinced me to finally take the plunge and learn Go!

[@Kane0123]

Yep. I could see myself using it as a direct result of this video.

[@JeffreyRennie]

The Go standard library lacks FIFO queues, double-ended queues, priority queues, sorted maps and sets. I sorely miss them when I have to write Go.

[@rupen42]

Coming from python, I also miss things related to randomness. Pick a random element from an array, pick with weights, pick repeatedly, shuffle an array etc. All aren't too hard to implement yourself from the RNG in the standard library, but it's nice to have them built-in.

[@alexandrep4913]

You silly gopher, you love us.

[@filipg4]

Go being "dumb" is its biggest upside. When you give programmers fancy tools to avoid problems, they will get themselves into subtle more dangerous problems. All styles of programming work at the small scale

[@dovh49]

I really like V which is heavily inspired by Go, but it has some syntatic sugar that is nicer and it just compiles down to C. It's still beta software so it have a long way to mature still. but I really like the simplicity of the language. I've gone through some of the tutorials for Go, but it just seems like a bit of an awdward language to write it. If I did it for work I would learn it a lot more.

[@Schematical]

I need to get on playing with Go. I hear so many good things.

[@ForeverZer0]

Go's best strength is how absolutely simple it is to learn, assuming you are generally familiar with programming. With no exaggeration, you can go from knowing absolutely nothing about it to writing complete and useful applications within the same day, just consulting some docs/examples for the syntax along the way. The tooling around it is just as simple, and everything you needs comes included.

[@melodyogonna]

Go is mid in many things, but when all these mid parts work together it is hard to beat.

[@snoupix3332]

As a Rust dev, when you say "it will be a lil bit slow" when you cross compile your hello world, it kinda makes me cry that you consider 1.8s "slow" compiling :')

[@koteelok2014]

Goddamn man, your beard is 10/10

[@sameershahid9775]

Well, I am mainly using my primary language for the backend, which is actually Go.

[@OetziOfficial]

Nice, I can finally switch one of my projects to sstv3 :D

[@nisem0no]

Please make an equivalent video on Rust? I'm just curious what your thoughts are after years of using both Go and Rust.

[@MisterKitKit]

i think it's awesome you support Go now. Still I never faced a use case actually using it :( basically all my lambdas are i/o driven so node makes sense most of the time. When do you think does it make sense to use Go over Node? For cold-start related problems? I think those are problems for systems with no users, so what are actually good use cases? Would love to hear that

[@nesssel]

Why is Node better for IO-driven apps?

[@ebukaume]

@@nessselbecause it is 😂. Can we get back to his question?

[@nesssel]

Go's concurrency model makes IO and networking so smooth, so to me, there at least even. I don't see what node does that's superior that you'd just discard any alternatives. But I'm guessing it's just your experience...

[@ebukaume]

@@nesssel good answer. He may have gone a little extreme by saying Node is the best for I/O bound apps. But given that Node is very good with I/O bound apps, what then would be his motivation to rewrite his apps or use Go for newer ones? If you ask me, reducing cold-starts plus faster execution might be a reason. Saves money, no matter how small. It might not seem significant but given that Go is easy to learn, might worth it. As for me, I will stick to Rust for most personal usecases (for now), Golang for a team (most ppl don't like going deep 😃) and Node (TS) when I am forced to 😃.

[@Salloom99]

DO MORE PLZ ❤

[@pedroalonsoms]

Go has a lot of advantages that I like. The biggest disadvantage I see currently is the lack of community packages, JS ecosystem is just superior there.

[@AlexGarcia-ir7fl]

Go is designed to discourage the use of third party packages. If it ain’t bringing substantial gains, don’t import it. YOU can do a better solution for YOUR specific problem.

[@pedroalonsoms]

@@AlexGarcia-ir7fl yes, but if your use case isn’t covered by the standard library then you are cooked

[@Kane0123]

Cooked is a little strong considering you can still import packages.

[@hello19286]

@@AlexGarcia-ir7fl Every dead language/framework uses this excuse. Oh we don't have a lot of packages because we are all 120 IQ and are all solving brand new problems!

[@nyashachiroro2531]

What packages are you missing?

[@florian6687]

Thank you dax

[@rupen42]

Go would be my ideal language if it had (1) immutable by default variables (or val vs var like in Kotlin) (2) Result / Nullable types (3) a good convention/culture for variable names instead of the dumb single-letter variables. Seriously... those single-letter variables get warnings from so many linters in so many languages, but somehow became the default in go. Who let this happen?

[@ForeverZer0]

There are indeed some strange naming conventions for variables, arguments, etc. in the stdlib, which by extension has become the convention for the entire ecosystem. I am mainly a Zig dev, which is all about making everything explicit and verbose to convey intent, and it is jarring when I make a switch to Go and everything is using single-letter names and abbreviations for words that are already short. I can get used to it, I pretty much always just follow conventions for whatever language I am writing ("when in Rome"), but it never feels nice using "r" to describe a "Reader" etc, especially when its is part of a public API.

[@vasiliisisilii]

Влад Тэн одобрил этот видео

[@lifespell-omega]

go is too simple to a fault in my opinion. there's just so much more boilerplate and it's painful. for simple scripts and things like that it's nice, but to build a real application is just pain.

[@MisterKitKit]

just do Rust support

[@ИванРагозин-я8я]

LOL RUST ONE LOVE

[@baracjohn3913]

I can’t stop thinking about “are you happy with your indians” now that I’m watching this

[@magnusred2945]

LLRT support please