freenode/#lisp - IRC Chatlog
Search
11:36:46
theemacsshibe[m]
I'm gonna go do some stuff, totally not murdering that scientist board that liked Mr Curry, with the time machine I built.
11:38:04
theemacsshibe[m]
(let ((time (- time (years 30))) (loop for person in (getf haskell :design-group) do (murder person) collect (scalp-of person)))
11:53:43
BernhardPosselt
hi, what features should I look into for expanding my horizon? I know the usual web stack, Java, Rust and a bit of Haskell
11:54:21
BernhardPosselt
shouldnt knowing macros or compiler plugins cover most of the power of Lisp already?
11:56:01
Xach
It will be hard to learn new things if you decide in advance what you'll get out of it.
11:56:50
Xach
https://medium.com/@MartinCracauer/a-gentle-introduction-to-compile-time-computing-part-1-d4d96099cea0 is the start of a nice series on a Common Lisp advantage
11:58:04
BernhardPosselt
syntax for me is off putting but I've heard from so many places that you should learn a Lisp language because it's powerful
11:58:36
ecraven
BernhardPosselt: to me, the syntax is one of the strongest points in favour of lisp ;)
11:59:46
Xach
https://www.reddit.com/r/lisp/comments/4oo1cp/common_lisp_for_clojure_programmer/d4eec68/ is a nice post about what it's like to use lisp
12:45:06
ecraven
Xach: ah, there's only two parts so far? This seems like a book I would gladly pay for, but it hasn't been written yet :-/
13:09:27
Colleen
loke: drmeister said 8 hours, 52 minutes ago: The dev branch built - I pushed it to the master branch
13:11:17
drmeister
You may want to try it out - but it needs a special build of boehm and a little more setup than usual.
13:12:26
drmeister
Yes - we have not integrated the boehm build system into clasp - it's a bit of a PITA
13:13:19
drmeister
It's still "experimental" - but it's been working for weeks in several peoples hands.
13:14:19
drmeister
If you have more than ~8 cores the build becomes dominated by other linear processes.
13:16:10
_death
ecraven: I think a very strong point for lisp is that it's not just a language, but also a "living" system.. when developing you simultaneously evolve the lisp language and the lisp process
13:16:56
ecraven
_death: I've been working with SLIME a lot with different Schemes (implementing an r7rs swank), and I've come to found out that while I prefer the *language* Scheme, it just cannot compare in any way to the *system* Common Lisp
13:17:24
ecraven
I haven't found any Scheme that comes even remotely close to debugging, introspection and mutation of running systems in common lisp
13:17:50
ecraven
I am very much a fan of "world" systems, and it seems every Scheme implementation has mostly just given up on that :-/
13:18:38
_death
just today I put back a screencast I made a while ago.. it's a bit long, but may be entertaining to "advanced" lispers.. https://adeht.org/casts/new-project.html
13:18:53
ecraven
loke: years ago, I find it interesting, but not something I would want to actually use the way I use lisp now
13:19:01
loke
ecraven: Smalltalk is nothing like Lisp, but has the same system-based development model. If you try it, and you like the model there, ten that suggests that that is indeed the aspect you like.
13:19:20
ecraven
loke: oh, I like that aspect of smalltalk, I don't like all the visual things it necessitates
13:19:23
loke
ecraven: All of those languages are more or less system-based in the way you described.
13:20:56
ecraven
erlang might be similar, in that you can connect to a running world, modify things, and it keeps working
13:22:31
loke
ecraven: Yes, but it's more limited. You have to rebuild one module at a time. You can't just recompile a function.
13:24:16
ecraven
in a way, it is a bit dismaying to find that *no* other language can compare with CL in this aspect :-/
18:08:08
flip214
_death: but that's only a good idea for a few common sets of slots, and not 30 slots with 50% chance of existance... too many combinations
18:30:44
aeth
For me, I pretty much always use a hash table when I want a hash table. Using a(n) alist/plist for a small number of elements is implementation-specific premature optimization. However, a plist can still be a good choice with lots of elements, if you're iterating over it (e.g. alexandria:doplist)
18:33:03
_death
I never used them, but AMOP claims they're useful in knowledge representation systems