@U04BUQET5B2 - do you want it to be a client side or server side programming language? Clojure/ClojureScript language is an excellent, fun and powerful functional programming language. So I would naturally recommend that! Clojure/ClojureScript language leans towards small libraries rather than big frameworks - so I've put some suggestions below, but there are many options and you may get other good suggestions from the community. Serverside programming • Basics: You can build powerful websites fully server-side with Clojure ◦ Use libraries: (Server: https://github.com/ring-clojure/ring + Routing: https://github.com/weavejester/compojure or https://github.com/metosin/reitit + HTML: https://github.com/weavejester/hiccup) • If you need extra interactivity: you can layer in https://github.com/bigskysoftware/htmx + https://github.com/bigskysoftware/_hyperscript inside your Hiccup when you need it. Client side programming (when you need maximum interactivity or building a static website and don't want a backend) • ClojureScript runs in the browser- you can access the full power of React Hooks and the whole JavaScript React ecosystem by building your website with https://github.com/roman01la/uix. You would typically use https://github.com/thheller/shadow-cljs for running/compiling. Combine both Server side + Client side • You can create a client side frontend in clojurescript and backend Clojure and have some of the source code shared between the two since its all one language. • Only do this when ready - as it's a lot more work to learn a new frontend + backend language + libraries all at once.

> do you want it to be a client side or server side programming language? I am mainly concerned with client side programming

ClojureScript might is worth trying out then. It's a small language and has nice capabilieis like live code reloading: https://www.youtube.com/watch?v=KZjFVdU8VLI

ClojureScript, of course. Or "Other": Javascript https://opensource.com/article/17/6/functional-javascript

ps Rescript and Purescript are strongly typed. No fun there.

Clojure then Clojurescript because learning Clojurescript first is harder due to interop with JS and tooling

@U0CKDHF4L - I get where you are coming from, but I think we should avoid putting up large barriers (like learning Clojure) when a new member just want do some client side programming in ClojureScript. It might be more off putting than encouraging. The learning materials and tooling for ClojureScript are certainly good enough to just jump in and use. Many ClojureScript libraries require no JS interop.

ClojureScript might make you more hireable? It seems like companies have a harder time hiring ClojureScript devs than Clojure

At the last 3 companies I have worked at we have had a strong preference for full stack developers. Which I think is reasonable request given how similar Clojure and ClojureScript are. Full stack cuts down a huge amount of inter-role communication when a single developer can build/test/debug/release a feature all the way from the backend to the frontend.

@UJVEQPAKS I don't consider learning Clojure (the core of it) a barrier at all

e.g. type clj , visit https://clojurescript.io/ or https://www.maria.cloud/ and start experimenting

Your second two links both appear to be powered by ClojureScript instead of Clojure, so I think I misunderstood you. I thought you were suggesting that if a user wants to get a taster/experience for ClojureScript in a browser, they first should go on "side quest" to learn Clojure on JVM first rather than just diving into ClojureScript (which is their actual goal). I agree that learning the core language can help in the long term, so I think we're on a similar page to each other.