no, blue hair = rust developer. He had to switch to Go otherwise he would be trans by 2025

Dyed hair blue to become a real rust developer, ended up identifying with the gopher so much that golang is his main language now

@@AJewFR0 The Foundation is clearly suffering from it.

Blue hair is rust bro 😅

@@susiebaka3388 Yep. So is the agenda.

There's something very beautiful about this. When there's often only one path available, you just don't have to think too hard about the minutia

​@@ThePrimeTimeagen ewww, that sounds like python. Gross

​@@RossDmochpython is a lot different from golang 😅

@@susiebaka3388 WAYYYYY different

Is python known for doing everything one idiomatic way?

😂 That's a generous way to say it!

Nice find! 'Complexivity' is a great word indeed 🤓

Gobblin up the GoC

I am with you.

Interesting perspective! Rust's expressivity vs complexity impact on human behaviors is a fascinating topic. Looking forward to your insights on Go's unintended consequences.

Where does Go go?

@@patrick_jane its going no where for prime

TypeScript, Go, Rust. Polyglot programming.

@@patrick_jane the places Go goes continues to grow as time goes on

Rob Pike knows Go is the go to language for a lot of people to the point that he has to put goto keyword in it

Living is a skill issue

Thought he said a scale issue

Agreed! Modal design can be tricky. Here's a simple fix: .modal { width: 400px; display: none; position: fixed; bottom: 20px; right: 20px; padding: 20px; background: #f9f9f9; }

A lot of the crazy typescript types are necessary to type the things people are used to doing in JavaScript. You can do basic classes and data types and only do that if you want, it's just that people are used to certain (more convenient) patterns from JavaScript.

Matt Pocock is trying to polish a turd , and guess what? It’s still a turd!

Ah, fellow over-engineer! 😅 Go is great for simplicity, but we all struggle with it. 😅

Yep, felt real

Nice! Here's a suggestion for the background color: #f9f9f9.

It’s not

I think that depends how you are extending the slice. It's just a pointer to an array plus a size...

@@Rakstawr there is an append function, it returns a new slice. Append to a slice, whos capacity has not been reached, and you get the original slice back, just with the new element appended. However, if you append to a slice whos length is equal to its capacity already, then Go creates a new slice, that contains copys of the original slices contents + the appended element and a new capacity. instead.

I understood slices much more as I used them in Python and there is a lot of .

⁠@@AScribblingTurtlethe capacity isn’t referring to the slices, but the underlying array. Slice is really just what the other user described

​@@AScribblingTurtleI mean it's pretty obvious. Slice is just a reference to an array. And an array is a continuous block of memory, so if you append and it exceed the memory, you can't just put it in, it will override some memory blindly. So you have to create a new one.

Wow, you've come a long way since your early Go-bashing days! 😊

A pity that Go has a lot more drive behind it from employers

Sorry to hear that! 😞 Can you tell me more about why you think it's a rubbish hammer?

C# .NET ftw

Context always matters, I think he's not challenged enough. Also C# NET ftw :')

This the arc we're all waiting for Visual Studio Enterprise C#

C# is like a duvet

C# is hot u know today

Ah, I see! Many Java devs find Go's simplicity refreshing after dealing with Spring Boot's complexity. 😊

That’s my case. I’m a Java dev and I feel alright about Java itself, but this obsession with that awful Spring thing is just sick. Spring is a monster gobbling up your development time, totally broken and undebuggable, and Golang is a refreshingly beautiful ecosystem in comparison. One of the best things about Go is that there’s nothing like Spring there

Nice catch! 🤯 That's a clever design choice.

Too good timing.

What kind of projects do you do in Go, I am starting learning but I don't have idea what to build because my mind is so immersive in Frontend but I need a change

@@enzocam07 I started with some simple webservers. Replicated a few things I did in JS. Then I focused on a smart alarm. A replacement for an alexa echo dot with a raspberry pi underneath. What I also want to are some GTK-Desktop apps. Mainly to fill in blanks in my workflow I haven't found tools for that I like, and to learn a bit more about desktop-programming. Even tho go might not be the best for that, it still is better then electron.

Impressive your journey. What’s the the main or top 3 ups of go compared to the other languages you handled?

@@mauricioramirez2855 I just like the language which helps. But if I had to pick... Errors as values, the standard-library, and simplicity. honorable mention to god-tier concurrency, BLAZINGLY(tm) fast compiles and the elegance with which you can solve a lot of things.

I'm kinda of migrating from PHP and Laravel to node because of a job and I'm really enjoying it. But I'm thinking about giving Go a try to see if I like it. The thing is, there are some details that scares me like pointers, bc I did not had a great time learning that on college lol. I wanna see if Go is all that great like everyone talk about

@@porfiriodev pointers in go is simple, you don't need to think of them too much, because of garbage collector. Just understand what it is and when to use it and that's it

