Clojurians Log v2

seancorfield: thanks for referring me to the channel

anyone went from golang to clojure? pros/cons?

As part of my attempts to "learn a new language every year", I tackled Go a couple of years back and I was very disappointed with it.

When I learned Rust last year, that was what I had hoped Go might be.

My friend @markmandel likes Go and he does Clojure as well so he might give his insight on comparing the two...

(he’s offline today… 4th of July and all… but I sent him a link to this message to see if he wants to join in the discussion at some point)

He’s a Developer Advocate for Google so he’s very pro-Go 🙂

seancorfield: awesome. I can't wait for his opinion

I made a performance comparison between phoenix / sailsjs / spring boot: http://tales.sveri.de/posts/2016-07-04-phoenix-spring-sails.html if anyone is interested

@sveri they are not doing the same thing

the controller in sails is only doing a lookup, while the spring one is doing a lookup plus persisting to the database

Go is my go to "work in a team, and get s* done language" - requires very little cognitive overhead, compiles to a binary, so is super easy to deploy, and comes with a great standard library

It's not without its foibles, but it does excel in those areas

the phoenix code is also only doing a lookup. Can’t really compare spring with those two if they are doing additional things.

you might get some heat for that

@roberto: Hm, thats true, the spring controller can persist, but in my test I was only running the lookup, maybe I should make that more clear?

I updated the post, thanks for the pointer

@markmandel: Yeah, bbloom liked Go overall I think, despite its issues.

The dev tooling is nice, I’m a huge fan of the auto formatter.

Having one true way to format, solves allot of arguments

Go the language looks horrid to me, but Go the platform, tooling, and the One True Way seems appealing. I've been curious to try it out for sake of that, and to put my naive impressions of the language to the test. Alas, time is limited, and so I have to focus on languages I believe will help me achieve my mid-term goals, of which Go doesn't seem like it'd fit the bill (for now).

I would use Go if I were working on a problem it seemed like a good solution for, basically. Either that or Erlang - Erlang is probably more interesting, and Go is probably more pragmatic. I have no problem with pragmatic when I need to get work done.

Yeah, that was the other thing: if I had the chance to work on a heavily distributed project I'd probably opt for Elixir/Erlang over Go, if given the choice. I have heard of at least one really good Erlanger moving to Go for sake of the platform/pragmatism though. I believe they have a Go library that attempts to capture aspects of the Erlang Way.