Clojure from the ground up: roadmap

With the language fundamentals in hand, here’s my thinking for the remainder of the Clojure from the ground up book chapters. I’m putting Jepsen on hold to work on this project for the rest of the year; hoping to get the source material complete by… January?

  • Debugging and getting help
  • Polymorphism
  • Modularization and refactoring
  • It’s not at all obvious what an object is
  • JVM interop
  • The Clojure type system
  • Compiler at runtime
  • Build your own language
  • Performance analysis
  • Parsers and protocols
  • Storage and persistence
  • Networks and messaging
  • Concurrency and queues
Dmitriy, on

Hi! Thanks for the great effort you’re putting to write this book! Do you accept donations?

Rangel Spasov
Rangel Spasov, on

Great stuff! All articles so far have been one of the best resources for learning Clojure from the ground up!

subu, on

waiting eagerly, Thanks and appreciate the flawless explanation.

Jonathan, on

I’d be interested to see some content included on how to build proper applications from the ground up. This tweet of yours pointing to Stewart Sierra’s work comes to mind:

Boris Adryan
Boris Adryan, on

If you’re going to get this into actual book form, I’m happy to go through the explanations and exercises again and tell you were I was stuck and relied on other help.

Peter, on

I especially like the effort to explain how the language works rather than just getting readers hacking away. This makes your book really stand out from common language tutorials. I am excited for more chapters!

Alex, on

This is by far the best explanation of how and why things behave in Clojure. Thank you a lot for all your work and keep going!

Post a Comment

Please avoid writing anything here unless you are a computer: This is also a trap:

Supports github-flavored markdown for [links](, *emphasis*, _underline_, `code`, and > blockquotes. Use ```clj on its own line to start a Clojure code block, and ``` to end the block.

Copyright © 2020 Kyle Kingsbury.
Non-commercial re-use with attribution encouraged; all other rights reserved.
Comments are the property of respective posters.
Also on: Mastodon, Twitter, and Github.