clojure-style-guide VS papers-we-love

Fixed link to that style guide entry: https://guide.clojure.style/#opt-commas-in-map-literals

Per that style guide, the above map would be formatted like this (on HN, just indent by two spaces):

  {:a 1

As for the broader question of Clojure style, there are style guides like https://github.com/bbatsov/clojure-style-guide and tools like clj-kondo to help learn and reinforce important practices.

Basically, you learn the expected places to put whitespace, make sure to edit your code accordingly and all of the parens will be automatically closed and adjusted. Using parinfer—which you can also combine with the more traditional paredit—makes writing Clojure code a lot like writing Python.

Also, there are guidelines, the styleguide, clj-kondo, kibit etc. And if you don't review your interns/juniors code to teach them good practices - you're doing it wrong (well, this one is true for any practical PL out there).

Another good resource is https://guide.clojure.style/ -- the (unofficial) community style guide for Clojure.

It's not an answer to your question but i can refer you to https://github.com/bbatsov/clojure-style-guide

The same could be said about the "Clojure Style Guide" from the Cider guy. As a matter of fact, there was an issue about it that was quickly declined https://github.com/bbatsov/clojure-style-guide/issues/232

Formatting is not that great, see https://github.com/bbatsov/clojure-style-guide btw

Papers We Love (PWL) is a community built around reading, discussing and learning more about academic computer science papers. This repository serves as a directory of some of the best papers the community can find, bringing together documents scattered across the web. You can also visit the Papers We Love site for more info.

You might find the paper Out of the Tar Pit interesting if you haven't already read it: https://github.com/papers-we-love/papers-we-love/blob/main/d...

The ideas and approaches you talk about evoked some of the concepts from that paper for me. It talks a lot about separating accidental complexity and infrastructure so you can focus only on what is essential to define your solutions.

Sure he was expecting a practical language and was designing one. Lisp was from day zero a project to implement a real programming language for a computer.

Earlier he experimented with IPL and also list processing programming on Fortran. The plan was to implement a Lisp compiler. At first the Lisp code McCarthy was experimenting with, was manually translated to machine code.

Then came up the idea to use EVAL as a base for an interpreter, which was implemented by manually translating the Lisp code to machine language. Around 1962 then a compiler followed.

https://github.com/papers-we-love/papers-we-love/blob/main/c...

I'm in a 4th camp: we should be writing our applications against a relational data model and _not_ marshaling query results into and out of Objects at all.

Elaborations on this approach:

- https://github.com/papers-we-love/papers-we-love/blob/main/d...

- https://riffle.systems/essays/prelude/

The short ask: Anyone know of any projects that bring incremental view maintenance to SQLite?

The why:

Applications are usually read heavy. It is a sad state of affairs that, for these kinds of apps, we don't put more work on the write path to allow reads to benefit.

Would the whole No-SQL movement ever even have been a thing if relational databases had great support for materialized views that updated incrementally? I'd like to think not.

And more context:

I'm working to push the state of "functional relational programming" [1], [2] further forward. Materialized views with incremental updates are key to this. Bringing them to SQLite so they can be leveraged one the frontend would solve this whole quagmire of "state management libraries." I've been solving the data-sync problem in SQLite (https://vlcn.io/) and this piece is one of the next logical steps.

If nobody knows of an existing solution, would love to collaborate with someone on creating it.

[1] - https://github.com/papers-we-love/papers-we-love/blob/main/design/out-of-the-tar-pit.pdf

Here is a great Repo on GitHub named paers-we-love. You will surely find some great papers there and also some good other resources. Hope this helps.

However, f and g are interchangeable anywhere else (this is not actually true because their addresses can be obtained and compared; showing that a C-like language retains its referential transparency despite the existence of so-called l-values was the point of what I think is the first paper to introduce the notion referential transparency to the study of programming languages: https://github.com/papers-we-love/papers-we-love/blob/main/l...)