ivanb

Funny thing is, it is now viable to vibecode your own bespoke IDE. What I pretty much did.

Most if not all the terrorist-related deaths are attributed to The Troubles that ended in - you guessed that - 1998. It is not possible to attribute the deaths or lack thereof to corporal punishment.

Regardless of what side you take, time is the judge. It does not care about what you consider right or wrong. It will show which societies will prosper and which will go extinct.

It would be nice to refactor some of these. Vas deferens and laryngeal nerve look like easy pickings. Leave me my ear-wiggling. Any last bit of expression matters.

I'm dreading the horror of genetic manipulation it would open. The gene editing craze feels like it is right around the corner.

Btw I meant quasi-mutations of course. So every quasi-mutation conses. Alright.

Big-O is one thing. Big constant factor, heap fragmentation and cache locality are other useful characteristics of data structures.

Balancing trade-off is crucial in software design. It would be nice if the documentation listed the trade-offs of the structures compared to their native implementations. I imagine at least every mutation is consing? There are also larger fixed and slow-growing overheads in various operations.

Besides, one can easily code a skill+script for detecting the problem and suggesting fixes. In my anecdotal experience it cuts down the number of times dumber models walk in circle trying to balance parens.

This is fantastic! Godspeed.

It is not easy to tell because lparallel's documentation website has rotted away just the same as cl-user.net. Does anyone remember this beautiful wiki of CL libraries?

Anyway, it looks like lparallel is nice and has some very useful concurrency primitives, but it doesn't have lightweight scheduling, unlike Go. So no cheap async work with many open sockets, cheap context switching, better cache utilisation, simple language constructs and mental model for async tasks. Besides, Go has M:N scheduler. It has all these async benefits but in addition all the threading benefits. Such things can only be properly done by the implementation.

>Yes, but that would be a CL violation

Let's be brave and deviate from the standard, preferably in a backward-compatible way, to provide the best achievable DX.

The CL committee, however smart it was, could not think through all the nooks and crannies of the system. Let's continue where they left off and progress.

The same way threads are different from goroutines, green threads, JS event loop etc.

Coalton is nice but it requires a wrapper around every form you feed a REPL or around the whole file.

If on the other hand SBCL had a more powerful type system or extension points for a pluggable type system...