4ever-clojure VS clog

I found this to be an awesome bridge between reading about the theory and actually writing code that works: https://4clojure.oxal.org/

This is for general Clojure, I’ve had a lot of fun and learned a lot from it (and the original): https://4clojure.oxal.org/

It's normal to apply methodology like this to clojure when transitioning from other languages. When I was first learning I did a bunch of exercises on 4clojure and my first attempts looked like this. Then I found loop from the standard library and I understood immutability but relied on loop to do anything to collections of things. Eventually, after looking at the answers, I started to get familiar with the standard library. Then my solutions started to look like the two line solution above.

4Clojure is here now: https://4clojure.oxal.org/. It runs locally in your browser.

Go to https://4clojure.oxal.org/ and solve some stuff. And don't learn any theory. You're thinking how a C# developer thinks and you think you need to learn some kind of packages by heart or something.

I learned by reading through a book, then working through problems on https://4clojure.oxal.org/. If you've got JS experience it won't take too much effort to pick up. Don't get too carried away with forming the perfect tail recursive pure functional monad or whatever. Get into just doing what you're trying to do quickly, then after you're competent, read other people's code to correct your style.

I'm only a couple months into learning Clojure too, but I found solving a problem myself and then seeing others solutions on this website https://4clojure.oxal.org/ was invaluable for learning to think like a clojurist.

I'm trying to learn Haskell and found https://4clojure.oxal.org/ very helpful. https://tryhaskell.org/ was also nice, but it is limited in scope as compared to its Clojure equivalent.

The actual address is https://4clojure.oxal.org/

Reminds me of the approach of CLOG (Common Lisp Omnificent Gui[1]) and its ancestor GNOGA (The GNU Omnificent GUI for Ada[2]).

They also integrate basic components and even graphical UI editor (at least for CLOG), so you can essentially develop the whole thing from inside CL or Ada

[1] https://github.com/rabbibotton/clog

[2] https://github.com/alire-project/gnoga

For me David Botton [0] with his work including code, support and videos is doing very nice work in this direction.

I use SBCL for everything but work because I cannot get; we are getting there, but like you say, it’s such a nice experience working interactively building fast that it is magic and it’s painful returning to my daily work of Python and typescript/react. It feels like a waste of time/life, really.

[0] https://github.com/rabbibotton/clog

I was following along on the Windows page and didn't check back on the main README to see if any of the other instructions would help.

It the answer is "latter", then you could look at Common Lisp and Reblocks (https://40ants.com/reblocks/) or CLOG (https://github.com/rabbibotton/clog).

I haven't used Clojure professionally in 10 years so with a grain of salt here are my thoughts as only one other person answered...

CL over Clojure: it's the OG Lisp that the creator of Clojure used and wanted to continue using but faced too much resistance from management afraid of anything not-Java/not-Oracle, or not-CLR/not-Microsoft, etc. Clojure shipped originally as "just another jar" so devs could "sneak" it in. If you don't have such a management restriction, why Clojure? If you want to integrate CL with the JVM, you can use the ABCL implementation, there's also something from one of the proprietary Lisps. Some useful CL features that are nice in this domain: conditions and restarts mentioned in a sibling comment (very nice to help interactively develop/debug e.g. a selenium webdriver test), ability to easily compile an exe (perhaps useful for microservices, or just to keep your deployment environment clean and not having to care about Lisp), and ability to easily ship with an open local socket allowing you to SSH in (or SSH port forward) and debug/fix/poke around in production (JVM of course lets you attach debuggers to a running process, even certain billion+ dollar companies will have supervised/limited prod debugging sessions for various hairy cases, but it's not as interactive). You should never hear CL advocates claim you can't scale to large teams/groups of engineers or large multi-million-lines sized projects, though you might oddly hear Clojure advocates sometimes claim you can't (and shouldn't) scale to such large projects -- large groups of engineers are a non-issue for them as well though, the challenge is in hiring, not in the language somehow making it impossible to modularize and keep people from stepping on each other.

Clojure over CL: its integration with the JVM is nicer than ABCL's, so if you do actually want a lot of the great world of Java stuff, it's easier to get at. Database integration libraries are better. Access to libs (Clojure or Java) is via Maven, so it's a larger ecosystem with more self-integrating components (especially around monitoring/metrics) than what's available for Lisp via Quicklisp. Clojure is very opinionated, much of it quite tasteful, and that gives the whole ecosystem a certain consistency. (You can have immutable data structures in CL, you can if you want use [] for literal vectors and make them syntactically important e.g. in let bindings, but not everyone will be on board.) Even though its popularity seems to have stopped growing, at least at the same rate as e.g. Go which it was keeping pace with for a while, it's still popular enough with a bigger community; as a proxy measure there are multiple conferences around the world and good talks at adjacent conferences, whereas Lisp mostly just has one conference in Europe per year and only occasional branching outside of that.

If you're doing a client-side-heavy webapp, ClojureScript is still amazing, CL's answers there aren't very compelling with the exception of CLOG (https://github.com/rabbibotton/clog) which takes an entirely different direction than the usual idea of translating/running Lisp on top of JavaScript and its popular frameworks.