Is this worth learning, /g/?

>>61245486
No.

i read that it is supposed to have super easy concurrency compared to javascript and then i tried it and it was shit and it was impossible to do simple things that are possible in node

From what a coworker says, it's pretty damn cool.

>>61245486
Yes.

If you're already familiar with a C-like language it should take you less than a week to git gud. Go for it.

>>61245486
no

>>61245486
it's meme language made for stupid people

>>61245486
hi where are the generics :DDDDDD

>>61245486
Probably not if you have something better to do. If I have time I might learn Go to deploy some simple restful web service to be used by an embedded device. Might just roll with C++, grpc and protobuf instead though since I use C++ and protobuf daily.

File: humouytohamster.jpg (88KB, 1263x357px) Image search: [Google]

88KB, 1263x357px

>>61245486
That hamster looks familiar...

>>61245486
The only thing Go has going for it is the go routines. These could have been implemented in C, there's no reason for a new goddamn language

Definitely worth checking out. If you like C++, don't like GUI and have to do network stuff - it'll be perfect. If not - there may be languages better suited for your task.

>>61245486
No. If you just want to learn a language for employment than Java, C# and Javascript are all better choices since they're a million times more popular than Go. If you just want to learn an interesting language then there are far better options.

>>61245526
Such as?

>>61245486
I think it's worth it to try out. You might not like it, but I do.

>>61245486

Absolutely not.

>>61246894
launching a loop inside a goroutine and then doing literally anything else after that goroutine

>>61246894
>>61247434
an infinite loop i mean

>>61247443
I can't see how that's not possible in Go.
What would that look like with node?

>>61246517
This.

Also, if you want to build malware or do anything with security. go is really good.

>>61245526
node is a meme, there's concurrency but not parallel processing.

>>61247652
Indeed. Mirai used Go for the c&c stuff.

The syntax makes me want to hurl. How do I get over that?

>>61247573
generators?

>>61247788
coffeego :^)

>>61245486
You learn it in a day, master it in a week. It gives you a handy tool for many tasks. Of course it's worth it. Don't listen to the jealous Rustbabbies.

>>61247803
>generators?
goroutines and buffered channels

>>61245486
Rust is better.

>>61245526
because JS uses callbacks as model for concurrency and Go uses channels... I can see why this doesn't translate well

>>61248226
Yeah cause promises, async/await and generators totally aren't in JS now?

>>61247943
True, but it's definitely not the same problem space.

>>61249419
I love how node 'programmers' try and hide all their awful ugly nested callback code with syntactic sugar that makes it look like goroutines or some how delays the call back so it doesnt look like what it really is and they some how think this fixes node so its like a real concurrent language

>>61249462
Go pretended for the longest time that it was in the same problem space. Actually there is no problem space where go fits.

>>61249591
Promises may be sugary, but generators are equivalent to proper coroutines.

>>61249760
Can you suggest some JavaScript->exe compilers?

>>61249817
>but generators are equivalent to proper coroutines.
no theyre not, they simulate processes but are not actual concurrent processes

>>61247434
What the fuck are you talking about?

>>61247769
Concurrency is specifically not the same as parallel

>>61248226
Howso?

>>61249419
Promises are the same thing as futures in rust?

>>61249911
Yes.

>>61249881
can you just make a fucking argument without socratic questions and restating what someone else already said

>>61249941
I'm asking for clarification to present an argument, I'm not going to blindly shout out random shit only to have the main response be YEAH BUT GENERICS LMAO

>>61247434
>>61247443
why would you do that in the first place

>>61250007
If you have to ask you don't belong anywhere near /g/.

>>61247434

func infinite() {
    for {
         fmt.Println("Look at this infinite loop!")
         time.Sleep(time.Second)
    }
}

func main() {
    go infinite()
    fmt.Println("Wow I'm doing something after an infinite loop in a goroutine")
    time.Sleep(time.Second * 10)
    fmt.Println("Still doing stuff! Wow!")
}

???

>>61250062
i have to ask, deadlocks are a thing

>>61250075
Then you need to fuck off and never come back.

>>61250101
https://play.golang.org/p/Mpu79jlcVT see >>61250068

>>61250156
>>>/tumblr/ will be more your speed I'm sure.

If you're willing to treat it as new technology then learn more about it. Go can be installed on a VPS and you can use it as a backend language for web, as an example.

>>61250411
>If you're willing to treat it as new technology then learn more about it. Brainfuck can be installed on a VPS and you can use it as a backend language for web, as an example.

The reason people are getting so pissy about it (here and /r/programmingcirclejerk which I'm pretty sure is just /g/), is because people are actually using this language for productive purposes; there really isn't anything in the language that is going to make you feel really smart.

If you don't expect a fully fledged language (generics) like C# or Java, you'll be fine. The tooling it comes with is great - learn about "go test" to see how easy it is to have unit tests (I'm not pro TDD, but some tests are useful), and there are means to performance test your code without requiring some third party.

>>61245486
it's not the best language in the world, but it makes Node looks like a total retard

>>61249419
JS has 5 different 3 ways of doing concurrency, of them only 1 is usable if you care about testing your code.

Go as one and it works.

>>61251636
>it's the worst language in the world, and it makes Node looks like a total genius
FTFY

Go is an excellent language designed by people with a clear vision and a lot of insight into what has good and bad in programming over the years.

Not being laden with extraneous features and typically only having one 'right way' to do something are virtues that come to be appreciated with experience. Unfortunately this does not garner much attention from the crowd that are looking for the next amazing language construct that Lisp already got bored with 10 years ago.
However, the readability difference between average pieces of Go and Rust code speaks for itself and is absolutely staggering considering that they can trace their roots to the same tradition.

>>61252562
>the next amazing language construct that Lisp already got bored with 10 years ago
ouch

>>61252562
True. Go looks like absolute unreadable vomit while rust is clear, straightforward, and complete. It always amazes. interface{}interface{}interface{}.

>>61246403
good one

>>61251277
How is Go not a fully fledged language?

>>61253410
>interface{}interface{}interface{}
what the fuck is this

>>61252562
lol no generics

>>61250528
>>>If you're willing to treat it as new technology then learn more about it. Brainfuck can be installed on a VPS and you can use it as a backend language for web, as an example.

>>61245486

If you want to be paid to work on large projects and be productive, yes.

If you are in academia and choose programming for bragging rights, no.

>>61253905
people made object oriented frameworks for brainfuck
no lie

>>61253927
>people made object oriented frameworks for brainfuck
>no lie

>>61253936
yes anon, that is what the post said

>>61253956
>yes anon, that is what the post said

>>61253410

>Go looks like absolute unreadable vomit while rust is clear, straightforward, and complete.

LOL, I like rust for what it aims to achieve (safety while staying performant) but it's probably the ugliest syntax I've seen, it's like they looked at the worst looking C++ code and said 'hey, we can do even worse!'.

Go is repetitive, but atleast it's readable.