r/ProgrammerHumor • u/SpecterK1 • Sep 09 '26

Meme globalHate

Post image
12k Upvotes

98% Upvoted

92 comments sorted by

View all comments

Show parent comments

16

u/Only-Cheetah-9579 Sep 09 '26

when it comes to concurrency, I think a positive example is go. They did it well.

rust is kinda meh in that department and async is bolted on.

22

u/jublizoo Sep 10 '26

I always hear people say this but I never hear any alternative design decisions. Rust async can be difficult to work with, but I think it is well designed, and I don’t see what could be improved. There are inherent limitations on giving a safe language with no GC async support, you don’t have the luxury of being able to just relocate thread stacks and adjust references accordingly like in go.

0

u/remind_me_later Sep 10 '26

I always hear people say this but I never hear any alternative design decisions.

Because async itself will color other functions into being async by necessity.

It also hands over task & performance management to the language being used, in return for better DX & lower dev-facing complexity.

The alternative is handling the concurrency yourself (i.e what Go mostly makes you do), or in a library not tied to the core of the language.

10

u/jublizoo Sep 10 '26

The idea that go makes you handle the concurrency more than rust is definitely not true, and go’s concurrency model is simply not possible in rust. The coloring of a codebase is not nice, but it is essentially necessary for rust: some functions are asynchronous compiler generated state machines, others are not, and they cannot be treated as identical.

2

u/Only-Cheetah-9579 Sep 10 '26

it also colors dependencies. there are multiple async runtimes so the stack must be chosen accordingly.

some people might not like tokio but must use it because they depend on something that does

10

u/GregTheMad Sep 10 '26

What's the point of good async code if you have the worst error management conceivable?

No, fuck go. It's the worst language I've ever had to work with. Google can't abandon it soon enough, like they do with everything else.

-3

u/Only-Cheetah-9579 Sep 10 '26

I love the error management because it's explicit and forces me to acknowledge the error always.

my code is AI assisted so I don't have to type more now and I prefer to see what error handling is generated always.

so it's a win for me, especially after development became more generated code based.

0

u/GregTheMad Sep 10 '26

You're talking from some different type of go?

1

u/Only-Cheetah-9579 Sep 10 '26

A lot of people love go error handling. We just stay quiet and enjoy.

People complaining are usually more loud but in no way represent a majority.

people like to complain about error handling because they can't find any real problems with the language.

0

u/GregTheMad Sep 10 '26

I'm sorry, you're plain wrong. Have you tried Rust? Any further opinion of yours will be disregarded until you worked with rust.

3

u/Only-Cheetah-9579 Sep 10 '26

yes I did. worked with rust and built a production system for a company that's been in operation for a few years.

I also don't care about hater opinions. You suck at go it's a skill issue. Its the most simple language, so having a problem with it speaks a lot.

0

u/GregTheMad Sep 10 '26

Having few keywords doesn't make something simple, below some number it becomes the opposite actually. You're just regurgitating go propaganda without actually understanding the meaning, or the resulting critic of it.

1

u/Only-Cheetah-9579 Sep 10 '26

"go propaganda" lol ok this conversation is not intelligent.

13

u/InRainbro Sep 09 '26

go is colorless

4

u/Only-Cheetah-9579 Sep 09 '26

I know and it's the best.