I WANT MORE BRACKETS!
You sure you’re alright?
- the whole world except a few brave men and women out there
First and foremost, I am feeling fine, thank you very much.
Having the brackets surrounding code 🤯
whoa, this needs to stop!
The elephant in the room:
Who would have guessed, it was both delightful and tough to do.
Clojure excels when it comes to logic, data mangling and ease of development. So this was true for most of what I did.
But what did I do exactly? Well, I wanted to see if I could setup an ugly one-page-app that would show events and lets me filter them.
Was it worth it? Absolutely. The data is a real big chunk, so speed was crucial and well, without any optimization (memoization or a lookup table) it turned out usable.
Being all functional, a implemented a basic state engine utilizing clojure’s atom. This was nice. What wasn’t nice was the interactive JS part, but it gave me a nice little practise around event based programming and async promises. I skipped building a more sophisticated bus, it had hurt a little first, but it was absolutely worth it.
I made this little project the most simple way, with the least dependencies possible. Yet, almost everybody else in bracket-land seems to use shadow-cljs (Source)
Go, check out the code. Yes there are brackets, you can grow past that fact, can’t you?
clojurescript-web-app-demo on GitHub