3 ms·
We use CL for many things and it’s definitely a big average beater for us: our clients and competitors (we have no competitors, not even small ones with less th
by anonzzzies 2y ago
We use CL for many things and it’s definitely a big average beater for us: our clients and competitors (we have no competitors, not even small ones with less than 50 devs) think we are massive by how much we churn out. We are a tiny team beating the averages.
- corinroyal 2y agoThis is great to hear! What does your team use Lisp for?
- anonzzzies 2y agoWe make software for streaming/realtime data analysis; our clients are, by first mover/network, mostly banks. We have been building for 20 years next to our ‘consultancy’ (no one else gets a peek; we are not investors like PG so I rather have the competitors slowly bleed Java and Python). We are not 100% cl yet (we started out with c# and Java), but all things that change a lot are.
- deleted 2y ago[deleted]
- miclill 2y agoIs there something in CL as opposed to a Scheme-impl that you would miss or would Scheme give you the same edge in your opinion?
- anonzzzies 2y agoWell, CL is very mature, with sbcl, abcl, ecl, clasp, clisp, lispworks, allegro etc all with different pros and cons, editors and libraries, besides the elegance of scheme, I would have little clue why one would use anything else.
- ducktective 2y agoSince you are focusing on CL, what editor or tools do you and your developers use? How do you onboard new devs for lisp roles?
- agumonkey 2y agoHow long have your shop been using CL ? I understand the value of mainstream languages at the group level (ability to distribute work through simple layers), but my brain doesn't like this way of working. I used to churn a lot on my own and I miss some of that (the speed and the ability to find creative / novel ways to solve problems).
- anonzzzies 2y agoWe started with c# decades ago, but lisp (and prolog by the way) kept nagging, so about 8-9 years ago I started getting my senior devs in workshops ; after about 6 months some of them asked wtf we are doing with that c# stuff?! While that is unfair, the debugging experience, stability, flexibility etc are more painful for my taste. Also, the biggest complaint by many; I have not found any cases where packages we were missing in lisp but are there in nupkg or npm actually sped up any work in the long run. Our work is very regulated (so we check, read and fork the stuff we use to make sure nothing bad lands in prod) and our integrations almost never have integration packages available and if they have them, they are out of date or very badly done because everyone just does it from scratch to make sure. Maybe we are weird and that is fine, but, if there is one thing; we iterate faster than our competitors.
- agumonkey 2y ago> While that is unfair, the debugging experience, stability, flexibility etc are more painful for my taste. You mean c# debugging and stability are bad relative to your own debugging workflow (I can imagine how CL makes things way faster) ? > lisp (and prolog by the way) Talk about low odds, I don't know how many shops use both but that seems like a rare gem. btw you use swipl as your prolog implem ? Do you do conferences discussing some of your work ? I'd be very interesting in following that :)