Wow, thanks for the kind words! 😊 Glad to hear that my content has inspired you to switch to GoLang. Good luck with your new journey! 🚀

No, mocks in test in Go are GREAT! You can mock as little as what you need for what you want thanks to duck typing. Maybe you're using it wrong based on your previous experience on other language (I know I did for a while). If you can share more, I'd be happy to help.

I got the same thoughts about syntax and readability. Can you recommend some approaches to start from and clear old-used-language brain?

@@bot1511 It would largely depend on your background, but nothing really specific beyond just "use it". Once you start creating more complex applications beyond tutorial-esque examples (might have to just slog through it at first), the design choices, which seemed odd begin to make moe sense and feel natural. Other things like the order of types/variables just need to overcome the muscle memory of doing it the C-style way. Embracing the "functions are first-class values" and "composition of inheritance" paradigms and using them effectively also helps break the old habits.

Even PHP has that now.

dart has it too

@@razvangrigore322 PHP.. no joke, is actually quite nice now.

Agreed! Rust's enums and match features are top-notch. 👍

Haha, I see what you did there! 😂 Thanks for the feedback!

Elixir is cool. I spent all of december and january using it 10-20hrs / week. i’m sold it’s the solution for small teams. Phoenix is Rails but better.

Undoubtedly the best? Have you compared it to Lisp, Clojure, Haskell, Ocaml and Rust? I haven't tried Elixir yet, so I can't make a comparison myself.

Elixir doesn’t have types, which are a must have for most people

@@harrybarden5438 So everything's a string? No arrays, no numbers, no hash tables?

Yeah Elixir is the best lang.

goto golang;

According to Google's website: « Go was designed to address the problems faced in software development at Google [...] The goals of the Go project were to eliminate the slowness and clumsiness of software development at Google, and thereby to make the process more productive and scalable. The language was designed by and for people who write-and read and debug and maintain-large software systems. » So, maybe... large software systems at Google?

Perhaps that's where you shouldn't use the language. It is a language designed for the web, writing servers, and clis. So using it outside of that bounds I'm not exactly sure where it fails

​@@ThePrimeTimeagenebiten is a pretty nice game engine for go, though.

Maybe try raylib with the go bindings?

@@Pabloparsil Maybe! I've been following it for a while and want to try it. Do you have experience with it and Golang?

@@amodo80 It's OK but it gave me a lot of pain actually. That's the library I was referring to. The shader system is kinda bad and dynamic audio synthesis is extremely laggy.

There are a number of reasons, granted they may be subjective, but they aren't trivial either. My main one is the concurrency model, namely goroutines and channels. For me this makes it a lot easier to write concurrent and parallel programs compared to using manual thread management in C or C++. The second main reason for me is the toolchain - for testing, profiling, debugging, and dependency management, etc - along with the go command and gofmt, etc. All in these promote a super consistent and efficient workflow. So whilst it is certainly true that C and C++ may be "fastest" and offer greater control in certain scenarios, Go provides a much better balance of performance, safety, productivity, and scalability.

go is far easier than c++ and rust is for bragging rights

speed isnt the most important factor depending on the situation

You have two options - use pointers like *int, *string, etc and if the value is NULL, the pointer will be nil - so you check "if x == nil" etc. Or use option types like sql.NullInt64, sql.NullString, etc then and check for validity "if x.Valid" etc. Both approaches have their pros and cons. Pointers are more "idiomatic" for simpler cases, while option types provide more explicit handling of NULL values. I prefer the option types myself as it feels more explicit.

thanks so much for taking the time to share the knowledge. Appreciate it.@@FraserChapman

whatever you do don't use pointers it will make your code disgusting to read

^^ glad to hear

Your problem is that you are trying to not use go. Generics really isn't the end of all things.

Similarly true for java and c# as well.

100%

I actually find Rust has less of that problem for me than Haskell. It's because the type system is slightly less expressive, at least, without macros. However, in C# I find myself spending too much time wondering what the simplest way to do something is, because it's so low-level that the simplest way to do something often looks complex. So it ends up being a different kind of type masturbation. I'm very happy with Rust so far. (I started using it this year.)

Same with modern c++. Main reason why I switched to Go

Thanks, glad you enjoy! C writing is awesome 😊

That's what made me stop C++. It didn't force me to care (like the borrow checker in Rust), but if I didn't want some rubbish program that would poop itself because of rewriting some memory somewhere, I HAD TO care. But caring about memory didn't help me actually writing my program that I needed. Go makes me avoid so much of this pain.

Understood! Here's a concise and human-sounding reply: Thanks for sharing your thoughts! 🤔 Yeah, Rust can be challenging at times, but it's true that it forces you to think more carefully about your code. 💡 Appreciate your input!