Clojurians Log v2
clojure-uk
Good Morning!
👋
Anyone know an android/ios developer looking for a small side gig?
I can do React Native if that is what you are looking for
You know it's going to be a good day when you upgrade IntelliJ, and it refuses to let you work on your (non-android) project anymore, because you don't have an Android SDK installed 😁
@djm_uk Is that the April update that folks were asking “Does it work with Cursive?“?
It was released yesterday.
Does it work with Cursive?
I was surprised to see how popular Cursive is, on the State of Clojure results
Yeah, I’m surprised too. I don’t like big, bulky, Java IDEs 😞 I used Emacs for years (technically “decades” but it was off and on), then switched to Atom, then VS Code (the third most popular Clojure editor).
I never got the hang of VS Code. I'm generally uncomfortable without vim's modal editing, but have been having some fun with emacs recently.
https://marketplace.visualstudio.com/items?itemName=vscodevim.vim ? 🙂
Sure, but then I could just use vim instead ;)
I wonder how well it works though - when I used to have to use Eclipse, there was a vim plugin that worked pretty well (despite a few rough edges). Now that I have to use IntelliJ, I have found that the vim plugin conflicts with IJ's own keybindings way too much
moin moin
mawning
morning
Morning
Morn'
Wee, inter-thread communication pain 🤦
always fun @carr0t - use a queue/stream/chan ?
Naah, I was just being a moron
I had a (try ... (a/go ...) (catch ...) (finally ...)) where I was assoc ing an object into an atom in the try and expecting another thread to be able to see it. But I had put a form to dissoc the object in the finally to clean up if there was an error, when it should have been in the catch and the async body in the go block. As it was the function was returning (because async), which was meaning the finally was executing and cleaning up the object before the other thread had chance to see it
@carr0t maybe a bit late... but I think the (preferred) way for observing changes to an atom is with agents and that would be async as well and on another thread.
But if the agent is async, how can I be sure that the value has actually been set before doing more work which is dependent on the other thread having the newly set content visible?
Now I just have more ring/Jetty async fun, and it might well be that the answer is "stop using Jetty, it's making your life harder" ;)
haha, i don't think i've used jetty for a very very long time
being a moron is my biggest problem too 🙊
This is my problem:
ah, yeah... finally can be something of a pain if you mix sync and async contexts... i generally force things to be async and then just use whatever async equivalent of finally you have
Turned out I also needed to upgrade the version of Ring to fix some issues, but not upgrade it too far... https://github.com/ring-clojure/ring/issues/436 😉