You WILL have the large binary

>> no operator overloading
thats a good thing actually, operator overloading is the vorst thing happened to c++.

>i was correct in my prediction years ago that when go gets generics, the genericswhiners who don't use even go will switch to complaining about generics

Attached: 1647794078726.jpg (680x371, 37.1K)

>no operator overloading
>no covariance/contravariance
>no sum types

Attached: moving_goal_posts.jpg (945x526, 95.2K)

>And you WILL be happy
yes

> half assed generics
how so?
> no operator overloading
That's a good thing
> no covariance/contravariance
Academia masturbation
> no sum types
can be semantically approximated with multiple return values and a couple of lines of code

I think its really neat
>compiles in a second
>performant
>no malloc faggotry
>cute mascot
>containers from scratch
>made for CLI and server services, filters out frontend webtards by design

t. self taught tard at 1 month, only used basic python before

Attached: file.png (1200x1200, 2.02M)

>Go
>Google
>Go keyword
>Goroutines
>Gopher mascot
Why would you use this conceited little piece of shit?

Attached: 1636590777973.png (976x850, 492.32K)

>no operator overloading
Have you ever tried to maintain C++ code. Operator overloading is literally the cancer of C++.

It's actually pretty good, people complaining are mostly neets that do not even write go

Why does golang make rusties seethe so much? People like what they like. Don't shit up the board with your straw man arguments, go to your rust thread and chat about whatever you're writing. Don't worry, I'm sure your memory safe fizz buzz will get you that interview.

(You)

It makes rusties and sepples users seethe because it implements referencing, interfaces, and multithreading in a nearly foolproof fashion. Anything that isn't a complex string of sigils is clearly inferior and for morons.

>>You WILL use all you imports
>>You WILL use all the variables
unironically good things, it's a shame shit languages are going to give these a bad rep