Earlier quoted context omitted.
We wouldn't have need such barbaric things in a lisp world. :p Personally I think/hope they would have earlier discoveries / more broad usage of the deterministic systems like nix etc, which are built upon functional principles of immutability etc. Maybe the world would be guix/Hurd!
> Personally I think/hope they would have earlier discoveries / more broad usage of the deterministic systems like nix etc, which are built upon functional principles of immutability etc. Yeah, that, uh, doesn't sound like Lisp
Steel Bank Common Lisp version 2.6.7
111–120 of 172 posts
Re: Steel Bank Common Lisp version 2.6.7
#112I'm going pretty deep on Lisp on accident - can anybody give me more context on this?
(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((
In Common Lisp it'd be:
(funcall (funcall (funcall (funcall ; ...
(~> some-data
function-1
function-2
(function-3 _ some-other-data)
; ...
function-n)Re: Steel Bank Common Lisp version 2.6.7
#113Steel Bank Common Lisp is what Hacker News uses. https://news.ycombinator.com/item?id=44099006 I discovered this while doing some research for a post the other day: https://vale.rocks/posts/hacker-news
I recall HN originally using Arc. Is there a history available regarding its development and redevelopment?
I collected the disparate words of Dang here: https://lisp-journey.gitlab.io/blog/hacker-news-now-runs-on-...
Re: Steel Bank Common Lisp version 2.6.7
#114Re: Steel Bank Common Lisp version 2.6.7
#115Earlier quoted context omitted.
But then again, why would I use CL for this when I can use Elixir? I’m not the original commenter but I too can’t find a use case for CL.
Well, why use Elixir if I can use Clojure/Python/Ruby/Go?
In my case, Elixir is the best language, plus the BEAM, for everything that consumes from the network or listens on a socket. It's just too easy.
Re: Steel Bank Common Lisp version 2.6.7
#116checkout lumbda dot com if you are into lisp / scheme
Re: Steel Bank Common Lisp version 2.6.7
#117Earlier quoted context omitted.
Image saving isn't something that's done very often, in practice.
What is done in practice, for daily development use? Building the image in memory from source files at startup?
Yes, that's quite fast. The files are kept in a version control system so you update from that first as well.
The use cases for images would be: delivery of applications to users, or (internally) delivery of some fixed set of underlying code that is used as a substrate for development but that wouldn't normally be changed by developers.
Normally, the developer has an image running all day, and does development and testing in it, but (unless needed for additional testing) doesn't save that image as a new binary that others can run.
Re: Steel Bank Common Lisp version 2.6.7
#118Fun fact I learned from a Func Prog podcast: the name Steel Bank is a play on it's origin as Carnegie-Mellon Common Lisp (Carnegie made his fortune in Steel, while Mellon did so with Banks): https://www.sbcl.org/history.html
There's another wordplay in the name. Namely, that "SB" stands for "Sanely Bootstrappable" - something that the CMU Common Lisp was unable to do
That's more of a backronym.
Re: Steel Bank Common Lisp version 2.6.7
#119Earlier quoted context omitted.
Further confirming my point on why it is the only lisp with some genuine traction out there.
I think you have very little insight to what you're talking about. The modern Lisp landscape is nothing like what it was in the 90s or even 2000s. The amount of practical shit Lispers been quietly building these days is genuinely impressive. Have you ever seen GitHub language stats? Elisp there in the list a few points behind Lua, Elixir, OCaml and Haskell. The amount of Emacs Lisp on GitHub alone should be at least…
[deleted]
Re: Steel Bank Common Lisp version 2.6.7
#120Earlier quoted context omitted.
I think you have very little insight to what you're talking about. The modern Lisp landscape is nothing like what it was in the 90s or even 2000s. The amount of practical shit Lispers been quietly building these days is genuinely impressive. Have you ever seen GitHub language stats? Elisp there in the list a few points behind Lua, Elixir, OCaml and Haskell. The amount of Emacs Lisp on GitHub alone should be at least…
It's mostly hobbyism. My point stands.
> My point stands.
Your point can stand, sit or jump around in a circle - makes no difference. Any ignorant fool can make a hollow point about things they don't fully understand and congratulate themselves in the process.
You can make similar "observation" about Linux on Desktop, mechanical keyboards, 3D printing and Raspberry Pi/Arduino tinkering and call them "hobby business".
You're essentially conflating "niche" with "unserious". By that logic Linux was a hobby OS and Git a hobby VCS - both literally started as one guy's side project, both now run the industry. Lisp is niche, not unserious: Clojure runs Nubank, Walmart, Cisco and Apple; Common Lisp ran ITA/Google Flights; and most of the features in whatever your favorite language is were Lisp ideas first.