@coralsikes4718
the blue hair was the Go foreshadowing
@keyboard_g
Prime C# dev 2025. Lets go.
@thesaintseiya
Love your take here, as a relatively new dev I'm currently learning Go and loving it, but I'm super excited about learning Rust next year. I love this idea of dedicating time, like a full year or two, to explore and get good at different paradigms and that's what I'm doing
@thaddaeusmarkle1665
"complexivityness"... Learned a new word today
@markhaus
I think this is a pretty great way of going about learning about the mysteries of how humans and teams of humans think about programming. Most languages have unintended consequences as a result of certain design decisions that eventually become crystalized and hard to avoid as it matures. I don't think a lot of people really know if the amazing expressivity and less than amazing complexity of rust affects the human behaviors of programmers working with it without trying something completely different like Go. I'll be following along and will be very curious what some of the unintended consequences of the decisions made during Go & Rust's development get uncovered.
@k0rnburn
I like D because it has both sides of the coin somewhere in-between of Go and Rust: you can start writing in a simple way very clean and fast with GC and simple structs.. And if you need to make some tricky magic - welcome to metaprogramming world with traits, mixins and templates. If you need even more speed - you can even disable GC and write your hot part with asm and great auto-vec support from GCC/LLVM world.
@AScribblingTurtle
Go is pretty fun. Cool, that you give it a serious chance. I love it for prototyping and testing new Ideas. You don't have to worry to much about types, to get things working, but once you want to tie things down, you can type things as strict as you want. The only hard thing to wrap my head around was slices. Once I realized that a Slice that is extended over its original capacity becomes a list of clones instead of references, everything was OK though. Until you extend a slice over its original capacity, all elements in it are references to the original entries, allowing for some pretty fun stuff, when building multiple slices from the same base Array.
@yugioh8810
I feel like lots of Go programmers are ex-java programmers who have never did professional programming outside Java (like yours truly) and once they did the shift to go they were impressed by the simplicity of the language, bear in mind half of java is spring boot with all it's features and complexity so it adds more to the complexity and abstraction you have to deal with.
@scofield117
“Your app having complexity that is unmanageable is a skill issue” amen brother
@HumanoidTyphoon91
Commenter: Just use whichever language makes you happy Prime: TRIGGERED
@unl0ck998
Type masturbation is hilariously accurate
@hakooplayplay3212
Prime, you actually one of the reasons iv switched from being node.js developer to Golang dev. Im happy and want to thank you!
@Julzaa
Looking forward to it! I've been gobbling up your Go content
@tessoir
I really like how there's a word "brain" in his transparent head on 5:40
@re_detach
Go is my goto language because it goes
@alexvass
Thanks
@JerredWernke
I have been writing php code for years. I starting to use go whenever I can because of how simple it can be to learn and all of the powerful choices it has made for a language go is really good and I want to find a way to write more Go code.
@scillyguy
"This chisel is a rubbish hammer"
@fr0xk
Go builds and runs on almost anything—any OS, any architecture. It cross-compiles from anything to anything, statically links during cross-compilation, and doesn't care about glibc, bionic, or GPL drama. It has a built-in concurrent garbage collector and comes with everything you need out of the box, handling 90% of what C, C++, or Rust can do without the headaches.
@taylorallred6208