which parenthesis highlighter do fellow emacsen use for clojure?

@slester: clojure is freaking awesome for basically anything, including a chat server.

@fenton I mean it is! Just wondering if it was too much work comparatively

@slester

its the easiest language to work in...

the others you might pull your hair out...clojure has core.async

@fenton: I use Spacemacs' built-in paren-handling, which IIRC is the author's custom one.

Rust has concurrency, as does Go

@eggsyntax: ok, i'm using plain emacs with my own conf... can't lose lispy for clojure editing...really didn't like the spacemacs for lisp like editing!

@slester: yes...and i've programmed in neither of those two, but have programmed in a lot of other languages and every moment i code in clojure i thank my lucky stars....i could list all the features of clojure here....if you want...that I'm thinking neither rust nor go could hold a candle to...but?

Haha. Your enthusiasm is noted! Just wondering if others have more experience with those kinds of languages that could compare/contrast.

sure good luck.

hey @slester definitely clojure. the jvm library ecosystem is infinitely more mature. there are robust libraries for every chat protocol, every transient or persistent storage service, every notification protocol, every appropriate in-mem data structure, etc. nearly all of that still has to be invented in rust. at a language level, rust gets you close to the metal, and gives you memory management control where the jvm utilizes garbage collection. there are domains where that matters but chat servers- where the app is likely running on cloud servers two or three layers of abstraction above hardware and where latency comes from the network, rather than from whatever the server has to do- are not going to be one of them

golang would be a good choice for chat server- the library ecosystem has gotten pretty mature.

@jonahbenton: Thanks for the response! Coming down to Clojure vs Golang, what are you thinking? Are they comparable? If so I'd choose Clojure for sure

just making sure I'm not shooting myself in the foot

by choosing something that may end up being less robust than I'd like

sure, either language ecosystem is a great fit for the problem in general. to choose i would spend some time looking at the details- specific libraries and protocol implementations in each case- and weigh other factors- team experience and comfort in each environment- some people hate the jvm, some object to the boilerplate required in go- operational experience, etc

why do people hate the jvm?!

https://www.google.com/search?q=hate%20jvm&rct=j

haha

yeah what i meant is that both languages/ecosystems are appropriate on a technical level, so non-technical/philosophical considerations may weigh highly.

gotcha, thanks

Havn't seen this xkcd before: https://xkcd.com/743/