News for hackers. Stuff that matters.
Re:Years in Common Lisp: 2022 in review by smcn on Tuesday January 10, 2023 @05:12AM (#34322683)
Tiny world!

CCL is used locally for two reasons 1) error messages are better and 2) it ensures that we're writing portable code. SBCL is used in production because it's much faster and it's constantly being updated, so we get cool things for free. I have been eyeing lispworks but I don't know that it offers much benefit right now. We do plan on mobile apps at some point and that's a conversation we'll have with them.

Production itself is pretty much just a live image, not much different than what you'd have when you're developing. We use slynk to be able to connect to it and play with the data. Can see that here [0].

GC hasn't caused an issue yet. I imagine we will run into issues latter half of this year when we roll out alerts but those are challenges which can be overcome. That might even be a lispworks thing honestly.

0: https://i.imgur.com/8ACxOXG.png

Re:Years in Common Lisp: 2022 in review by galdor on Tuesday January 10, 2023 @05:30AM (#34322798)
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 :)

Re:Years in Common Lisp: 2022 in review by smcn on Tuesday January 10, 2023 @05:38AM (#34322855)
That honestly means the world to me, thank you so much!
Re:Years in Common Lisp: 2022 in review by freilanzer on Tuesday January 10, 2023 @07:29AM (#34323813)
I would read that blog as well. I can't use CL at work but I'm always interested.
Re:Years in Common Lisp: 2022 in review by smcn on Tuesday January 10, 2023 @08:09AM (#34324269)
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.

Re:Years in Common Lisp: 2022 in review by sph on Tuesday January 10, 2023 @08:54AM (#34324843)
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 system.

Looking forward to reading your blog.

Re:Years in Common Lisp: 2022 in review by smcn on Tuesday January 10, 2023 @09:09AM (#34325028)
The hype phase won't disappear unfortunately. Sorry about that.

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!

Re:Years in Common Lisp: 2022 in review by freilanzer on Wednesday January 11, 2023 @05:14AM (#34336903)
Another blog I would read...