I saw this headline, saw the tweets and missed what this was about.
Then read Simon Willison's breakdown and got the 'Aha!'.
I like what they've done, played with it and immediately started to plan how I'd try to implement it myself.
I guess this will be the way to go, for development setups instead of using a dedicated machine. Especially when mobile clients are created for Sprites.
Try the reverse, get a document that is critical of the US foreign policy, from China, and ask your well known brand LLM, to convert the text from PDF to epub.
It'll right out refuse, citing the reason that the article is critical of the US.
Because of him, I installed a RSS reader so that I don't miss any of his posts. And I know that he shares the same ones across Twitter, Mastodon & Bsky...
I guess it's hard to switch from a working setup that you've invested time in.
Especially since you might not be familiar with the new one.
Personally, I'm trying out things in VS Code, just to see how they work. But when I need to work, I do it in Emacs, since I know it better.
Also, with VS Code, just while trying it out, simple things like cut & paste would stop working (choosing them from the menu, they would work, but trying to cut & paste with the key shortcuts and the mouse, wouldn't). You'd have to refresh the whole view or restart it, for cut & paste to become available again.
I know of UNIX parameters, with a single hyphen & a single letter, and GNU parameters, with a double parameter and a word. But a single hyphen and then a word: *mind broken*.
When I first saw that on Terraform, I was upset & conflicted.
OK, I know that Java also has mental parameter options like that ('-version', note the *single* hyphen followed by, gasp, a word!), but I just dismissed it as weird enterprise-ism.
Then I saw that this 'single hyphen + word' was an accepted convention for parameters, in the Go world & I was disappointed.
Glad that this package is fighting the good fight.
Somebody brought up a point about outdated documentation.
Currently https://clojuredocs.org is sort of the go to place.
It wins due to Google algorithm.
I wanted to add the ability to vote on answers provided there.
So that you have the ability to see the most relevant/popular answer, rather than the oldest.
Raised an issue on the repo, four years ago now. No response:
And why do I mention Google algorithm? Because there was another effort
that tried to create a (debatably) nicer documentation, but due to lack
of Google traffic, it died. See: https://news.ycombinator.com/item?id=8027119
For a more eloquent argument on its uses, see this blog post:
> I found myself frustrated a lot when I used it two years ago.
Sad to hear about your experience.
> A lot of abandoned libraries. There's not a huge ecosystem around it compared to golang
I found it to be the opposite. In Clojure you have Clojurists Together: https://www.clojuriststogether.org which funds people to work on Open Source libraries.
And more importantly there is Clojure Commons: https://github.com/clj-commons which takes popular Clojure libraries, that are no longer being supported and carries on looking after them.
When I found popular Go libraries that have been abandoned, I asked in the Go community, if there are such initiatives, especially seeing how Google is behind Go. When people didn't understand what I meant, I pointed them at the examples above, from Clojure. To which their response was "TIL, Clojure, never heard of it before! No, we don't have such initiatives in Go."
Maybe the initiatives from Clojure Commons & Clojurists Together need more visibility for the newcomers to Clojure?