This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-04
Channels
- # announcements (8)
- # beginners (27)
- # calva (8)
- # cider (26)
- # clara (19)
- # cljdoc (4)
- # cljsjs (1)
- # clojure (221)
- # clojure-dev (6)
- # clojure-europe (11)
- # clojure-gamedev (18)
- # clojure-italy (8)
- # clojure-nl (12)
- # clojure-spec (85)
- # clojure-uk (17)
- # clojurescript (34)
- # community-development (1)
- # cursive (26)
- # datomic (16)
- # dirac (19)
- # duct (6)
- # editors (4)
- # figwheel-main (1)
- # fulcro (68)
- # graphql (41)
- # juxt (16)
- # luminus (11)
- # off-topic (30)
- # pathom (35)
- # planck (2)
- # re-frame (18)
- # reagent (20)
- # remote-jobs (6)
- # rum (1)
- # shadow-cljs (37)
- # spacemacs (9)
- # vim (14)
wow, Chaim Kirby from the Python group has such a good idea for the community
he uses a slack plugin to give credits to people
you should follow his github, what a cool person…
can all of you follow his github?
Like IRC's "karma" bots? One of the other Slacks I'm in has a karma bot. It's a nice idea. I'll bring it up with the Admin team here but I wouldn't expect any opposition to the idea really (other than us being on a free plan with very limited integrations -- and I think Slack are trying to get rid of the legacy API tokens and "force" everyone into specific app integrations).
@seancorfield ya, it gives you extra access to channels and rewards based on the credits you get
I think the goals are fairly different. Schema aims to perform validation and coercion at a type level, e.g. enforce that foo
is some type Foo
as represented by a schema.
Spec aims to model relationships between data. Type validation is part of this, but it also includes stuff like modeling relationships between function arguments (i.e. in an args list [start end] you can enforce that start < end
and start > 0
in the spec), output, shape of a sequence, regex validation. The goal is that spec serves more as a specification of the data and transformations in a system, which allows things like generative testing with quick-check and validation of business requirements on top of the type validation.
Schema also has function validation (args & return) and supports generative testing. Sequence & regex spec are much better with spec, also the fact that branching info available in conform. Spec doesn't support runtime transformations like coercion. Schema is mostly data, spec is mostly not data.
After watching a few intro videos, I still don't understand the Actor model. Besides the guarantee of a queue that will be processed one message at a time, what does it buy me? What leverage does it afford me against the complications of concurrency?
... Is that it? In a talk a listened to, the creator seemed to think it was a very exciting and important idea. Maybe, 40 years after its invention, we just take it for granted?
Like, how does that help me achieve a consistent view of the world between processes? Or over network boundaries?
(Your explanation does make some of what he was saying much more clear though - thanks)
what makes you think scala is bound to the actor model @UGQJZ4QNR?
I'm just wondering why you seemed to imply one language is more suited to one paradigm than another
there's STM libs for scala, and there was various attempts to implement the actor model on top of clojure
the actor model used to be quite popular in scala, but IMO much more due to akka's aggressive marketing than technical features of the language itself
This post has valuable insight about how the actor model relates to clojure http://www.dalnefre.com/wp/2010/06/actors-in-clojure-why-not/
Ok, as I suspected, there’s more to actors than is evident to me at the surface, just like there’s more to CSP than syntactic sugar. Thanks for the article @U053XQP4S, really helpful.
> In this paper, we aim to answer a long-standing open problem in the programming languages community: is it possible to smear paint on the wall without creating valid Perl?
SIGBOVIK?
yeah. noticed it from hacker news. I actually thought there was no invalid perl so i was surprised to see only 93% of paint thrown against a wall are valid perl programs
haha what else could it be :’) — SIGBOVIK that is
i thought i heard parse errors in perl turned the characters into comments. so i didn't think it was possible to be invalid perl
You can have strings that are unquoted