4ever-clojure VS edn

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/

> was utterly surprised how no one ever apparently has thought to create a configuration/templating system that's basically a fancy library on top of Scheme.

There's Clojure's extensible data notation: https://github.com/edn-format/edn

A thin language layer around edn/datalog, the query language

EDN (Extensible Data Notation) is a subset of Clojure: https://github.com/edn-format/edn

It is:

- Streamable

- Extensible

- Whitespace-insensitive, but there are formatting conventions for readability

To begin with, EDN is somewhat like the JSON of Clojure. And regarding the code is data/data is code nature of Clojure, it is Clojure. It doesn't have some of the vagaries of JSON, and it is also extensible.

Alien is not a reason something is bad, just that's it's unusual. JSON was a bit alien when it first arrived as well, as everyone was used to XML at the time.

`{num 5, val 4}` looks fine to me, but we can do even better! We already know objects/maps are always in pairs, so we don't really need that comma either. Just do `{num 5 val 4}` and we save yet another unnecessary characters.

Of course, I didn't come up with this format myself, what I actually want JSON to be is EDN (https://github.com/edn-format/edn) which is a standalone format but also directly used in Clojure, so it already exists inside a programming language and works very well. There keys are strings though, so you example would end up being `{"num" 5 "val" 5 "person" var}`, where commas are optional.

I just checked out the spec, and it gets pretty ugly in the Table section. A lot of the json examples are both shorter and IMO more precise. Stuff that’s not allowed with [table] is allowed with [[table]], and it’s confusing to understand what level of depth I’m at.

I’ll take edn over any of “em. https://github.com/edn-format/edn

As XT is written in Clojure and it natively supports Clojure’s data types, we were not satisfied with available JSON types and decided to give EDN a try - that way we would have way more supported types:

Compare the nightmare that is pickling with how simple it is to serialize pure data with edn in clojure. What ends up happening is people passing around JSONs or whatever and writing parsing/encoding code at each end, which makes things unnecessarily more complex, and dangerous, and error prone, and boring, etc...