This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-24
Channels
- # aatree (27)
- # admin-announcements (5)
- # all-the-channels (2)
- # aws (27)
- # beginners (38)
- # boot (48)
- # braid-chat (18)
- # cider (6)
- # cljs-dev (9)
- # cljsrn (8)
- # clojars (4)
- # clojure (73)
- # clojure-dev (2)
- # clojure-russia (2)
- # clojure-sg (1)
- # clojurescript (96)
- # code-reviews (3)
- # community-development (4)
- # conf-proposals (17)
- # core-matrix (2)
- # cursive (2)
- # datascript (4)
- # datomic (4)
- # dirac (1)
- # funcool (5)
- # hoplon (2)
- # mount (66)
- # off-topic (35)
- # om (211)
- # parinfer (2)
- # pedestal (2)
- # proton (1)
- # reagent (2)
@jaen I have a lot of experience with Elixir/Erlang, want to check out more LFE now that I've done Clojure.
about as much Erlang as I have Ruby, and OTP apps are very much purpose built imo towards soft-realtime. Elixir's the same way. It's too much in the sense of a "general programming language" where I'm not building a distributed system.
there's something to like about rapidly being able to build up a Node or Go app, and I like Clojure for feeling like a nice in-between.
@jarodzz: soft real time, IO dependent systems. I'd reconsider anything that's CPU-bound.
got it. so if i have a high through put event stream,like a company all services daily log, i'd like to monitor it, detect some ilegal or dangouer activity, i should use Elixir?
actually, I'm considering using it for something similar, but exactly. The way I'm looking at doing that is taking the rules (even user-generated rules), and compiling them into the live running BEAM VM, because you can do that.
Also a good point is to consider the resiliency structuring your application with OTP can give you.
If you need a highly distributed system that's also reliable, anything based on the Erlang VM (like Elixir) is a good choice.
Though, unless you really really need hot code reload, don't do it, just adds a fun layer of complexity.
so @jaen I think the attraction for me to Clojure is for when I don't want to start out building up supervisor and application trees, or an entire OTP app, and want to iterate fast and maybe grow parts of the system into it.
Yeah, I can see how that can be appealing to not have to buy into some structure at first and move fast.
As for play-clj - yeah it's pretty interesting. Having your whole game state in an atom and transactionally update that. Of course it won't scale to any type of game, but if it fits it sounds awesome.