4 ms·
To anyone not already experienced with Lisps, there's varying schools of thought and opinions on what's important and valuable, within Common Lisp (CL), and wit
by neilv 3y ago
To anyone not already experienced with Lisps, there's varying schools of thought and opinions on what's important and valuable, within Common Lisp (CL), and within the broader Lisp family.
For example, although this writer doesn't think macros are important, the Scheme (and especially Racket) branch of Lisp ran with macros, then with various other DSL support that take macros further (like Racket `#lang`). Racket also moved towards a strict definition of phases, and a very nice module system that works with that.
That might horrify some CL people, because it moves further away from the dynamic REPL live manipulation strength of CL, but others of us have found the tradeoffs very practical for our needs.
- ilrwbwrkhv 3y agoHonestly just using Steel Bank Common Lisp is the best choice if you are looking to build high quality software which just works. A lot of my software which earns a $4 million profit per year has SBCL sub systems though that is slowly decreasing as we are moving away from Lisp.
- neilv 3y agoIf you have some great Lisp hackers who are also experienced in industry team software engineering, you step back and let them use whatever they decide is best to use. :)
- valbaca 3y agoI'm curious. May I ask what you're moving toward and what the motivations and reasons were? What was great and not great about building on/with Lisp?
- ilrwbwrkhv 3y agoI am moving towards Go. The greatest benefit of SBCL is that it's got great performance and the REPL jack in allows you to debug any application state. Building CL software is just amazing. So as the company is growing really fast, and I never want to talk to a VC, I need to add those reliability into the system as I can't spend a lot of time training people. That can only be done by having the highest performance to simplest code ratio (since we lose the repl jack in). Go is the clear winner here after trying a bunch of them. It is also easy for people to learn and the amount of tutorials and resources online is great. It is a bit sad, but the Lisp hacker bucket is a really small pool if you want to hire from so at the end of the day I had to compromise. Having said that Go is quite a workhorse and has the simplicity of C so it is actually not that bad.
- medo-bear 3y agoAre you able tontalk about your product and SBCL's role in it?
- neilv 3y agoHow many CL hackers do you need? What about having a core of a few people, and leverage that Lisp productivity potential? If you need a lot more "bulk" work (say, for customer integrations/customizations), is it something that the core people can make easier? Such as with APIs or DSLs, and recipes, so that this other set of programmers doesn't have to all be CL experts? You'll probably have to pay good money for that core of great CL hackers, though. Go programmers are more numerous, and maybe easier to find competent ones at commodity rates. And is the number of CL hackers available on the job market decreasing? ITA found a lot of them, at one point. There are many Scheme/Racket programmers than there are jobs.
- akkad33 3y agoDid you build it on your own? And why are you moving away from Lisp?
- ilrwbwrkhv 3y agoYes I wrote all the first images. I love Lisp and think it is amazing if you approach it in the right way. Now the company is growing at a rate that I need to hire people and build teams. That is where Lisp is a hard bargain. The bucket of people who can write a new system from scratch without falling for the common traps is really small. So that is why we are slowly transitioning away.
- BaculumMeumEst 3y agoAs someone who dabbles in common lisp I would love to know some examples of common traps are in designing a system in cl, since I am probably bound to fall into many :)
- felideon 3y ago> Now the company is growing at a rate that I need to hire people and build teams. And yet you didn’t post on the Who’s Hiring thread. :) Not that I’m looking, nor am I not looking, but sounds like an interesting gig.
- kaveh808 3y agoWhat is the field of your software product?
- patrec 3y agoHygienic macros and a strict phase separation are not distinctive to scheme, many languages have this now, most importantly Rust. And just like Rust macros scheme macros are not really an organic part of the language but some extra edifice bolted on top. Scheme definitely deserves credit for pioneering work here, but the only aspect that's of enduring distinctiveness that I'm aware of is Racket's #lang, which basically gives you a less messy and more powerful version of what you could do in Common Lisp with macros and read-tables. My impression is that hygiene itself (which the scheme community tended to obsess over) is of minor practical benefit, but the fact that you get good error locations (because not using plain lists and symbols makes it easy to carry sufficient contextual information around[^1]) is a major upside. Out of curiosity, are there additional important practical benefits you see, macro-wise, over Common Lisp (that would make up for the gimped repl)? I.e. in addition to better error messages? [^1] I seem to remember being told Allegro Common Lisp does a good job here, but I assume identity still imposes some major limitations.
- justinpombrio 3y agoRust macros are not hygienic. The biggest issue with this, I suspect, is the visibility limitation: due to lack of hygiene a macro can only refer to a public value. Thus some crates will publicly expose a value with a doc string saying "this is supposed to be private please don't abuse it our you'll clobber the invariants this crate otherwise upholds". https://doc.rust-lang.org/reference/macros-by-example.html#hygiene https://doc.rust-lang.org/reference/macros-by-example.html#h...
- DonaldPShimoda 3y ago> Hygienic macros and a strict phase separation are not distinctive to scheme, many languages have this now, most importantly Rust. My understanding is that Rust's macros are only partially hygienic. They fall short of Racket's. To the best of my knowledge, Racket has the most hygienic and expressive macro system of any language today. The people behind it have put a lot of work into it over the past couple of decades, producing more than a few significant papers in the realm of PL research. > My impression is that hygiene itself (which the scheme community tended to obsess over) is of minor practical benefit I assume you've not written many macros that generate identifiers before. I assure you, hygiene is quite important for safely reasoning about your syntax! > are there additional important practical benefits you see, macro-wise, over Common Lisp Racket sports a focus on what they call "language-oriented programming". The gist of this community philosophy is that all significant software really is an API (or a layer of multiple APIs), and by treating these APIs as "languages" we can make them more ergonomic. Expressive macros enable a style of programming where you can make your API look however you want while still implementing it within whatever other language you're using. Pretty much all of my Racket projects end up with at least a few macros, though it's worth pointing out that the community also stresses that things that can be functions should be functions rather than macros.