Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2021-09-24

Channels

#clojure-europe
<
2021-09-24
>
dharrigan06:09:34

Good Morning!

seancorfield06:09:50

How's that port to 17 going?

dharrigan06:09:19

All ready to try out this morning. Got a bit tied up with some adjusting some build tools, but nearly there now 🙂

dharrigan06:09:33

I run it locally, on my machine on 17, so it should be okay 🙂

dharrigan06:09:02

🪵👈

djm06:09:55

👋

gklijs06:09:37

Morning, current project is using Kotlin and just a few dependencies, so should be fine to move to 17 when possible. But it will run in a low code setup and no idea when they move the JDK there to 17.

vemv07:09:34

buenos dĂ­as

dharrigan07:09:59

Deployment has gone painlessly, our first Clojure application running in our staging environment on jdk17

🎉 4
javahippie07:09:20

You said you adjusted the build tools? Was it something in the Clojure build tools or in your build infra?

dharrigan07:09:48

we use python to do some tooling

dharrigan07:09:59

like, deploying to ECS, making sure the task definitions are set etc...

dharrigan07:09:38

Funnily enough, this popped up yesterday

javahippie07:09:40

Ah, thanks. So for Clojure it was just “Compile with the new JDK and it works”?

dharrigan07:09:46

Yup. Flawless.

dharrigan07:09:04

I've been experimenting with JDK 17 past day or so, no observerable issues.

dharrigan07:09:15

Before that I was running JDK 16, again, no observerable issues

Jakub HolĂ˝ (HolyJak)08:09:15

One just has to love Clojure 🙂

dharrigan07:09:53

Will monitor for some time (I've also enabled ZGC...will be interesting to see if that and the Shenandoah GC in action)

slipset07:09:02

So reading through a blog post this morning, it struck me that microservices (with a local data store) could be viewed as OOP over http (with all the benefits that would get you, lol) . And it clearly answers why I prefer my functional monolith. But being a bit less smug about it, what would be the Clojure way of implementing microservices. Is that simply eventsourcing?

❤️ 1
slipset07:09:35

Of course, Bobby Calderwood 🙂

⚡ 1
vemv07:09:41

I went ahead and introduced it in a certain project as a consultant (not in Clojure though). It went pretty smoothly but as it happens often, these patterns end up subverted in the name of 'agile'

slipset07:09:31

> Programmers can and should enjoy a lively debate about OO’s merits and drawbacks for organizing code within a single memory and process space.

Fahd El Mazouni09:09:51

would appreciate your help !

Jakub HolĂ˝ (HolyJak)09:09:45

perhaps ask #lsp to document this for posterity?

slipset09:09:08

This is possible, hang on

slipset09:09:42

(with-eval-after-load 'lsp-mode
  (add-to-list 'lsp-file-watch-ignored-directories "[/\\\\]\\ardoq-attachments\\'"))

slipset09:09:25

I guess you could file an issue here, @UKFSJSM38 might be interested, if this is a common path which always should be ignored as pr the third bullet point.

Fahd El Mazouni09:09:16

is this emacs specific ? I'm currently using vscode so I don't really know here I'd put this to have it work

slipset09:09:27

crap, yes, it’s emacs specific. Maybe @U0ETXRFEW can help you

🙏 1
pez10:09:47

Calva doesn’t have a setting for this. I would expect clojure-lsp to have a config for it, but it doesn’t afaics…

pez10:09:19

Let’s hope we get some clarity from the question posted in #lsp 😃

Fahd El Mazouni11:09:08

no answers yet, but I assume if the emacs lsp integration can handle it, then it's probably doable with some config. unless it just filters out said files once the emacs integration gets lsp results

ericdallo12:09:42

for this specific problem, the correct way to fix that is changing the setting ignore-classpath-directories to true : https://clojure-lsp.io/settings/

ericdallo12:09:52

this is not related with file-watchers

Fahd El Mazouni13:09:00

god damn it's right there in the documentation, I missed it

ericdallo13:09:42

We can probably make it clearer in the docs :)

pez14:09:20

Ah, great! Nice that my expectation that this would be configurable regardless of client were met. 😃

slipset15:09:17

Very off-thread, but I’ve used clojure-lsp for about half a year, with almost no config tweaks. Thanks for setting same defaults!

ericdallo15:09:04

Glad to hear it :)