edn VS futurecoder

> 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...

I have recently found a neat new (to me) resource for learning Python. It's called futurecoder and you can find it at https://futurecoder.io.

If you’re interested in learning Python, i’ve been messing around with this site today and it’s been pretty cool! link

here's how I started my journey (SWE at aerospace now)

1.https://futurecoder.io/

futurecoder — interactive, includes integrated debuggers, enhanced tracebacks, hints for exercises and more

I really enjoyed https://futurecoder.io when starting. It makes diving deeper into udemy courses very easy, and helps to actually read and understand code.

As for courses, there are many great, free Python courses on YouTube, but I recommend this Harvard CS50 Intro to Programming with Python course. Or, if you are looking for something a bit more interactive, check out futurecoder.io. I just discovered it recently, and it is great (completely free, as well).

https://cs50.harvard.edu/python/2022/ https://futurecoder.io/ https://roadmap.sh/python https://www3.ntu.edu.sg/home/ehchua/programming/webprogramming/Python1\_Basics.html#zz-1.

I believe your application needed to be "complete" in order to be eligible. Good luck next time! There's also lots of other resources for learning python like Coursera's programming for everybody or http://futurecoder.io