Why is golang so comfy?
>putting the variable type after the variable name
>>54307184
It's the new "thing", Rust does this as well.let a: f64 = 1.23456789
>>54307184
Literally the only good thing about it.
>>54306934
It's not comfy. It's not good. It's harmful. Please stop using it.
>>54307213
i didnt know uriel had an evil twin
>>54307221
I'm not his twin (though I am indeed evil).
>>54307213
Harmful, how?
>>54307277
It infantilizes its users. It was designed for people who Google thinks aren't capable of using Java or C++.
>>54307184
It makes sense if you program in a language from the ML-family or know operational semantics.
its them go routines senpai.
>>54307289
So then dynamic and scripting languages are harmful?
>>54307688
They sure are.
>>54307724
t. C fizzbuzz expert who has never had a job
>>54307742
this, kek
>>54307742
Scala dev, actually.
>>54307759
how embarrassing, you need to go back to ribbit where you belong.
>>54306934
Because it is a nicer C.
>>54307289
Could you elaborate? What exactly is infantilization in golang?
>>54306934
>Why is golang so comfy?
Manual labor can be relaxing.
>>54310728
What's your non-manual labor language then?
>>54311021
OCaml. Sadly, it lacks the genuinely impressive standard library of Go. Someone make an ML (or anything with a half-decent type system) that targets Go's runtime already.
>>54306934
It's not. It has garbage collection.
Rust is better
>>54307184
Putting return type definition after the function definition like `fn function_name() -> type` is even better. That's Rust tho, dunno about goshit.
>>54307688
For anything more than webpages and simple data processing, yes
Go lang is great for making apps without the need for a fucking framework
Was curious about Java last night, I decided to try some tutorials / examples, never again. This is truly the designated programming language
>>54306934
Stockholm Syndrome
