This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-30
Channels
- # babashka (46)
- # beginners (234)
- # bristol-clojurians (4)
- # cider (7)
- # clj-kondo (39)
- # cljdoc (8)
- # cljs-dev (10)
- # cljsjs (10)
- # cljsrn (24)
- # clojure (84)
- # clojure-brasil (7)
- # clojure-europe (12)
- # clojure-germany (4)
- # clojure-italy (3)
- # clojure-nl (41)
- # clojure-spec (17)
- # clojure-uk (66)
- # clojurescript (64)
- # conjure (161)
- # cursive (12)
- # data-science (45)
- # datomic (20)
- # devops (11)
- # docker (2)
- # duct (9)
- # events (7)
- # figwheel (1)
- # figwheel-main (20)
- # fulcro (32)
- # graalvm (5)
- # helix (82)
- # jackdaw (9)
- # jobs-discuss (19)
- # kaocha (11)
- # local-first-clojure (1)
- # malli (6)
- # meander (3)
- # nrepl (12)
- # off-topic (2)
- # other-lisps (15)
- # pathom (14)
- # rdf (6)
- # re-frame (8)
- # reactive (1)
- # reagent (5)
- # reitit (4)
- # rum (3)
- # shadow-cljs (77)
- # spacemacs (3)
- # sql (9)
- # test-check (31)
- # tools-deps (13)
- # vim (62)
- # xtdb (18)
Not 100% convinced yet to be honest. It does solve some really complex problems and it is very clever at doing that. It also includes everything including the kitchen sink.
So can't adopt it by using little pieces (as far as I can tell). So it has a rather steep learning curve IMHO.
I've been pondering about babashka, whether I should leave JDBC+Postgres support in (which I included last week), since it might be going to "everything including the kitchen sink" direction. Just interacting with psql
and the mysql
CLI by shelling out is already quite powerful for small sql things and it doesn't put extra features into bb...
not really, so that's why I may re-consider. most people just shell out to their respective sql CLIs
I'll release it behind a feature flag in the next release probably, so people who desperately need it can compile babashka for themselves
I’ve been wanting to take a look at fulcro. But so far I’ve been really happy with just using Re-frame + some clojure web stack
Fulcro and Pathom work really wel together. You can use the separately if you want to though.
I'm currently building a commercial product using Fulcro, Pathom, and Datomic. I inherited a legacy code base that used rum, minimally, and was more of a proof-of-concept than something I'd be comfortable with in production. So we stopped and asked ourselves if we should continue on as-is or pivot. We pivoted:
Yes, you can use Fulcro without Pathom. If you're using Datomic on the backend it may not matter much if you use it or not since Fulcro has its origins in om.next which means Fulcro's protocol is a lot like Datomic's pull-syntax. Using Pathom with Datomic provides marginal benefit, but if you're using SQL on the backend then Pathom would be super helpful in parsing the client request so it can be easily turned into SQL
This https://gitlab.com/tvaughan/fulcro-template is a Fulcro app I built for myself to learn and evaluate Fulcro.
I can't clone the project. I have downloaded the zip now, but then it complains that stuff is missing
I have no idea how to interpret this. This says anyone can access this repo, and also says only those with access can. These two seem contradictory to me. I don't see any option to open up access any further. I'll mirror this to github
Yeah, that's not required. This originated in a private repo. In .http://starterkit.mk you could just make the login
target return true. I can't redistribute Datomic so http://datomic.mk won't work either. I'm sorry this is so rough around the edges. The only way to get this to run as-is now requires that you download and run Datomic locally. I could come up with something that builds the Datomic docker image from a Datomic zip