kscarlet

10 ms·

1.
by kscarlet 18d ago
Thanks! Kudos for the great work!
2.
by kscarlet 18d ago
On second thought, some skepticism on performance comparison: 1. do both systems access everything from memory? 2. do both systems have the same kind of indices? 3. do either system tradeoff scan performance for faster/acceptably fast
3.
by kscarlet 18d ago
Cool language! I thought dplyr and datalog are both local optima (forget about the three-letter abomination) but I now declare this language the global optimum of query language. > In contrast, Prela can be implemented extremely close to
4.
The Story of Mac: A Just-So Story(gigamonkeys.com)
30 points by kscarlet 1mo ago|6 comments
5.
by kscarlet 2mo ago
So does the community of every other dialect (Common Lisp, at least). Write a function if you don't have to write a macro, and maybe declaim the function to be inlined. The "Lisp Curse" is a ridiculous and tired myth that can
6.
by kscarlet 2mo ago
VSCode: https://github.com/kchanqvq/olive
7.
by kscarlet 2mo ago
PSA: VSCode users deserve to use the OLIVE plugin ( https://github.com/kchanqvq/olive ).
8.
by kscarlet 3mo ago
Honestly I think the author misunderstood and misused P != NP. They should have said something like "collusion is NP-hard". P = NP doesn't imply NP-hard problem is efficiently solvable in practice, but the author assumes so.
9.
Markets are competitive if and only if P != NP(arxiv.org)
231 points by kscarlet 3mo ago|164 comments
10.
by kscarlet 3mo ago
These mean nothing. The C/C++ implementations use SIMD intrinsic while Lisp doesn't (it should have used sb-simd).
11.
by kscarlet 4mo ago
That's what the author means. She know what she's talking about.
12.
by kscarlet 4mo ago
> A small but illustrative example: given a live running clisp program, I can click on a UI element to inspect both the live object and the underlying code in the IDE. I can even copy and paste UI elements! I agree GUI is awkward in Emac
13.
by kscarlet 4mo ago
Can you tell a bit more about what is missing from Emacs SLIME when compared to LispWorks?
14.
by kscarlet 4mo ago
I don't see any comments on Kernel in the post. I didn't waste my time reading the book, but the post criticizes unhygiene F-expr, which is known to be awful and is exactly what Kernel aims to solve and supersede (via hygiene
15.
by kscarlet 4mo ago
Not directly. Every "extensions" listed above cannot be implemented as user libraries, that's why these back and forth process between implementation extensions and portability user libraries need to happen to reach a de-fact
16.
by kscarlet 4mo ago
I think the Common Lisp ecosystem sets a good example of how a dozen of implementations move ahead together. Implementations experiment with extensions, the really useful ones get implemented multiple times, and some portability library eme
17.
by kscarlet 4mo ago
(defparameter *a* '(1 2 3)) (setf (car *a*) 3) And this is undefined behavior because it mutates literal constant. I stopped reading further. The CL column is so bad.
18.
by kscarlet 4mo ago
"Lisp Curse" is really a myth, or at least, it completely fails to apply to the Common Lisp community. https://applied-langua.ge/posts/lisp-curse-redemption-arc.ht...
19.
by kscarlet 8mo ago
Why? Many Lisp systems and Common Lisp in particular have great hot reloading capability, from redefining functions to UPDATE-INSTANCE-FOR-REDEFINED-CLASS to update the states.
20.
by kscarlet 8mo ago
Very nice. p.s. (I hate to point this out), there seems to be a name collision with https://lisperator.net/slip/
21.
by kscarlet 9mo ago
> As to the actual difference between JIT vs. AOT... it may just come down to accounting. That is, on whether you can always exclude the compilation time/cost from the overall program execution time/cost or not. If so, you&#x27
22.
by kscarlet 9mo ago
They generate native machine code.
23.
by kscarlet 9mo ago
In that sense almost every compiled Lisp/Scheme implementation, GHC, etc. or any other interactive programming system, count as JIT. But virtually nobody in those circles refer to such implementations as JIT. Instead, people says &quot
24.
by kscarlet 9mo ago
It seems that JIT is overloaded with at least 2 meaning. The canonical definition of JIT is "compilation during execution of a program". Usually, a program is being interpreted first, then switches to compiled code in the middle
25.
by kscarlet 9mo ago
I guess this case is workable similar to struct redefintion. There can be a condition and a CONTINUE restart, which makes instances of the removed constructor obsolete.
26.
by kscarlet 9mo ago
I don't find any good idea in [1]. > 1. The function and variable namespaces have been collapsed into a single namespace. Lisp-N, package system and homoiconic macro is a local optimum (IMO practically much better than Scheme, but I
27.
by kscarlet 9mo ago
wookie is built on cl-async, so my hope is that it's more tractable to write proper async SSE handler. But I haven't looked at whether it's possible to keep open connection asyncly.
28.
by kscarlet 9mo ago
> Each SSE connection blocks one worker for its entire duration. Have you tried wookie? Such extreme case of blocking the event loop... negates any benefit of async processing.
29.
by kscarlet 9mo ago
Well written in general. However: > C++ has method override but it's not the same: you cannot change the behavior of how addition works on two 64-bit integers (such as treating them both as fixed-point numbers). Wouldn't you j
30.
by kscarlet 9mo ago
I find it funny that what you said summarize the publishing process in academia very well. Only except that it's much, much worse.

More ›