Post AZptrUOULEvD19AQqW by carcosa@emacs.ch
 (DIR) More posts by carcosa@emacs.ch
 (DIR) Post #AZpsauNeN5OUjhIy8W by louis@emacs.ch
       2023-09-16T20:28:14Z
       
       0 likes, 0 repeats
       
       Took a break from #CommonLisp the last few weeks. Just to hear that constant nagging voice at the back of my mind .... "you could have written that Go crap in Common Lisp... why haven't you? ... just do it, for me it's never too late to use me". 🥴​  Pfff... already knee deep in my Slime setup again.
       
 (DIR) Post #AZptrUOULEvD19AQqW by carcosa@emacs.ch
       2023-09-16T20:42:29Z
       
       0 likes, 0 repeats
       
       @louis I really want to do a fun CL project. But I have personal projects blocking me! Not just work and kids!
       
 (DIR) Post #AZqf9de7NQdwlpdMu0 by holgerschurig@emacs.ch
       2023-09-17T05:32:23Z
       
       0 likes, 0 repeats
       
       @louis You might want to swap Lisp with something powerful, like Nim. Not with a language that was designed with a built in handbrake, like Go (Go was intentional designed for beginner or intermediate programmers).In Nim, you even have Macros that can help you define compile-time DSL if you're so inclined.But if you swap anything out for an intentionally too simple thingy, you might end up frustrated with a high probability.
       
 (DIR) Post #AZzRaxhZ5Wpl64CiGG by mousebot@todon.nl
       2023-09-21T11:12:52Z
       
       0 likes, 0 repeats
       
       @louis I guess that means you're doing your large contract in go not CL?
       
 (DIR) Post #AZzSVpHb3t9JUbAlJg by louis@emacs.ch
       2023-09-21T11:23:08Z
       
       0 likes, 0 repeats
       
       @mousebot 👍​ Yes, very unfortunately. There is simply already so much Go code I could reuse and for my day-job and I can literally get the job done while I sleep.I've tried with CL first but it didn't take long until I hit issues with libraries that I could not resolve myself due to heavy macro use and a high degree of hesitation to submit deficient patches to a maintainer.However, I've not given up on Common Lisp at all. My goal still is to reach a level of proficiency where I can do my stuff without relying too much on external libraries.
       
 (DIR) Post #AZzTVWWktV1THGgNUG by mousebot@todon.nl
       2023-09-21T11:34:17Z
       
       0 likes, 0 repeats
       
       @louis ah bummer. yeah it's a pity that its harder to jump in to CL like that, as it also means less people participating, less momentum. what libraries did you struggle with?
       
 (DIR) Post #AZzVtzu5Wc8XFFOUKW by louis@emacs.ch
       2023-09-21T12:01:06Z
       
       0 likes, 0 repeats
       
       @mousebot I don't remember all of them but specifically Postmodern and Closer-mop. Postmodern really took a lot of energy to cope with.I also used jzon (the only sane JSON lib that seamslessly de/serializes to CLOS) and had some issues but the developer is on Discord and was very responsive. However, since jzon also uses Closer-mop I encountered issues with LispWorks that could not be easily resolved.For web I had to resort to hunchentoot because the libs from fukamachi (caveman, ningle etc.) all had issues under high load. And then, I have two external APIs to connect to which run on SOAP 😜​. CL-SOAP didn't work at all with these and so I had the choice to either build my own lib or handle a lot of different XML request/responses with hundreds of fields manually. No, thank you :-).The type-safe json/xml encoding packages in Go to the rescue.