This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-11
Channels
- # announcements (1)
- # babashka (70)
- # beginners (8)
- # calva (5)
- # cider (9)
- # clojure (48)
- # clojure-austin (68)
- # clojure-europe (29)
- # clojure-norway (30)
- # clojure-uk (5)
- # clojuredesign-podcast (2)
- # cursive (19)
- # datomic (10)
- # emacs (11)
- # events (2)
- # exercism (4)
- # fulcro (2)
- # hyperfiddle (29)
- # introduce-yourself (2)
- # jobs-discuss (4)
- # kaocha (1)
- # leiningen (8)
- # lsp (8)
- # malli (2)
- # matcher-combinators (20)
- # nrepl (15)
- # off-topic (33)
- # reagent (7)
- # releases (4)
- # shadow-cljs (42)
- # spacemacs (6)
- # sql (6)
- # squint (10)
- # vim (3)
Binging some tv show: https://youtube.com/watch?v=nYUz7YKmg2M
trying to deploy an API on a fresh server, pre-requisites are always a surprise :^)
haha nice! @U0482NW9KL1 what kind of API?
Exploring XTDB 2 in the cloud @ AWS.
Polishing https://github.com/samcf/ogres for a 1.0 release and marketing push 🌟
> @U0482NW9KL1 what kind of API? A (clojure-based) API for some internal management/processing of ad-campaigns that we run :^)
(HTTP, but not really RESTy 😆)
Also I was working on my project but today I'm taking a break: https://gitlab.com/invertisment/rnht/
at work: another data flow into our kafka stream. oss: continuing to poke at an alternative to clojure.test
Graphql service for a graph database
Setting up GitLab CI pipelines.
I've already failed at setting up a CI pipeline this week 😅, might have a 2nd attempt on the next one
I've been contemplating this post about making the indie web easier (https://gilest.org/indie-easy.html ) the last few days. I'm not sure clojure has much to offer on this score but I've been exploring tiddlywiki as a possibility (verdict: maybe?). I do miss the indie web though.
I’ve been using Python a bit lately (yeah, yeah, I know. I’m not too happy about it either. But the APIs I needed were there), so I’ve been using my company-provided CoPilot, which I have integrated into both Vim and Emacs. CoPilot is actually really nice in Python as it fills in a lot of boilerplate for me.
Anyway, I’m back to Clojure right now, and it’s the first time I’ve used Emacs on Clojure since I installed CoPilot. I created a namespace, and the first thing it tried to do was require [clojure.core.reducers :as r]
which seemed like an odd first choice, but OK. I added clojure.string
and then it wanted to bring in
which makes sense (even though I didn’t need it).
But the reason I’m here is because I added metadata to the namespace, starting with :author
.
The first string it gave me was "Miguel Alba"
. I started typing "P
and I got "Paulus Esterhazy"
. Then I finished typing "Paula
and it gave me my own name.
This is both totally in line with what I would have predicted, and totally weird.
Curious how your Clojure experience compares with Python. I gave it a try recently and my main takeaway is its approach to closing parens is to throw 3 or 4 or 6 more on at the end just in case. I’ve considered trying it with paredit to see if that makes it less tedious to deal with. It often has reasonably useful suggestions if I didn’t have to spend so much time fixing that issue in particular.
I opened a new namespace and required spec.alpha
, then started pasting in webidl definitions as comments and copilot was generally able to get something like 70-85% of the structures right. I adjusted naming conventions of some code it produced and when I would paste in new idl comments it seemed to glean the style appropriately for new code.
I like Vim, so I use Emacs in evil mode. This means I can always find matching parens, though I do miss paredit.
I reference a lot of my own Clojure libraries, and it doesn’t know about them, so it makes some bizarre assumptions about what functions are available from my namespaces
Copilot is definitely getting better at suggesting Clojure code. I find it's at its best when writing tests: once I have a few tests in place, it's pretty good at suggesting additional cases to test -- and it's nice to have the "boilerplate" of tests inserted almost automatically. It's also very helpful when writing documentation, because it seems happy to concoct sentences derived from stuff in the code and from docstrings and comments.
Yeah, when I can set it up for success and let it do the equivalent of smartfilling in excel for several suggestions in a row it feels very useful and the templates/patterns it can recognize from context are pretty impressive. It also seems (in my experience) to do better about not blowing up the syntax when it’s writing whole top-level forms rather than inlining suggestions elsewhere
@U051N6TTC when you say > ...though I do miss paredit. > Do you use evil-cleverparens or lispyville? If so, are they missing things from paredit?