hmm https://stackoverflow.com/questions/27246740/exclude-certain-clj-namespaces-from-compilation-in-leiningen

You need to run lein clean between the builds or specify a different target directory in the profiles

(sounds like you are aot compiling)

:target-path "target/%s/" helps as well. %s gets replaced with the build name, so that each build is isolated (instead of having competing builds mutate the same folder)

thank you; unfortunately neither of those suggestions prevented code being pulled in from an unwanted dir (e.g. src/desktop classes go to the server)

I'm pretty sure there aren't any dependencies between the namespaces to account for their inclusion

Found it: https://github.com/clojure/clojure/blob/ee3553362de9bc3bfd18d4b0b3381e3483c2a34c/src/clj/clojure/core.clj#L5950

Thanks Tim. Looks interesting. Seems that and Amazonica are the two main ones out there.

I've found https://github.com/riverford/objection to be somewhat underrated and it tends to be the first thing i reach for

I don't, but I know that some do and really like it.

@U76D9RZRR We've used Component very heavily in production for years. We find it great in the REPL too. What sort of problems are you having?

Is it because you're trying to use the "Reloaded" workflow and it's causing you problems? We do not use that workflow -- we don't need it.

Eric Normand talks about this in his REPL-Driven Development course -- and Stu Halloway talks about it on podcasts and in his conference talks. If you have good practices around the REPL, you do not need "reload" / "refresh" workflows.

(it is a good amount of ceremony when you only have, say, 1 or 2 objects)

The "opinionated" installation guide for ProtoREPL for Atom advocated turning on the full refresh workflow but it causes lots of problems for beginners. Chlorine also supports it but I advise people not to use it for the same reason.

Component solves a problem that you don't have in simple programs -- but you do have in spades in a large, complex program.

I think the latest hostility toward reloaded workflow is overblown.

one should always consider whether there is a more appropriate code structure with fewer dependencies

I agree with Eric and Stu that it is unnecessary -- and it certainly seems to cause endless problems for beginners (since they don't understand what's really going on, under the hood), so I encourage folks to avoid it until they really think they need it (which they don't).

but it’s nice to have a guaranteed clean env to check for slimage

If it works -- which it doesn't for a lot of people.

I’m kind of perplexed by the idea that it doesn’t work for folks.

Always did what it said on the tin for me.

but idk

perhaps it’s somewhat unintuitive?

Yeah, for some folks It. Just. Works. I've had it work perfectly in some projects and not at all in others.

what did it do when it “didn’t work”?

I don’t even understand the statement! 😄

Like, it just hung? It hit errors? You got errors after it ran?

(I’ve hit loads of unexpected behavior/errors before running reload. Usually to do w/ interop.)

it's bit of an unfortunate tradeoff - both Reloaded and manual management have some gotchas I think Reloaded could be improved, in the end it's a fancy name for 'automation'. The current status of that automation is relying in a slightly unmaintained library that doesn't document all its intricacies Raw clojure isn't perfect either - keeping track of namespaces in your head or intricacies related to the compiler isn't perfect either One always can experiment with both approaches, document observations and draw conclusions

If we had searchable archives here, you could just search for the problems many people have experienced with it... 🙂

🤷

I'm not even sure what people mean by reloaded? tools.namespace ?

I use cider ns refresh all the time, without using a component library

Its pretty great, for when you want to make sure your code compiles without restarting the repl

I do think there are certain things it can't clean though, like thread locals and all

But just gettijf rid of bindings and letting me know I've got all the right require in place and declared functions is great

I use the "reload" workflow in most of my projects, and indeed, sometimes it works, sometimes it doesn't. With Clara-Rules, for example, I wasn't able to cut an approach that works without reload

But for multiple other projects, manual load-file / other tools work fine too (if there isn't too many protocols/records)

Nowadays, I use a mix of approaches. The thing is, I work mostly with very small microservices now, so the dep graph is very simple to understand (and maybe that's the reason the "reload workflow" works so well for me 😄)

I still think I'm confused about what is the "reloaded" workflow. Initially, from Stuart's talk it was about being able to perform starting and stopping logic in the correct order to initialize and shut down resources

For that, you need a Component like system

But there is also the issue that load doesn't unload. And sometimes, you just want a clean REPL without having to restart it (because its so slow to restart). Tools.namespace is targeting that issue.

Sorry for late answer, @U04V70XH6 . I used Mount but occasionally one namespace didn't compile anymore (No matching field found: stop for class mount.core.DerefableState) and the only way to fix the issue was to restart REPL - which I'm learning to avoid. I have a personal learning project in which I'm mostly trying to learn a personal efficient REPL workflow. I think next I'm trying to do the same project without any application state management library and see how REPL driven development feels like that way.

Clojure is really a great language and I think REPL is the soul of Clojure - I really want to learn to use REPL smoothly when developing Clojure code.

Actually I have fallen in love with Clojure so much that I gave up my good corporate career and moved to a smaller company just for the chance to do Clojure full-time. 🙂 Well, I have paid my mortgage and my kids are grown-up now so I thought that I can do for the rest of my career what ever I want - and I want to do Clojure. 🙂

BTW. If you guys know links to good REPL driven development sites / pages, please provide links here.

I have watched Purely Functional TV's Repl Driven Development course and I must say it is really great (thanks Eric!).

Also "Chicago Clojure - 2017-06-21 - Stuart Halloway on Repl Driven Development" (https://vimeo.com/223309989) is really wonderful. After watching this video I realized that I have done REPL driven development totally wrong - editing stuff in a REPL editor. After watching that video I immediately started using a scratch file (for REPL experimentation) that I save for future review.

If I remember correctly Stuart somewhere said that he mostly compiles namespaces one after another following the dependency graph manually to better understand what kind of dependencies there are. I have tried to do that also myself more now (and try to avoid fixing issues just by "restarting repl").

... @U04V70XH6 already said it in this thread, I somehow missed it when reading this thread the first time: "Eric Normand talks about this in his REPL-Driven Development course -- and Stu Halloway talks about it on podcasts and in his conference talks. If you have good practices around the REPL, you do not need "reload" / "refresh" workflows." => Maybe that's what I'm trying to achieve: "good REPL practices". 🙂

Note: Those videos do not go into any detail on the use of Component -- it is simply apparent that they do use it in their code base from seeing it mentioned in the video.

I believe I have heard him mention that he does not use the "reloaded" workflow that some other Clojure devs use, instead choosing to force himself to remember to explicitly resend (via a single keystroke configured in his editor) any modified functions to the REPL, to redefine them.

Here's an example he made awhile back: https://github.com/seancorfield/usermanager-example