This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-13
Channels
- # adventofcode (35)
- # announcements (2)
- # arachne (1)
- # beginners (71)
- # chestnut (2)
- # cider (100)
- # cljdoc (17)
- # cljs-dev (17)
- # cljsjs (2)
- # cljsrn (2)
- # clojure (53)
- # clojure-austin (2)
- # clojure-europe (1)
- # clojure-finland (2)
- # clojure-italy (3)
- # clojure-nl (7)
- # clojure-russia (56)
- # clojure-spec (56)
- # clojure-uk (35)
- # clojurescript (58)
- # community-development (14)
- # core-async (9)
- # cursive (22)
- # data-science (5)
- # datomic (14)
- # duct (5)
- # emacs (2)
- # expound (4)
- # figwheel-main (6)
- # fulcro (23)
- # kaocha (8)
- # lumo (7)
- # off-topic (10)
- # pathom (6)
- # re-frame (17)
- # reitit (31)
- # ring (3)
- # rum (1)
- # shadow-cljs (45)
- # spacemacs (10)
- # sql (12)
- # testing (9)
- # tools-deps (130)
Is there a Windows installer for openjdk 11? I can only find one for oracle jdk 11. AdoptOpenJDK don't have one yet.
Use Chocolatey
@topi.kettunen I'm not too familiar with that tool, will it modify PATH?
I believe that when installing Chocolatey it only adds Chocolatey
's own /bin folder to PATH
what is so cool about coroutines (In Python/Kotlin)? ain’t CSP/Actor model a better approach?
The cool thing about coroutines is they allow to implement green threads, which have a better memory footprint than system threads so you can have many more of them simultaneously on a single machine. It doesn't make much sense to compare coroutines with CSP or actors, because coroutines are low-level constructs, not a concurrency model per se. core.async
's go
macro actually uses a coroutine engine internally. What is interesting is to compare concurrency models.
thanks. that cleared some confusion. But still coroutines are building blocks for the new async/await approach (not C# approach with Futures). This is what I was intended to say. Comparing async/await with CSP, Actor
I've been wondering about the comparison between CSP and async/await too. One difference is that channels in C#/JS, awaiting a Task/Promise is a one-shot, and building a pipeline for data requires extra constructs. Would you say that's accurate?