I learned the Go Programming Language 👩‍💻 #coding #coder #programming #software #technology

The road to hell is paved with `pip install`

'pip install add-two-numbers'💀

The error handling eliminates try/catch hell. It reduces readabilty because you are actually handling errors

😂 The sound effects and editing when you mentioned the Python and JS packages situation just had me

I learned C++ as my first programming language... My keyboard is still traumatized to this day..

I code for 16 years, using PHP in the begining and Java most of time. So error handling and concurrency is part of my daily routine. However, I have to agree, error handling in Go is cons and pros at same time. I start thinking I was coding in 80s, then I understood we should never leaver 80s coding style on error handling aspects.

I started learning go this month and i love it. My first language was C

I also use to hate the error handling, but it makes more sense this way. I can’t go back to try/catch.

Go? More like goat, like lewis.

go stdlib is minimal yet so so so powerful

Lack of packages is a good thing in my book, since it encourages you to write your own implementations instead of gluing packages together, while still having the most important ones i.e. web frameworks, Markdown parsers, Raylib, etc.

The error handling is pretty great. The Lack of packages and comprehensive documentation for beginner is the current issue i think

It took me five days to learn Go to the point where I was able to create a project that was used in a massive content delivery production environment for five+ years.

"Errors as values" the best part of Golang syntax! But for me it's mainly the performance, pay less for hosting APIs.

kotlin next would be amazing. Its java but better. And its *advertised as 100% java compatible BUT it really sucks so your standered and external libraries are not fun. But use it for general purpose not just android apps

"Just use the standard library"

I actually prefer errors as values over try/catch. So much that I started using this paradigm in JS as well. When you throw, you sometimes forget to catch, and sometimes you don't know where it's caught and how it's handled... Maybe it just throws again and isn't cought at the top... I just prefer the safety of returning errors. Especially since TS lets you safeguard your actual return values so they stay undefined before you handle the returned error. Ever since I started doing this, I NEVER had a reference or an uncaught error... Think about that...

In Go errors feel so much more like information Maybe it's possible to do so with try catch, but I've never felt this experience of like, "something went wrong, but I know how to recover from this error" Like errors truly feel like information, I made quite a few custom types because it's just so nice to describe why a massive function went wrong It helps your code rly decide what to do abt it

Bro was like: the con is I have to do the programming 😭

0:04 that hand positioning seems like a RSI waiting to happen ?! 😮