"Better" in what sense? Impossible to give any advice without knowing exactly what you want to achieve.

You are right @U2FRKM4TW. I was mainly just thinking that coming from React.js and JS it is such a standard practice to make a component with a useEffect hook where fetch is called, which uses setState to update a value which then gets displayed. Is there a similarly standard approach for this in CLJS with Reagent? I have looked into cljs-http, core.async and even js/fetch . But I'm not quite sure about which one to use in this scenario: I simply need to fetch something from and external HTTP API and display it in a reagent component.

Even in React, using a hook is a practice, not something standard.

You can use hooks with Reagent just fine. Or you can use atoms. Or you can use re-frame. Or maybe something else.

Generally, people don't use hooks with Reagent simply because Reagent atoms are simpler and sufficient.

> I simply need to fetch something from and external HTTP API and display it in a reagent component. If you care about nothing else, then your current code LGTM.

Thank you for your response. i'm still quite new in the Clojure world. When would it make sense to make use of re-frame?

When you have a decent amount of state that you have to manage.

Yes that was also my understanding 🙂 Thanks again for responding so quickly and well @U2FRKM4TW

interop with javascript is at least a lot easier

also, the dev-experience ones you get used to a REPL, hot-reloading etc

I’m almost done with an app using Krell and I had to interop quite a bit with react libraries, so I think it would be awefull with Elm to be honest

here’s one experience report https://www.youtube.com/watch?v=geeK1-jjlhY

For me... the ability to use Clojure Script interop with Node/TypeScript because of WASM

but what about other great Elm benefits...like refactoring and maintenance of a codebase, when you can literaly dig into some specific part that you still remember about ...and then for the rest ... compiler directs you. Don't get me wrong... i just recently "moved" here... but for reasons around how Elm core team drives development of Elm... where you have a feeling that Elm is just a private project... shared with public... and that rarely community is heard

But i am still not fully sure, that i did the right decision. I still try to persuade myself i did.... every day

so i am interested in others opinion

I think the role you use a language (contractor, enterprise employee, cofounder) will impact your reasoning to keep commited to Clojure

what do you mean with that exactly?

for example.... I think many of us want to use a popular language because we think that helps us find a job

even though Clojure is simple... it can take time to learn... so demand can be high in the market and there is a barrier to entry

contrast that to JS... low barrier... bigger market

but more competition

aha...

that's why I use JS, Typescript, Clojure and CLJS... it gives me both strategies

big fish in small pond (I am still a small fish)... or small fish in big pond

other than that... ignoring any market reason... just pick what you like to work with

would you say (since you use both worlds) ... that for instance.... you need to equaly frequently devote time for maintaining the past projects... (updating, upgrading packages...) or would you say that Clojurescript allows you to do that less frequently. This is one really big plus for Elm ... you might be aware of, for some, slow development... but for some... this is a huge plus.

or your two ponds require equally amount of effort for this? :)

Clojure is incredibly stable and requires very little maintenance... but Node seems to be always breaking things.

Also... Node added a really weird way of supporting 2015 ecma script modules... where you need to copy all your files to an .mjs extension.... but I do like Node because it's rapid when building things.

Clojure takes more thought but over the long term... much more stable... it's a trade off

(or value1 value2)

Note that in both cases the second value will be used if the first one is false.

oh yeah that actually works

probably it compiles to the same expression

thanks

Re-frame uses Reagent. Reagent uses React. Regardless of what you use, in the end you will have a JS file or files that browsers can run.

A react component is usually a function that returns a "react element"

which is an object you get from calling React.createElement(...)

A reagent component is usually a function that returns "hiccup" data, which is a format that can be converted to a react element

aha... so Reagent uses React functionalities... which i need to be aware of then. :) and the output of a project is vanila JS. ok, thanks!