This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
Hi, my name's Marcin. I work as a mlops daily, mostly do python/ai stuff, but my background is in electronics and after touching a few functional programming languages I decided to give this crazy lisp syntax a try... I still don't like it, but I told myself it might a good thing. I didn't like Python syntax at all at the begining as well and today I am forced to use it daily as my income source... 🙂 I decided to do clojure mostly for fun, still going through my first book (clojure for bandt).
Welcome aboard. 🚢 "I decided to give this crazy lisp syntax a try... I still don't like it, but I told myself it might a good thing. I didn't like Python syntax at all at the begining as well...." Good call. Lisp syntax will be the same. Give it a month of actual coding. Following a book may not be immersive enough to draw you in. Make sure you explore the structural editing capabilities. Then the lisp syntax really pays off, letting us edit the same way we think.
The animated guide to paredit http://danmidwood.com/content/2014/11/21/animated-paredit.html > Paredit is great, it brings structural editing to lisps, maintaining the syntactical correctness of your code. I’ve been a fan for a long time, but still was only using a small subset of the functionality available, even afer spending time reading the manual and paper printing out cheat sheets. > > Lately I decided to work deliberately with Paredit and really understand it, and now I mostly do. Here is what I learned.
One time I reached for paredit-convolute-sexp to refactor some clojure.test forms. It was awesome!
One of those things that make no sense whatsoever until one finds oneself in the exact situation it was designed for.
Oh, then systemcrafters guy also did a short demo on structural editing with paredit. https://www.youtube.com/live/FiFMZwQbgOM?t=580&si=MKQc2DbQAJOkINRq
> I decided to give this crazy lisp syntax a try... I still don't like it, but I told myself it might a good thing It is more general and common than one believes. It just shows up in different ways --- think of anything requiring a "balanced" syntax. Open/close braces, open/close XML tags, single/double/triple quoted text, JSON objects. The list goes on... Several features of structural editing work for all of these!
Wow, thanks for the replies, I will check all the links out, right now I'm using Calva in VS Code.
@U069JU5VDV2 sorry, I should have clarified... Calva includes paredit for structural code editing: https://calva.io/paredit/ (Structural editing (and paredit) are not emacs-specific!)