« Oatmeal

Tagged "clojure"

Follow this tag

In reply to: What a Clojure Web Framework might look like - LispCast

On the power of plug-ins (as opposed libraries and frameworks):

you can install the plug-in and activate it and it just works and there’s no other integration required because it’s all done through these known hooks, these published hooks that are part of the core.


In that way, you’re actually trying to build an ecosystem, an ecosystem of plug-ins that provide a lot of the functionality that you need.

I like the use of ecosystem” in this context. I think the web would benefit from more folks thinking of web-based tooling in the context of how it fits into the wider ecosystem of the web itself. Rather than see the web as a means of distribution, think of it as a coherent space unto itself, like a continent with unique biomes and ecologies. Does your tool fit into the ecosystem? Does it work with, or against it?

Facebook and similar walled silos ignored the ecological aspect of the web, whereas the IndieWeb attempts to integrate itself, and to extend the web’s existing ecology.

In reply to: Key Lesson: Building CloudRepo With Clojure

In Clojure, if you adopt the Data is the API paradigm then designing systems is primarily about identifying your data and how it flows through your functions. Data can be represented by a small set of abstractions, in particular a map, and so would reduce the requirement to write the glue code that is so commonplace in Java (a.setFoo(b.getFoo) , etc.).

Also, if functional programming is your jam, don’t miss this article’s use of Data Flow diagrams to describe Clojure code 💯

While reading Clojure for the Brave and True, I’ve also been working my way through the lisp koans. At this point I’m pretty obsessed with lisps, and am growing increasingly excited to use one for a project. Generally speaking, I feel most cozy working with a really small (some would say constrained?”) toolset. Lisps most totes fulfill this coziness.