clojuredesign-podcast 2022-03-25

neumann23:03:21

@leif.eric.fredheim In the #announcements thread about Lighthouse, you mentioned how we’ve complained about Kubernetes YAML on the podcast before. That made me think of a general principle. I think lighthouse is a great example of keeping information in a useful format for computation and then “rendering” out the representation you need at the very end.

👍 1

neumann23:03:10

What works well for computation is likely different than what works well for integration.

neumann23:03:45

@U0510902N and I like to call it the “internal” representation vs the “output” representation.

leifericf23:03:45

Yeah! I think that’s a good principle in general, even outside of programming. For example, AsciiDoc and Markdown serve a similar purpose for having a single human readable source and “compiling” to several domain-specific target formats, like PDF, HTML, EPUB, Word, etc.

leifericf10:03:34

Maybe https://github.com/weavejester/hiccup and https://github.com/noprompt/garden are better examples than AsciiDoc and Markdown, if we want to stay within the realm of Clojure.

neumann19:03:30

Hiccup is a nice way to express information that can be transformed 1:1 to markup. I haven't gone down the road of writing code that manipulates hiccup, but I certainly enjoy using it.

👍 1

2022-03-25

Channels