Clojurians Log v2

@favila @souenzzo thank you both for your comments. I understand how Pathom's use of Clojure's namespaced keywords makes it difficult to use Pathom without Clojure, but I was hoping someone came up with something. I'd just love to be able to leverage its power in other ecosystems - I think it would be a great tool for introducing Clojure.

FWIW not having field-level concept-name disambiguation mechanisms is my biggest frustration with the entire information system computing ecosystem. Namespaced fields are so obviously a necessary idea, and whenever I have to touch architectures that don’t have them from clojure it’s a huge pain (e.g. sql, json, graphql, etc etc etc). The only mainstream thing that has something like it is xml and things that inherit that legacy, like RDF. (arguably not mainstream)

https://imgflip.com/i/7xgxr9

Yeah, namespaced keywords are a very underrated idea and it would be nice if something similar existed outside of Clojure. The closest thing I can think of is some of the ideas from the Glom library https://glom.readthedocs.io/en/latest/tutorial.html#access-granted but it's still a bit of a stretch to draw strong parallels.

In principle: consume some query format and translate it to EQL?

Depends on what you mean by “outside” and “communicate”. Do you have something in mind?

Some way to to run queries against Pathom from Python and/or JS.

Does it have to be in-process, or is IPC fine?

IPC is the approach I just mentioned: expose some endpoint that accepts some data format you can translate in and out of eql and clojure data

Pathom runs on clojurescript, so I guess in theory you could call it from js code in-process

I don't have any real requirements right now, I'm just trying to understand how one might approach it and whether there's been anything already built to this end.

If you just want to use pathom to implement a service called from elsewhere, it’s no different than e.g. a webapp that has a sql database--no one needs to know, you just implement your own interface. But if you want to actually use pathom as pathom it depends pretty heavily on edn data and namespaced keywords as the language of the system--anything that exposes it to other languages is going to have to cross that hurdle.

maybe just dealing with it as a wire format is possible. E.g. you could use an edn or transit implementation in another language (js and python definitely have those)

It could be possible to have a nice integration with JS imagine to expose "smart-maps" as a raw javascript object, for example: https://blog.wsscode.com/alternative-to-clj-js/ But currently, it is all in our imagination.

about @favila meme:

(defn print-name [user] (println (:org.user/name user)))

package org

class User {
  String name
}


// another file

import org.User

void printName(User user) {
   println(user.name)
}

Languages that uses "qualified keywords": https://en.wikipedia.org/wiki/Nominal_type_system Languages that uses "simple keywords": https://en.wikipedia.org/wiki/Structural_type_system (as clojure can do both, you can decide which tool is better for your problem)