Golang is BAD for SMART PEOPLE

Why bother reading some russian creep nonsense?

Is it just me that I find Go ugly visually?

Go = {}, if, else, for loop, async tool

"Goggle", lmao you killed me

writeln throws an error in the catch.. Ownoo...

Meanwhile c# … var text = File.ReadAllText(file);

This was painful to watch. I don't know how you could make so many videos about Rust and be so positive about it and then make this video. The 2 languages are nearly polar opposites, and Rust is so, so much better designed than Go. Sure, JS does suck, but even TypeScript has a significantly better type system than Go. Go's type system is literally trash. The argument that you can get things done faster in Go is weak considering you're much more likely to produce bugs and tons of duplicated boilerplate code due to the weak type system and lack of language features for abstraction. The goal isn't to spit out garbage as fast as possible. It's to write correct code that's easy to maintain and easy to refactor when you need to make changes.

Confusion is definetly a feature of some languages

Just watched a video of a google guy that said he uses java and c++ for internal microservices

I would have used Go for my new project, because of the simplicity and fast compile and run test cycles, if it had support for extension methods. So I ended up going with Dart instead. Dart is also simple like Go, but not quite as simple, it has some of the things Go is missing without getting too crazy. It also can compile to and run on many different platforms, and has a fast compile and run test cycle like go. Dart has turned into, basically, a modern, better designed Java/JVM that can also compile to JavaScript. With Dart, the compiled executables have a small Dart VM inside them, so it doesn't put the burden of runtime environment/version on the user like the JVM does.

elitism

I was writing PHP, JS, Python and my code was shit. I tried Go and now no matter how small-brainer i am, my code is amazing. Why? Because in other languages there are people saying how you should and shouldn't write code with little to no examples, yet they say it ever so often and mostly contradict each other; whereas in Go land, people don't have an opinion on anything. Go already decided for you how you should write code and enforced it with its syntax and std library. Wanna inherit something? Think again. Wanna throw an error in a random place? think again. Wanna make some multithreaded code? don't think, you stupid, you can't do it, just use go and we'll do the rest.

Confusion engine😂

Yeah the point in coding is usually to make reliable software quickly.
Not an academic circle jerk.

such an example of a reactional streamer jesus chrust

What are the 4 hard cases of go channels?

Golang has a fatal flaw, or so I've heard, which is why I don't think I'll try it.




It doesn't compile if you put the { on a new line after conditions/functions!

Confusion engine 🤣😂🤣😂🤣

Just started Go 2 days ago, I write TS for my job and embedded C on the side for fun.
When I learned about goroutines and saw how it took 2 minutes to implement very elegantly something that had taken me 2 weeks to figure out and build (still not working properly) in Node.js... I jizzed in me pantaloons

Moving from C# to GO feels like a downgrade. I had to deal for about a year with GO code and i still cannot get used to it.

If statements are always better than ternary operators, change my mind. And not just because ternary operators confused the absolute fuzz out of me for several years before I sat down and spent an hour learning how they work. Ternary operators invite new programmers like me to display their intelligence in the codebase by running the line length out into JavaScript levels of insanity when an if statement does exactly the same thing.

Heck, any feature that encourages developers to be smart should be discouraged, IMHO. As you mentioned at the end, it just turns into a clusterbomb of epic proportions just waiting for something to go wrong. Have I dealt with code that was too smart? Yes. It was mine. I thought I'd display my intelligence in the codebase by only using GOTO for everything. When I had to use that program later, I rewrote it like a normal person. "It takes twice as much intelligence to debug code as it does to write the same code. Therefore, if you write to the limit of your intelligence, you are by definition not smart enough to debug your own code." -author unknown. I try to live by that statement.

Just add Rust enums to Go and the "?"-Thing and Go would improve at least 2x

Okay, the one thing that really chaps my ass is putting new lines for curly braces and that catch part in the D Lang example. i have a rage inside me that desires his immediate demise. Holy crapola I hate unnecessary lines like that and frankly it makes it all less readable.

WTF. i.(type) should have been much more readable as type(i) or even i.type

Elegantly simple is different from simple-minded. Go seems intended for the latter.

As a Neovim/vscode/emacs enjoyer , I really enjoy your content regarding all this hot controversial topics.

The confusion engine 🤣🤣🤣

With go its not just the syntax but the batteries that are included .... tcp/stream programming is extremely nice and performant ... golang hit a homerun with the network stack (`-tags netgo`) and static compilation

Having a guy like the author of the article on my team will be a nightmare.

gomod came in 2018, before that dealing with dependancies in go was a joke.

Simple solutions are less prone to fail and easy to maintain. If you want to play 3D chess, play 3D chess.

I can't respect any programmer that doesn't writes pure machine code, not those dummy compilers.

So I love go but := is auto so wouldn’t count it against D but fully agree with you that go is cleaner

Hah, the line "programmers who grew up on C". ken was on the Go team. ken. THE ken. ken did not grow up on C. C grew up on ken. ken knew C when it was B or BCPL. (yes, I knew BCPL too, it's like C in ALL CAPS)

Is Go a good choice to replace large Cobol business systems?

Ym
V

D is pretty hardcore, but Nim can compete:

import os,sequtils,strutils
proc params:auto =
try:
if paramCount() > 1: result = toseq(1..paramCount()).mapIt it.paramStr
else: result = paramStr(1).readFile.splitWhitespace
except: result.add "No input"
echo params().join " "

Some unofficial Go manifesto explains it best:

1. We are aware that the computer is a computer, not a thinker. That's why we are explicit. Always. Telling the computer explicitly how to compute is smart. Expecting the computer to think, to guess and to assume is foolish.

2. We believe in strong and static typing because we believe in being reliable.

3. We are well-organized, readable and consistent. We hate chaos, we hate conflict and we hate losing time. That's why we follow standards and idioms.


4. We want to be smart and creative about our projects, not about coding. That's why we follow standards and idioms. And we love first-class IDEs where we can cast standards and idioms into smart snippets.

5. Go is designed to make smart and careful concurrency management easy. It's not designed to encourage sloppy and stupid concurrency management.

6. Thinking in Go is thinking big. Really big! It's about programming superservers dealing with super loads each and every second. It's about programming the network infrastructure of Wall Street where a foolish bug simply must not happen. That's why we are so picky.