This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-05
Channels
- # adventofcode (22)
- # ai (1)
- # announcements (1)
- # babashka (3)
- # beginners (8)
- # calva (8)
- # cider (17)
- # clojure (3)
- # clojure-europe (4)
- # clojure-norway (13)
- # clojurescript (20)
- # core-logic (1)
- # data-science (3)
- # datahike (6)
- # deps-new (4)
- # events (6)
- # hoplon (4)
- # hyperfiddle (4)
- # lsp (34)
- # overtone (8)
- # podcasts-discuss (2)
- # releases (3)
- # ring (5)
- # vim (10)
- # xtdb (2)
Less than a month to go until AOC2023. Which raises the obvious questions: What language to use? What to focus on? (Static types? Unit testing? Optimize for fast feedback? Learn new editor?)
I'm thinking Elisp this year - not sure if this is wise...
I am considering Janet, since I had a great experience learning it this year and I especially want to see how far I can go with PEGs (parsing expression grammars, built into Janet) and how I can work with a mix of imperative and functional code, maybe learning some C along the way.
I had a good time doing some of last year’s puzzles in APL. There’s a relatively nice setup you can get working with an APL kernel for Jupyter. Some of the puzzles are more trouble than they’re worth though
Clojure & #clerk is the dream combo 🙂 https://www.juxt.pro/blog/using-clerk-for-aoc/
@U06F82LES In the past, I've tried to do a new language each day, so solved a couple using elisp. It was interesting, though a struggle to move back into the mutable mindset. Restartable error conditions were nice though.
I'd like to be more comfortable with writing my own emacs modes. So I figured elisp might help with that
I'm still a Clojure beginner so just plain and simple Clojure for as far as I can reach! Probably dropping into Java since I have work experience with that once I hit the wall
The first year I did AoC I used elisp. Not sure I learned much from it that would help writing a custom emacs mode… I did learn a lot about Common Lisp style loop
. https://github.com/pshapiro4broad/advent2019
@U047L83TC77 same here. The idea to try different languages is a nice one, I could actually try Haskell or rust this year for some of the tasks 🙈
Good luck with that, @U1Z392WMQ 😃
This year I'll try to finish it in clojure 😄 (and probably rust too as well as keeping performance acceptable as an exercise for performant clojure, that should be fun)
Performance or profiling could be an interesting focus. Flame graphs are so hard to read