News for hackers. Stuff that matters.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by s_Hogg on Sunday July 14, 2019 @09:53AM (#20433368)
Why is HN this interested in Lisp anyway? Not saying it's a good or bad language, just don't quite get why it receives as much attention as it does.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by dreamcompiler on Sunday July 14, 2019 @09:59AM (#20433404)
What organization hosts HN?

From what computer science construct does that organization's name come from?

Who founded that organization?

How did that person get wealthy enough to start seed funding other companies?

Did that person write not one, but two books on Common Lisp?

Just some points to ponder.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by s_Hogg on Sunday July 14, 2019 @10:02AM (#20433419)
Oh really, that's interesting. Is that sort of info widely known among the HN user base and I'm an ignoramus or is it a case of some of the users of longer standing being vocal about Lisp?
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by nnq on Sunday July 14, 2019 @10:39AM (#20433636)
> Is that sort of info widely known among the HN user base

Paul Graham's essays are widely known among the HN user base, especially the "Beating the Averages" [1] one. Some of those who've read it know a bit more about the deeper history. And others obsessed with the "10x programmer" myth and they randomly stumble upon Lisp as one of the many "magic oils" that are rumored to make one into such a mythical creature.

It's a big circle jerk imho, but there's a lot to be learned for any programmer from modern Lisp-family languages like Clojure or Scheme/Racket. CL is also worth playing with if you want to know how a truly-hyper-flexible language feels like, but it's probably not a good tool to use unless your problem requires you to invent a new programming language but at the same time you have no time/budget/people to actually do it "the academic way" so you need a weird ducktaped-nuclear-power-tool to hack your way at the problem. Guess that's why some folk in quantum computing and computational chemistry and other on-the-edge-fields tend to pick it from time to time, but it gets replaced with other tech after the really hard research problem gets solved and the software gets rewritten to something else for v2.0. I alway re-try playing with it but it never sticks in my head, the [Python + (C++ or Rust or Go)] combo always wins over it.

[1] http://www.paulgraham.com/avg.html

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by badfrog on Sunday July 14, 2019 @11:12AM (#20433836)
> Paul Graham's essays are widely known among the HN user base

I'm not sure that's true anymore. I think there's a much wider variety of people here now than 10 years ago.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by beezle on Sunday July 14, 2019 @11:27AM (#20433920)
Before today I did not know who Paul Graham was, what he had done or the lispy association to HN. Then again, I'm a few thousand miles from the Bay area and not much of one for keeping track of personalities in any field. Though I am of course interested in things 'tech' related for both work and personal reasons. Am I really in the minority of HN?

Any programmer benefits from exposure to language families other than the one that is their daily driver. Even within familiers there can be nuances and differences that are worth at least a passing thought. Probably applies to life in general too.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by zshrdlu on Sunday July 14, 2019 @01:38PM (#20434660)
> ...but it's probably not a good tool to use unless your problem requires you to invent a new programming language

I'm curious why you say this.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by lispm on Sunday July 14, 2019 @10:05AM (#20433435)
Among Lisp users this is known...

Also if one knows a bit about Lisp history, the headline "O'Reilly agreed to publish a book about Common Lisp" triggers some memories, since for a long time O'Reilly actively discouraged people from trying to contact them about publishing Lisp books. ;-)

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by s_Hogg on Sunday July 14, 2019 @10:16AM (#20433496)
That's reasonably hilarious, thanks for the info :)
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by CydeWeys on Sunday July 14, 2019 @10:30AM (#20433585)
Wait, why?
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Jtsummers on Sunday July 14, 2019 @10:33AM (#20433600)
They didn’t sell well. It doesn’t matter how interesting or important a topic is. Eventually a publishing business has to decide on what their limits are for risk/reward. O’Reilly had decided that Lisp books cost too much and brought in too little for them.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by barbecue_sauce on Sunday July 14, 2019 @10:04AM (#20433434)
I would guess that the majority of HN users never even think about the fact that the site is affiliated with Y Combinator and its associated personalities.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by detaro on Sunday July 14, 2019 @10:49AM (#20433699)
Quite likely, but also something users that have been around a long time might not think about. From my understanding, in the early days of HN the link was a lot closer (content-wise, pg participating on the site, ...)
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by s_Hogg on Sunday July 14, 2019 @10:07AM (#20433445)
I'm well aware of the start up incubator link, but you're definitely right otherwise in my case. When you get here it just looks like a nice lil' news site!
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Waterluvian on Sunday July 14, 2019 @10:19AM (#20433513)
No no it's not just you. I get this kind of thing from the HN community now and then too.

I once got chewed out for not knowing who Paul Graham is.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by kazinator on Sunday July 14, 2019 @02:13PM (#20434870)
You'd probably get chewed out on Facebook for not knowing who is Mark Zuckerberg.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Waterluvian on Sunday July 14, 2019 @07:02PM (#20436824)
The concept of needing to know the key figures behind each website you use is detached so far from the reality of being a human in the 21st century.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by kirubakaran on Sunday July 14, 2019 @01:25PM (#20434580)
This might catch you up a little bit :-) https://news.ycombinator.com/item?id=60357
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by andrewflnr on Sunday July 14, 2019 @06:17PM (#20436561)
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by edraferi on Sunday July 14, 2019 @10:34AM (#20433613)
Sorry about that. People should use these kinds of questions as an opportunity to educate, not brag/exclude/shame.

Relevant XKCD: https://www.xkcd.com/1053/

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by heartbreak on Sunday July 14, 2019 @10:37AM (#20433628)
Pretty sure HN itself is written with Lisp.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by harperlee on Sunday July 14, 2019 @10:50AM (#20433704)
A lisp dialect called arc, created by Paul Graham himself: http://arclanguage.com/
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by dreamcompiler on Sunday July 14, 2019 @11:51AM (#20434058)
You're probably not an ignoramus. You're probably just new here. No sin in that.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by sireat on Sunday July 14, 2019 @09:59AM (#20433409)
HN exists because of LISP.

More precisely PG attributed success of Viaweb to LISP (speed of iteration etc)

http://www.paulgraham.com/lisp.html

http://www.paulgraham.com/avg.html

I am pretty sure the key factor was having a small and talented team. It didn't have to be LISP. They could have used another language they were familiar with.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by toyg on Sunday July 14, 2019 @10:21AM (#20433525)
Even if you give LISP a role, one also has to consider that it was a time when the most popular languages (C++, early Java, Perl) were pretty low-level and not at all web-friendly or async-friendly. LISP could bridge that gap because it makes it very easy to build DSLs and "go up" in abstraction with minimal fuss. If you start with Python or Ruby and their popular frameworks, these days, most of that work is already done for you.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by pjc50 on Sunday July 14, 2019 @11:53AM (#20434067)
Perl was extremely web-friendly: large amounts of the early web were written with CGI.pm or even Apache mod_perl.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by ilikehurdles on Sunday July 14, 2019 @10:32AM (#20433599)
Lisp was a lot less web friendly then than it is now, especially compared to those languages.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by mark_l_watson on Sunday July 14, 2019 @11:06AM (#20433797)
When Alexis Ohanian gave a talk at Google in 2013 I asked him afterwards about converting Reddit from Common Lisp to Python. He said the Common Lisp version crashed too often. He even made a funny comment about this when he autographed Without Their Permission for me.

I agree with you, the web apps in CL story is much better now. I am biased, now that I am mostly retired most of my fun side projects are in CL (with Haskell being a close second).

I really don’t care what languages other people choose to use but using CL makes me happy and I enjoy reading about other people doing good things in CL.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by namibj on Sunday July 14, 2019 @03:10PM (#20435277)
Do you know of any good setup for type-aware autocompletion of Haskell? There are some language servers for it, but it's difficult to get them to play nicely in the face of updates and such.

I hope such an editing system could offset the power of AST macros due to the possible ease of discovery.

Macros unfortunately require a very skilled developer team to not cause mayhem, taken to the extreme in Go not offering any fancy typing or macros.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by hajile on Sunday July 14, 2019 @05:14PM (#20436088)
I doubt crashing had anything to do with lisp -- the site crashes hard at least once every week.

It was all about logistics. YC had two competing companies. They pushed them together. The lisp team could get up to speed on python faster than the python team could on common lisp.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by toyg on Sunday July 14, 2019 @11:00AM (#20433758)
In primitives, yes; but that's not the point with Lisp, whereas it is for those alternatives.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by mepian on Sunday July 14, 2019 @10:28AM (#20433571)
Python already existed at that time for 4 years, at least.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by CydeWeys on Sunday July 14, 2019 @10:34AM (#20433611)
New languages are coming out all the time. For every one like Python that proves to have serious staying power, there are dozens of others that slowly stagnate. It doesn't typically make sense to bet your business on a new unproven language; you want to use something that's already been around for awhile, clearly has staying power, and has a decent community built up around it. Lisp has fit that bill for decades now. At the time of Viaweb's founding, Python was not there yet. The closest thing that was would've been Perl.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by toyg on Sunday July 14, 2019 @10:58AM (#20433747)
Python didn't even have lambda/map/filter/reduce until '94.

Lisp was already Lisp.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by dreamcompiler on Sunday July 14, 2019 @12:17PM (#20434226)
Python's lexical closures are still crippled even today, no?
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by TJSomething on Sunday July 14, 2019 @12:26PM (#20434289)
Since Python 3 added the nonlocal keyword, they seem to be fine, although I haven't examined them too closely.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by dreamcompiler on Sunday July 14, 2019 @12:14PM (#20434209)
That's not what pg has said. He said lexical closures were critical to Viaweb's success, and no popular language offered them except Javascript, which was decidedly not a server language in those days.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by ken on Sunday July 14, 2019 @12:13PM (#20434201)
I don't think "HN exists because of LISP" is the reason that Lisp posts are popular on HN today.

Viaweb also used GNU's compiler, ran on FreeBSD, and stored all data in flat files -- but those other choices aren't nearly as popular here (or in general practice) today.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by tosh on Sunday July 14, 2019 @10:04AM (#20433428)
I was wondering the same thing. IIRC I found hn without having a clue about either Lisp nor about Startups or YCombinator.

Over time I noticed that posts about Lisp were quite common and decided to read up on it thinking there must be something to it if people bring it up again and again. Has been a gratifying journey so far.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by s_Hogg on Sunday July 14, 2019 @10:06AM (#20433442)
Yeah I got here without having anything to do with Lisp at all either.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by SquishyPanda23 on Sunday July 14, 2019 @11:11AM (#20433828)
Independently of the connection between PG and Lisp, many engineers are interested in Lisp because it's one of the simplest programming languages that is closely connected to the Lambda calculus.

E.g. https://crypto.stanford.edu/~blynn/lambda/lisp.html

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by edraferi on Sunday July 14, 2019 @10:31AM (#20433591)
Because Paul Graham, who founded Y Combinator and by extension Hacker News, loves Lisp. He used it as the primary language at Viaweb (basically late 90s Shopify) and viewed the language as a key enabled of their success.

Paul’s blog posts on the subject are useful background: http://paulgraham.com/lisp.html

You should probably start with this one: http://paulgraham.com/avg.html

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by mtreis86 on Sunday July 14, 2019 @10:09AM (#20433458)
Lisps are hackers' languages - programming languages made for writing programming languages.

The following applies to Common Lisp at least, if not others.

It is homoiconic and most implementations are written in Lisp.

It is very open, in that you can inspect existing structures from the REPL.

It has a long history and was the language where many common software paradigms were developed.

It comes with powerful builtin tools like a debugger with restarts where you can make changes to the system live.

The core language is very small but doesn't constrain what can be done with it.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Sunday July 14, 2019 @10:04AM (#20433429)
Because it can easily solve or altogether eschew a lot of the issues that object-oriented JavaScript developers are struggling with and that's barely scraping the tip of the iceberg of problems which Lisp doesn't suffer from.

Alas one of the problems Lisp does quite acutely suffer from is that SBCL has become a defacto standard and its support for anything that isn't GNU/Linux (like Solaris / illumos) is dismal.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by kazinator on Monday July 15, 2019 @05:16PM (#20445362)
SBCL is not alone in neglecting Solaris. For instance, the GNU Debugger is not usable on Solaris any more. And it won't even read core files post-mortem. There is an open bug for this, unsolved.

My TXR runs on Solaris (Intel x86, note). I roll a build for Solaris 10 for every release.

TXR Lisp isn't an implementation of Common Lisp, however.

I build on Solaris because by doing so, I can tick off a little mental checkbox: "[ ] Runs on at least one OS that has Bell Labs Unix DNA".

It's only x86 because I don't have a port of jmp.S for SPARC. A quick an dirty port could be done using setjmp/lonjmp, without delimited continuations. (Or maybe even with?)

I've had to debug a few things in the past that showed up only on Solaris. For that it was worth it to have that Solaris port; but the debugging was difficult without GDB. For instance, most recently, a GC-related bug (potentially affecting all platforms) only reproduced, by chance, on Solaris.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Tuesday July 16, 2019 @11:51AM (#20451196)
I might be able to help you with jmp.S since I know SPARC assembler.

By doing builds on Solaris, you are ensuring your code remains clean and honest because Solaris and illumos are reference implementations of just about any open standard imaginable. If it works there, it's highly probable that the code is standards compliant.

For debugging, you can use dbx, which comes included with Sun Studio, which is a gratis download. If you compile with GCC, you'll have to use gdb. At least I couldn't figure out what Sun engineers did to their version of GCC to make it emit DWARF 2 debugging format.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by kazinator on Tuesday July 16, 2019 @01:57PM (#20452347)
Knowing assembler isn't so much a problem; I wrote the PPC and ARM variants in there without being versed in ARM or PPC assembler. I just don't understand the SPARC register windows well enough to be confident it would work.

Originally, I used setjmp and longjmp. The motivating reason jmp.S exists at all is that at one point I added delimited continuation support to the language. Delimited continuations are captured by copying segments of the stack into heap objects. Continuations are revived by copying back to the stack; but at a different location: the current stack top. Here is where setjmp/longmp became inadequate on Glibc/Linux systems. Glibc's setjmp applies an XOR mask to the pointers stored in jmp_buf, using a secret word (that is different with each process invocation). This is to make certain exploits difficult or impossible. But when we revive a continuation, we need to find inner pointers (from the stack back to itself) and fix them up, including the pointers in a jmp_buf. If these are masked by an XOR, that's a problem.

For any unsupported platform, the thing to do would be to try to just target the C library setjmp and longjmp instead of adding code to jmp.S.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by mepian on Sunday July 14, 2019 @10:22AM (#20433536)
SBCL is open source, so you are free to improve the support for Solaris.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by mark_l_watson on Sunday July 14, 2019 @11:09AM (#20433814)
Also, the SBCL maintainers can be hired for custom help or support - one of my customers did this, with good results.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Sunday July 14, 2019 @04:01PM (#20435627)
I'm a private person in this capacity, so paying someone to reverse the breakage is out of the question. It's an outrage that something like that was allowed to happen in the first place. If this were my software, not only would I fix it immediately, but I would be deeply ashamed of myself for allowing it to happen. We as programmers should start taking responsibility for our actions.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Sunday July 14, 2019 @03:38PM (#20435467)
I would if I knew how; it sure wasn't for lack of my trying to do so, but I don't know enough to pull it off.

By the way expecting that something be fixed by a non-specialist just because something is open source and expecting someone to sink their extremely valuable free time so someone could break and destroy that work again, well, that's not only despicable, it's extremely infuriating.

All the more infuriating as SBCL wouldn't exist without Solaris, which means someone already broke it at least once and here you come expecting me to not only know what to fix, but invest my life into something where my effort would likely be broken upstream again.

This needs to be taken up by the core SBCL team. Meanwhile, pity the time I used to report bugs which just sit there unhandled.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by rjsw on Sunday July 14, 2019 @06:34PM (#20436671)
If none of the core SBCL team use Solaris then they won't know that SBCL doesn't work on it.

I'm sure that people will suggest things to try if you post details of what you have done to get it to build. Leave out words like "despicable" though.

Your account info states that you want to work with the Solaris successor projects, debugging a complex application is a good way to learn more about an OS.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Monday July 15, 2019 @03:06AM (#20438732)
I've left as much information as I could, but nobody even bothered taking on the bug. The other bug was "fixed" but no information was provided on when it will be rolled into the next release, so that's not useful either, especially since Lisp cannot be built without a working Lisp first, which doesn't work now, so I've no way to test the fix.

Working on debugging C code and assembler is one thing, working on debugging Lisp another: I have to master Lisp first, but without working SBCL that's not possible and I'm not switching to an inferior OS just to master something I can't later on deploy on illumos / Solaris. I'd spend an inordinate amount of my free time for dubious gain, something I can no longer afford, so much so that I've stopped sinking my precious free time into computers. Why does software often fail to gain acceptance, respectively why does it become successful? Availability.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by lispm on Monday July 15, 2019 @04:30AM (#20439041)
> since Lisp cannot be built without a working Lisp first

That depends entirely on the Lisp implementation. Some implementations can do this easily.

SBCL supports using another CL implementation. One compiles SBCL with that other compiler and then in a next step this then can compile SBCL.

SBCL supports building with a few selected other implementations. For example I used recently a version of CLISP in the SBCL compilation process. That's described in the INSTALL documentation. CLISP is usually a bit more portable, since it is written in C and does not use a native code compiler.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Monday July 15, 2019 @12:47PM (#20442593)
SBCL documentation states that it can be built with another Lisp, but that is not true: I've tried with CCL and it failed spectacularly.

I couldn't find a working version of CLISP for Solaris 10 for sparc and i86pc.

Guys, I've built hundreds of packages for Solaris 10 on both sparc and i86pc the number of which can easily compete with the number of packages on "OpenCSW" and I'm telling you that SBCL is so broken on the operating system from which it came that it can no longer be built or run on it without the involvement of the core SBCL team. It needs serious attention.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by rjsw on Monday July 15, 2019 @03:13PM (#20444119)
CLISP should build from source, it seems to be getting built fine by Joyent pkgsrc bulk builds. Their build of SBCL is failing in C code [1], maybe a Solaris expert could fix this.

The usual reason that SBCL stops building is that something has changed in the OS.

[1] http://us-east.manta.joyent.com/pkgsrc/public/reports/upstre...

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Monday July 15, 2019 @05:16PM (#20445359)
But nothing has changed on my build servers which are running Solaris 10, so OS change cannot be the cause; without additional information, that leaves us with one or more breakage(s) caused by someone in the core SBCL team.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by rjsw on Monday July 15, 2019 @06:14PM (#20445788)
Did you look at the build log I posted ?
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Tuesday July 16, 2019 @03:28AM (#20448157)
I sure did: it's due to changing the code but not using the correct macro definitions and compiler options from what I could see (I'm on a mobile telephone, on vacation, so lots of the log is cut off). But you also have to realize that Solaris 10 is much older than illumos and I'm telling you that the build breaks on both.

I actually patched that and got past it, half a year ago. The build broke somewhere else after that and it was in Lisp so I had no idea how to fix it. This breakage is just a simple endianess "pre-flight check". SBCL's problems are much more serious then this: they broke it but good.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by rjsw on Monday July 15, 2019 @03:41AM (#20438871)
There are regular SBCL releases, something that is fixed will appear in a month or less. If you don't have a working SBCL you can bootstrap it using CLISP or cross-compile from a different OS such as FreeBSD.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Monday July 15, 2019 @12:53PM (#20442668)
CLISP doesn't work on Solaris either and I've no FreeBSD nor the spare time to figure out how to get it to work.

The only Lisp which works is CCL but when I tried to build SBCL with it, the build failed spectacularly.

I then went to use CCL but all the getopts examples are for SBCL and since I'm still learning Lisp I couldn't figure out how to make them work on CCL. So I'm busted.

Post scriptum: it's been around six months since I've opened those bug reports for i86pc and sparc and there are still no new releases:

http://www.sbcl.org/platform-table.html

I wouldn't have written what I have about SBCL and dismal support for Solaris if I hadn't tried to build, debug, package and research it and research throughly I did. As a professional engineer, the first thing I did was read all the documentation and all the INSTALL instructions I could find as well as any other documentation and bug reports I could locate using multiple search engines; the official documentation is very poor for such a big and serious project and in my opinion as an engineer, not very professional at all, especially when compared to corporate documentation efforts. This creates an additional hurdle for someone looking to master Lisp and do so using SBCL. Pity the two intense weeks of my spare time; what a waste of my life since I'm none the smarter or more knowledgeable for it.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by lispm on Tuesday July 16, 2019 @02:35AM (#20447937)
> The only Lisp which works is CCL

How about ABCL?

> I wouldn't have written what I have about SBCL and dismal support for Solaris

Unfortunately, a niche language implementation & OS combination.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Tuesday July 16, 2019 @11:56AM (#20451237)
I get an existential crisis when I read "niche implementation" in the context of one of the most important operating systems which changed computing forever and which is a reference implementation for just about any open standard imaginable and that on an IT site full of IT professionals.

Never tried ABCL but will look into it when I get a chance.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by rjsw on Monday July 15, 2019 @03:17PM (#20444159)
That platform table doesn't represent what will build, only which binary packages are on Sourceforge.

I'm running 1.5.4 on NetBSD/amd64 and can build it on i386, sparc, ppc, arm and arm64.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Monday July 15, 2019 @05:08PM (#20445296)
NetBSD also happens to be a completely different operating system and pkgsrc is likely to contain NetBSD-specific patches.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by rjsw on Monday July 15, 2019 @06:14PM (#20445785)
I don't build from pkgsrc.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by rjsw on Sunday July 14, 2019 @11:10AM (#20433824)
SBCL works fine on BSD variants, and the project makes submitting patches easy enough.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by _ph_ on Sunday July 14, 2019 @11:25AM (#20433905)
I have run a server software written in SBCL on Solaris for many years. In which sense is the Solaris support lacking?
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Sunday July 14, 2019 @03:43PM (#20435505)
SBCL goes straight into a debugger on i86pc and on sparc it just core dumps immediately.

It cannot be built from source on either of those platforms.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by _ph_ on Monday July 15, 2019 @03:32AM (#20438834)
Then this is a regression in newer SBCL versions.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Annatar on Monday July 15, 2019 @12:57PM (#20442729)
That's exactly what I've been trying to say all along. It needs serious attention from the core SBCL team.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by sp332 on Sunday July 14, 2019 @10:03AM (#20433425)
Paul Graham was on the team that wrote Viaweb in Lisp. He wrote very highly of it, so HN attracted a lot of Lisp supporters early on.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by lawn on Sunday July 14, 2019 @02:50PM (#20435128)
Lisp is an interesting programming language. Some have strong opinions that it's a good one as well. I personally think it deserves more attention than it gets and the more mainstream languages usually get more attention than they deserve (like Go for example).
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by breck on Sunday July 14, 2019 @10:16AM (#20433499)
A lot of people (notably the creator of YCombinator and HackerNews) are arguably "in love with" Lisp.

I bet circa 1940's you would say the same thing about binary, and your question might be "why is X this interested in binary?"

Just as binary notation is a very simple notation that underlies all of computing, and has completely changed the world once an enthusiastic group of early adopters figured out how to leverage it, so goes Lisp. The details people haven't gotten quite right yet with Lisp, but once those are straightened out, imo, it will finally go mainstream like binary has.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Boulth on Sunday July 14, 2019 @09:57AM (#20433387)
Maybe it's because HN itself is written in a dialect of Lisp.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by s_Hogg on Sunday July 14, 2019 @09:59AM (#20433401)
Do you reckon that's all there is to it?
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by emit_time on Sunday July 14, 2019 @11:44AM (#20434011)
Is the second programming language to have existed, and it is still used for some applications. It has some unique properties, including _code is data_.

It is a functional language, and functional programming is making a comeback as well.

There's a lot to it.

I work at a company that used common lisp all the way down.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Thiez on Sunday July 14, 2019 @11:57AM (#20434106)
Is lisp really more functional than, say, Rust? I've tried it for a while but find Haskell much more pleasant to work with.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by emit_time on Sunday July 14, 2019 @07:46PM (#20437009)
I'm not saying it's more functional than another language, also depends on the dialect of lisp.

In general though, lisp is a functional language.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by ken on Sunday July 14, 2019 @12:37PM (#20434337)
i. From the Jargon File: "The dominant HLL among hackers until the early 1980s, LISP has since shared the throne with C." Even though it's not the dominant HLL today, it's been around for 50 years. There's a lot of area under that curve.

ii. It's properly a family of languages, and they usually have "Lisp" in the name (plus Scheme, and now Clojure -- still a small enough set you can remember them all). The Algol family of languages don't all have "Algol" in the name, and the Simula-style object systems don't all have "Simula" in the name, even though both of those are extremely popular today.

Re:In May 2009 O'Reilly agreed to publish a book about Commo... by cheez on Sunday July 14, 2019 @11:06AM (#20433798)
Lisp the language has "code as data" which other languages are just catching up on. Basically, you can generate code using formal code, not a pre-processor
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by jplayer01 on Sunday July 14, 2019 @10:11AM (#20433467)
I don't feel it gets any more attention than Python, C, C++ or any of the functional languages. What do you have against Lisp?
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by s_Hogg on Sunday July 14, 2019 @10:13AM (#20433481)
As I state in the post containing my question - nothing :) just wondering is all
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by layoutIfNeeded on Sunday July 14, 2019 @01:18PM (#20434541)
Paul Graham the founder of Ycombinator was a Lisper.
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by Der_Einzige on Sunday July 14, 2019 @10:23AM (#20433548)
Lain from the hit anime, "Serial experiments lain" used lisp when she coded
Re:In May 2009 O'Reilly agreed to publish a book about Commo... by klez on Sunday July 14, 2019 @10:43AM (#20433664)
Yeah, except this isn't Lainchan, it's HN.