When you say "write some cross-platform macros" what do you mean?

What is the problem you're trying to solve?

macros that can be consumed from both clj and cljs codebases

Most macros you write will have that property.

Unless you're using self-hosted ClojureScript macros will be evaluated as Clojure whether you're targeting the JVM or JavaScript, which is fine.

> for larger projects cljsbuild will fail because the conditional will return the wrong thing I believe What do you mean?

> Most macros you write will have that property. not sure. If I need to emit x or y depending on the consumer's platform, I need a hack such as the linked one in Stackoverflow. I found this pattern https://github.com/jeaye/orchestra/blob/4e7fd20ab6596528560c730d1425a77edc1ea2e9/src/cljc/orchestra/core.cljc#L21 which solved my issue

If you need the runtime behavior to be different depending on the host language why not macroexpand to a function call. You can then make the implementation of that function platform-dependent in one of the usual ways.

Just to be clear: are you questioning the need for a cross-platform macro?

No.

Again, if you need the runtime behavior to differ depending on the host language you could have your macro expand to a function call where the function being called has both a Clojure and a ClojureScript implementation.

Yes. More or less I did that: grab (-> &env :ns some?) in the macro and pass that value as an argument to functions that are invoked from the macro

You don't need that hack.

Just define a function that wraps the platform-specific behavior and have your macro expand to a call to that function.

Like so: http://bit.ly/2KHoS06

Note that example.macros/function's behavior differs depending on the runtime platform.

I'll try it thanks! It might get muddier though for things that actually need a macro, and/or per-platform ns variations (`clojure.spec.alpha` vs cljs.spec.alpha). I'll have to see.

Yeah, I'd be interested to see a situation where this breaks down, but I'm having trouble imagining one.

Note that there's no reason why function couldn't be defined in a namespace that has two completely different implementations, one .clj and one .cljs.

https://github.com/denoland/deno_install

The creator of node js left around 2012 and went to create Deno

It still uses the V8 but also is written in Rust

I am wondering if the use of Deno will impact whether Clojurescript uses npm and node js, because JS keeps forking into different projects

I think Clojurescript is good because it can adapt to the JS stuff as JS keeps changing

ClojureScript isn't restricted to a single JS runtime

yea, exactly

Vert.x is using Rhino and Nashorn runtime machines… so Clojurescript can adapt to anything

But if Deno stays unpopular, you probably won't see a lot of cljs tooling around it

my theory is Google pushed some of these ideas with V8 and Golang, to get around using the JVM

because of the lawsuits between Oracle and Google for the past 10 years or so

But NodeJS doesn't use the JVM. So what would be the problem of it over Deno?