Earlier quoted context omitted.
Thanks for the info. I'm also using both SBCL and CCL, both to stay portable and because it sometimes help finding issues detected by one and not the other. If you end up blogging about CL (and tech in general) at Feetr, know that there will be at least one interested reader :)
That honestly means the world to me, thank you so much!
Common Lisp: 2022 in review
31–40 of 77 posts
Re: Common Lisp: 2022 in review
#32Disclaimer: not a big Lisp user. Interesting how Lisp code is NOT littered with " if something != null, ...", unlike your average Java project (or even python, but it's less visible), and just works. My understanding is that busines-as-usual handling of nil (empty lists) implicitely confers to Lisp code monadic style which help to avoid tedious checks
Re: Common Lisp: 2022 in review
#33Disclaimer: not a big Lisp user. Interesting how Lisp code is NOT littered with " if something != null, ...", unlike your average Java project (or even python, but it's less visible), and just works. My understanding is that busines-as-usual handling of nil (empty lists) implicitely confers to Lisp code monadic style which help to avoid tedious checks
https://bugs.launchpad.net/sbcl/+bug/2002244
https://sourceforge.net/p/sbcl/sbcl/ci/06f1639e53e99365f48a1...
If you are calling a generic function you can sometimes avoid such checks by introducing methods specialized on the type NULL (which contains only NIL).
Re: Common Lisp: 2022 in review
#34Earlier quoted context omitted.
That honestly means the world to me, thank you so much!
I would read that blog as well. I can't use CL at work but I'm always interested.
It's something that I'd love to do, especially as there aren't many people using it in production, or at least talking about it, and I think that showing people it's a viable language could be important.
It's a shame that we as a community still throw around the Grammarly article as proof of people using it, I wish we had more recent examples.
Re: Common Lisp: 2022 in review
#35Earlier quoted context omitted.
Talking about Common Lisp in the places I worked for in the past has always be met with mockery and disdain. But then again, I have seen this kind of reaction for every non-mainstream language, so it is not really surprising. I'm currently getting back to CL, hoping to do much more with it for 2023. Being able to develop incrementally in SLIME has been a joy. Hopefully I will manage to find the right project idea to…
I was /that guy/ at my last place and I agree that it's not well received. Though once I was writing some lisp to fix a problem we were having and I had a developer beside me and he was blown away by what was happening. I think that the interactivity is something which must be experienced to be fully appreciated. I use it at my current start up and could not imagine using another language. I've become too used to thi…
Re: Common Lisp: 2022 in review
#36Re: Common Lisp: 2022 in review
#37Earlier quoted context omitted.
I would read that blog as well. I can't use CL at work but I'm always interested.
Thank you so much for that! It's something that I'd love to do, especially as there aren't many people using it in production, or at least talking about it, and I think that showing people it's a viable language could be important. It's a shame that we as a community still throw around the Grammarly article as proof of people using it, I wish we had more recent examples.
Also, now that I've decided to go solo-entrepreneur, there is no one that can laugh at me if I decide to use CL for a core system.
Looking forward to reading your blog.
Re: Common Lisp: 2022 in review
#38Re: Common Lisp: 2022 in review
#39Earlier quoted context omitted.
I was /that guy/ at my last place and I agree that it's not well received. Though once I was writing some lisp to fix a problem we were having and I had a developer beside me and he was blown away by what was happening. I think that the interactivity is something which must be experienced to be fully appreciated. I use it at my current start up and could not imagine using another language. I've become too used to thi…
I'm curious, are you able to write full backend services in CL, with http and database interactions, or "just" some domain logic ? If it's the former I'm curious what kind of libraries you are using
We use Postmodern for Postgres interaction. Have no complaints at all. You're able to use s-sql which is SQL statements as s-exps but can drop into just passing it strings if required.
Dexador is how we're doing web scraping (and requests should we need to). Top tier, no complaints. Exactly what you want from it. Plump and lquery are also used for parsing HTML
Jonathan is where I'll fight with most people in the CL community. It's the best JSON library. When I say fight, I mean it, I'll throw hands at anyone recommending cl-json or jsown.
Local-time is something we depend upon a lot. Great for timestamp manipulation.
cl-cron for scheduling. I like it well enough.
I'm also a big fan of Hunchentoot for the web requests. All static pages (currently all addressable webpages) are generated by Spinneret.
There's a few more libraries but they may be more niche or more specific to us.
Re: Common Lisp: 2022 in review
#40Earlier quoted context omitted.
Thank you so much for that! It's something that I'd love to do, especially as there aren't many people using it in production, or at least talking about it, and I think that showing people it's a viable language could be important. It's a shame that we as a community still throw around the Grammarly article as proof of people using it, I wish we had more recent examples.
Same here, I'm interested in the finance angle as well. I've written a few crypto arbitrage bots for fun over the years, and now that I'm deep in the Lisp hype phase, I really want to do it in Common Lisp. I'm already vibrating at the idea of being able to introspect its operation from day 1. Also, now that I've decided to go solo-entrepreneur, there is no one that can laugh at me if I decide to use CL for a core sys…
Especially in finance where most of the effort is geared towards data and data manipulation, it's almost a super power being able to work with live data and live systems. Your development speed is going to 10x.
I wish you all the best on your journey! Can't wait to see what you come up with!