This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-13
Channels
- # adventofcode (84)
- # aleph (1)
- # announcements (2)
- # aws (27)
- # beginners (52)
- # braveandtrue (2)
- # calva (440)
- # cider (7)
- # clara (2)
- # cljdoc (26)
- # cljs-dev (70)
- # clojure (131)
- # clojure-berlin (4)
- # clojure-brasil (1)
- # clojure-europe (2)
- # clojure-greece (4)
- # clojure-hamburg (1)
- # clojure-italy (4)
- # clojure-losangeles (6)
- # clojure-nl (14)
- # clojure-spec (7)
- # clojure-uk (25)
- # clojurescript (26)
- # component (2)
- # cursive (13)
- # datomic (60)
- # dirac (59)
- # docker (1)
- # figwheel (1)
- # figwheel-main (2)
- # fulcro (12)
- # graphql (5)
- # juxt (33)
- # leiningen (19)
- # nrepl (1)
- # off-topic (37)
- # protorepl (2)
- # re-frame (18)
- # reagent (46)
- # remote-jobs (1)
- # ring-swagger (1)
- # shadow-cljs (88)
- # sql (10)
- # tools-deps (64)
- # vim (24)
amused at how harsh the examples in this postgres vs mariadb article are https://www.cybertec-postgresql.com/en/why-favor-postgresql-over-mariadb-mysql/#
And only yesterday I learnt about (iterate). So far I've just used (recur) based solutions everywhere.
the article seems to pick on a few points where postgres does better than mysql/mariadb... which for some people if important and for some it isn't.
I opt for postgres by default, but only because I know it better. Trying to form a proper argument now to support that.
I have tried MySQL after Postgres, because I was forced to, and was surprised it did not even do foreign key contraints well (unless you did extra work). It’s probably better now
it is unfortunately still not better, the defaults are horrendously unsafe (even in MariaDB)
the meetup was nice yesterday. We solved the last problem of 2015 of AoC and it was a good occasion to pair experienced clojure people with less-experienced. I think it was a nice combination of both 😄
old solutions welcome to https://github.com/borkdude/advent-of-cljc/ too