This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (47)
- # boot (5)
- # bristol-clojurians (1)
- # cider (45)
- # clara (2)
- # cljs-dev (11)
- # cljsrn (47)
- # clojure (169)
- # clojure-brasil (2)
- # clojure-dusseldorf (22)
- # clojure-finland (1)
- # clojure-italy (9)
- # clojure-nl (3)
- # clojure-poland (2)
- # clojure-russia (4)
- # clojure-spec (79)
- # clojure-uk (105)
- # clojurescript (59)
- # core-async (39)
- # cursive (31)
- # datomic (10)
- # devcards (1)
- # duct (6)
- # editors (9)
- # emacs (12)
- # figwheel (1)
- # fulcro (50)
- # java (4)
- # mount (1)
- # off-topic (47)
- # onyx (33)
- # pedestal (1)
- # protorepl (1)
- # re-frame (32)
- # reagent (45)
- # ring-swagger (6)
- # shadow-cljs (100)
- # tools-deps (6)
- # uncomplicate (27)
- # vim (3)
Has anyone submitted a Clojurists Together Q2 2018 funding round proposal for improving ClojureScript + React Native tooling? I assume there are lots of areas that could be improved if only developer resources could be applied. Perhaps if a few specific improvements were clearly identified a proposal might be accepted.
The various project (Re-Natal, Boot React Native, expo-cljs-template) all seem to be in a place where they fundamentally work but could use "robustness" and "polish" fixes, essentially knocking off bugs in their respective issues lists. True?
Speaking as someone who works with a CLJS + RN codebase every day, and has spent many hours pawing at
hello-world projects using e.g. Re-Natal or Boot searching for a hair-extinguishing workflow, I would say true
Sadly, I am not in a position to nominate myself as a maintainer of any of these and submit a proposal. 🙂
any nontrivial CLJSRN project will inevitably make use of native modules and prebuilt components
My speculation is that the respective maintainers are accustomed to offering their time for free, but might be convinced to do work under the Clojurists Together project. (It helps justify dumping time into something when you are being paid.)
I currently don’t have a stake into which projects get funded or who gets paid; I just think it is a great fit.
(In the sense that React Native + ClojureScript is still a ripe area with lots of work to be done. 🙂 )
Btw sadly boot-react-native is not in working state anymore; I haven't had time to keep it updated and it has fallen in disrepair.
Yeah, that’s what happened with Ambly / Natal. (I ultimately decided it was worth trying to get behind one of the other projects that had community momentum, rather than try to “nurse” a project that didn’t have as much critical mass.)
Some things I can think of: - production builds (RN packager chokes on large bundles)
Well, I use it and the pain points really seem to fall into the areas of general robustness / polish.
Yeah, all of that is worth doing, and currently unpaid. But that story could be different
I wonder if the compensation rates that you get from Clojurists Together is compelling. Hey, at least something is better than nothing.
react-native has been a frequent topic for
shadow-cljs recently. I certainly want to add support for it but since I haven't done any
react-native project myself I can hardly say what would be required. Getting the code to run there seems fine but REPL doesn't quite work yet.
I did some basic tests with
create-react-native-app a while ago which seemed to work fine https://github.com/thheller/shadow-cljs-examples/tree/master/cljs-react-native-app
@pesterhazy The automatic require of external deps in fighweel works so and so for me personally. That could be improved I think.
I haven’t contributed at all to that so I have no right to complain. Thanks for your contribution!
But definitely focus on production builds. It’s the hardest problem we’ve had at work for the last year I think 😝
So, maybe if some specific proposal could be put together to improve Re-Natal production builds, there might be a chance @drapanjanas that would be interested in doing it as a Clojurists Together project. To apply for funding, you have to be a maintainer or recognized as such, which seems to have a single answer.
@mfikes There are a couple of good folks that have done interesting things in cljsrn so if @drapanjanas is not available maybe @tiensonqin could be available for example. But working on re-natal, or even better: a solution that works both for expo and re-natal.
Yeah. My rough feeling (this is just me), is that for individuals who are already playing the role of contributing (for free), it is a a no-brainer to toss some funding their way to help encourage more good stuff. (This is just my opinion.)
Otherwise, stuff can be put on the back burner, while at the same time the community wants said stuff.