Fork me on GitHub
#cljdoc
<
2021-08-16
>
martinklepsch09:08:50

that’d be fine by me 🙂

lread14:08:22

From a purely selfish perspective, learning about helix would be more interesting to me than learning about TypeScript.

lread14:08:41

Yeah, there’s that! 🙂

lread14:08:22

Now that you’ve dug into cljdoc @deleted-user, as an experienced front end dev, how do you like tachyons for styling? I never came to a firm opinion myself.

4
lread14:08:56

Cool, I guess I've not really felt the pain that a tachyons-like solution solves. I remain interested, open-minded but currently neutral.

4
lread14:08:04

I've no clue if bloat is a concern, we'll have to wait on @martinklepsch

lread14:08:08

I don't know if tachyons repetition is necessarily necessary...

martinklepsch14:08:43

Not too concerned, especially if it’s progressive enhancement type stuff.

lread14:08:30

Yeah maybe I don't either, but I didn't like the repetition either and thought maybe some fns could be extracted. But then worried maybe I was creating a kind of style sheet and stopped thinking about it.

lread14:08:56

To not overwhelm/burn you out, maybe start with your TypeScript plan (barring any objections) and then treat helix as a separate piece of work?

lread14:08:54

Dunno, just tying to be thoughtful of all the work you are putting in!

💯 3
lread15:08:52

Not trying to sway you in any way. Your choice! Not sure yet how @martinklepsch feels about introducing TypeScript to cljdoc?

lread15:08:50

I expect maybe he'd be at least a bit hesitant... but dunno!

lread15:08:36

You've made some very good arguments.

💜 3
4
lread15:08:00

But I'm good with @martinklepsch rejecting contributions when they don't fit with his vision for cljdoc. At one point I had contributed a change that included introducing Sass (among other complexities). I was cool with his choice to not accept the PR.

3
6
lread15:08:55

I mean I cried a little bit, but got over it! simple_smile

martinklepsch16:08:18

Heya 🙂 I think there’s a few things to optimize for when it comes to the ts/cljs decision. I think the main things I want to optimize for is enabling potential contributors. To me this means making it easy to get started with the system but also allowing folks to run with their ideas if they feel a lot of energy. While maintainability is important too I think cljdoc doesn’t have the same pressures as a library in terms of backwards compatibility and stuff like that and I like that we can be a bit more chill about letting people take the project in new directions.

martinklepsch16:08:34

In the ts/cljs question I’m leaning towards cljs because I believe it would make it easier for other members of the Clojure community to contribute but also I wouldn’t want to get in the way of shipping a nice improvement to the platform just because it’d be written in typescript. In the end both setups require a build step/probably have similar complications. I’m happy to defer the call to you @deleted-user if you want to make it 🙂

martinklepsch16:08:09

That sounds good to me 🙂

lread17:08:02

Go team cljdoc 🚀!