This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-21
Channels
- # announcements (1)
- # architecture (1)
- # beginners (125)
- # boot (6)
- # boot-dev (2)
- # calva (69)
- # cider (38)
- # cljs-dev (3)
- # clojure (212)
- # clojure-austin (7)
- # clojure-australia (1)
- # clojure-denver (2)
- # clojure-europe (3)
- # clojure-gamedev (1)
- # clojure-hamburg (8)
- # clojure-italy (10)
- # clojure-nl (31)
- # clojure-russia (3)
- # clojure-uk (57)
- # clojurescript (56)
- # core-async (3)
- # cursive (15)
- # datascript (1)
- # duct (28)
- # emacs (6)
- # events (1)
- # figwheel-main (11)
- # fulcro (22)
- # luminus (59)
- # lumo (2)
- # onyx (4)
- # overtone (1)
- # re-frame (1)
- # reagent (4)
- # remote-jobs (3)
- # rum (2)
- # shadow-cljs (84)
- # spacemacs (7)
- # speculative (5)
- # vim (1)
- # yada (127)
listened to https://www.therepl.net/episodes/16/ sounds cool, 80+ people company, whole stack supposedly clojure/clojurescript
Installed shellcheck as an emacs plugin. https://github.com/koalaman/shellcheck
and it compiles down to binaries with fast startup time, hence suited for linting in editors
Parser Combinators are great
Love Haskell’s Parsec
@lennart.buit I used this in Clojure once for an advent of code problem: https://github.com/blancas/kern
Yeah, one of the first things I went looking for when switching to clojure
Ehm, started out in Java, then Python, Haskell, Ruby and now Clojure
Last two in ‘work life’
oh JavaScript, how can I forget about that
Parser combinators live in this strange “they are super cool, but I don’t know when to use them” land. They are great for prototyping grammars I guess, but as soon as you know your grammar, why would you still have it as a PC
unless you want to have context sensitivity or something like that. Thats totally valid in Parsec
Well I mean, when you have a complete view of your grammar, why would you develop it with a Parser Combinator library instead of a Parser Generator
PG’s are usually much faster