This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-12
Channels
- # babashka (37)
- # beginners (27)
- # biff (1)
- # calva (18)
- # cider (45)
- # clj-on-windows (5)
- # cljsrn (1)
- # clojure (90)
- # clojure-art (3)
- # clojure-uk (1)
- # clojurescript (7)
- # core-logic (4)
- # datomic (4)
- # events (2)
- # fulcro (3)
- # hyperfiddle (23)
- # leiningen (66)
- # malli (1)
- # meander (7)
- # nrepl (1)
- # off-topic (9)
- # pathom (1)
- # re-frame (15)
- # reitit (19)
- # remote-jobs (1)
- # shadow-cljs (103)
@zimablue re. your question about business model in the other channel Commercial OSS is huge, see https://twitter.com/josephjacks_/status/1494840009882361859 I.e. Apache Spark -> Databricks We think the best business is likely selling a shrinkwrapped experience to midsize businesses who don't want to spend eng time on UI Hyperfiddle (the library) and Photon are FOSS as far as Clojure programmers are concerned, we haven't chosen a license yet but guidance from the best open source VCs is to use a real FOSS license. As members of the Clojure community ourselves we personally value FOSS and the ecosystem activity it enables. This approach gives us access to growth capital which we think will benefit the ecosystem tremendously, both Hyperfiddle ecosystem but also paving an onboarding path for mainstream programmers to Clojure - which should produce a compounding flywheel effect for Clojure itself
Here you can see • the UI stream in from the server on start click • the forms work and emit signal of transactions • select options widget is exploded to diagnostic "xray" view • bugs in our dom renderer which is being reworked • gray fields are reflected from clojure specs
Same test AST as always:
(hf/ui
{(submissions .)
[:person/name
:person/email
{[:person/gender {::hf/options (genders)
::hf/option-label :db/ident}]
[:db/ident]}
{[:person/shirt-size {::hf/options (shirt-sizes person/gender .)
::hf/option-label :db/ident
::hf/render xray-select}]
[:db/ident]}]})
(defn submissions [needle] ...)
(defn genders [needle] ...)
(defn shirt-sizes [gender needle] ...)
(s/fdef submissions :args (s/cat :needle string?) :ret (s/coll-of hf/ref?))
(s/fdef genders :ret (s/coll-of hf/ref?))
(s/fdef shirt-sizes :args (s/cat :gender hf/ref? :needle string?) :ret (s/coll-of hf/ref?))
seems like a really apt emoji to signal an impressed reaction to this kind of reactivity ☺️

thanks so much for your answers, sorry to ask awkward questions I am curious partly because I dream of selling software myself
sorry, growth capital = venture capital real foss license = as opposed to a source-available commercial license
so not necessarily copyleft, do you have an opinion on copyleft vs other for someone in your situation?
Whatever FOSS license we choose will be commercial friendly so as many people can use it as possible
We're angel backed
commercial friendly is like MIT right? so enterprises don't freak out and get squeamish. But then you have the "Amazon problem" where they bundle you into their AWS except now they have bigger sales team and integrations
I'm curious about you saying your approach gives access to growth capital, what is it that you're saying gives access to capital where another choice wouldn't. Do you mean the approach to try and monetize through a SaaS ish bundled offering?
AWS problem is a fake problem, tech monopolies produce terrible software, AWS legitimizing us would be net positive by far
a slightly interesting company in a similar-ish space you might or might not have seen is "Anvil"
do you have a link, this is hard to google for
https://anvil.works/ they're basically using one of the python-to-js transpilers to reinvent winforms in the web and selling it with clojure in the backend as a low code platform for people doing a lot of workflow/forms stuff
less technologically interesting than what you're doing I think but similarly low-code, batteries included, open core
it's not quite the space I'm interested in but been doing some market research and they turned up
I meant a goto market strategy something like developer led with upsell to either enterprise/HA server or a managed low-code platform - this lets us keep the core product open but also has great economics
Clojure market size has been a source of anxiety for a long time but user interviews for our latest tech would suggest that familiarity with functional mindset matters a lot more than syntax, and everyone knows React.js now