My question would be: How would you improve this error message? I’d second that learning to read stack traces is essential. I don’t think this error message is all that bad. It shows you were to look and what failed. Granted it is far from perfect, but I also don’t know what could be done to improve it. The challenge with stacktraces is that its not always easy to know when to cut them off and omit the rest from the tooling side. I personally get frustrated if anything is cut off at all, since most often some clue is missing when trying to diagnose the causing error. I also know what to ignore ..read more

precondition assertion Those are not meant to be friendly. It’s more like a last resort check in the “it’s better to go up in flames than to proceed” sense. A nicer error message can be achieved when using the (assert ...) form manually: (assert some-condition "some message"). But assertion are meant to be a developer-only tool and can be disabled. If you want to provide an error message under all circumstances, it’s better to use an explicit exception: (when-not some-condition (throw (ex-info "some message" {:some "data"}))) I would love it if it left out the stack trace (— is that wha ..read more

what follows is an error message I get when my precondition assertion fails . I wonder, do y’all have anything in place that gives nicer error messages? . is there something I’m missing here which those-in-the-know utilize? . in this case, eg, I would love it if it left out the stack trace (— is that what it’s called, a ‘stack trace’?) and please nobody make a case for why the error messages as they are are great . they are not great ------ REPL Error while processing --------------------------------------------- (app.dom/evaluate "borf") Encountered error when macroexpanding app.dom/evaluate ..read more

Hi! It is not too late to join the real-world-data study group. See the meeting 1 post for background. This study group is a bit different from the other ones. Participants are assumed to be actively working on a problem and willing to share it. If you wish to join the group, please reach out beforehand ..read more

newApproach: Thinking about a nice, simple blog site as my first project I think most Clojurians who have blogs use a static site generator these days, like Cryogen, so they just write Markdown pages and have the Cryogen program generate HTML, including tag lists, archives, etc. So I’ll assume you’re going to build this purely as an exercise, to run locally on your machine, perhaps with a local database? There’s certainly nothing like Django in the Clojure world – there are some (opinionated) templates that provide a curated starting point with a bunch of selected libraries, but I don’t thi ..read more

Hi all, started learning Clojure end of 2022 but dropped off (sorry), so here is my attempt number 2 after getting back into functional style programming (+ python itertools operator functools), reading a few old papers on the lambda-calculus, and realising I never actually learnt a functional language. Have started the Exercism track, have got hold of one Clojure text, and have both the quickref and cheatsheet at hand. Things I’m most nervous about/Things I think could be my downfall: Expected level of knowledge when building things (Django hath spoiled me) Not being able to get through the ..read more

On April 7th, 2024, the Scicloj visual-tools group had its 23rd meeting. This was the third session on a short series about ggplot2, an R package for grammar-of-graphics data visualization. Summary In the session, we decided to look into ggtrace following @kiramclean’s suggestion. Regretfully, we started reading the Overview rather than the Getting Started. We spent some interesting time with the details, but only with the first section, so we did not reach the parts which are actually about the grammar. This way, we are still missing the big picture regarding ggtrace. Video Clojure visual-too ..read more

The visual tools group will have its 24th meeting on April 26th. Agenda Adam James will discuss badspreadsheet - A Clojure Spreadsheet for building design tools. As time permits, we will also use this opportunity to discuss HTMX (which is used by badspreadsheets), following some recent community interest. Preparing Please read the README, the attached videos, and the explanations. Please read the discussion at the Clojurians Slack. Your comments and questions there will help a lot in preparing the meeting. Joining Please write to @daslu or comment below if you wish to participate. You can ..read more

Hi all, The recording of this event is now available on our YouTube channel: https://youtu.be/qfrEWIGwcPY ..read more

We’re doing an Functional Programming Tutorial Day on April 18. It features tutorials on all major functional languages including several tutorials on Clojure, but also other FP-related topics and a big AMA at the end. More information is here ..read more