lispm

8 ms·

61.
by lispm 2y ago
Thanks, Mikel, for the explanations!
62.
by lispm 2y ago
The MCL kernel was written in C.
63.
by lispm 2y ago
> UI development? The interface builder was written in Dylan and running inside the Dylan runtime. The early use of Dylan (actually its precursor language Ralph) was to develop software on a Mac for an external device, like tablets and h
64.
by lispm 2y ago
> The platform which Dylan was originally designed for, the Newton had no C to begin with. These platforms had no development tools. The firmware and software runtimes were created outside. I would guess that there definitely C was invol
65.
by lispm 2y ago
The teams he assembled and worked with had a crazy impact on programmers, software development, computer platforms and end users. Even when he way not a developer himself, he looked for very bright people in software development to make it
66.
by lispm 2y ago
why not? Having the specs and benchmark results for both CPUs in a table gives a good overview. What advantage would it bring to manually write such comparison tables?
67.
by lispm 2y ago
https://nanoreview.net/en/cpu-compare/apple-m4-vs-amd-ryzen-...
68.
by lispm 2y ago
I would think that's still the case.
69.
by lispm 2y ago
> CL has a very similar degree of dynamism and remains fast. But not the dynamic parts remain "really" fast. Common Lisp introduced very early a lot of features to support optimizing compilers -> some of those reduce "d
70.
by lispm 2y ago
probably there were no such machine-level instructions, but assembler macros https://en.wikipedia.org/wiki/CAR_and_CDR
71.
by lispm 2y ago
"usually" probably means at the time of writing this book. lambda, car and cdr are from the 50s/60s when short names were preferred for various reasons (small memory, input on cards, output on paper, small screens, ...).
72.
by lispm 2y ago
Is Pyret based on reader macros ? I would think it's much easier to use a syntax parser for that.
73.
by lispm 2y ago
Far enough. I had a Symbolics Lisp Machine on a NuBus card, the MacIvory. Actually I still have it, in a Quadra 950.
74.
by lispm 2y ago
It was wild to see the still ongoing overclocking Ghz competition, while suddenly one could use a laptop with good performance, no fans, no noise and while using it mobile.
75.
by lispm 2y ago
I have the M4 iPad with the new OLED. That screen would be great in a Macbook Air.
76.
by lispm 2y ago
The Nubus in the IIx was great.
77.
by lispm 2y ago
> many people in the Lisp world were unhappy because Common Lisp didn't have this or that from whatever they were working on, and because CL was standard they would have to use it. There were many unhappy, but from very different ca
78.
by lispm 2y ago
> Common Lisp is an amalgamation of every lisp they could find, they slammed it all in. Not really. It's mostly a modernized version of Zetalisp. In many cases simpler as that, with some added new stuff (like type declarations).
79.
by lispm 2y ago
> The most popular lisp dialects are linked list based (Common Lisp, scheme, guix I think as well) You may want to check the Common Lisp standard (a dialect, where its development goes back to 1982). https://www.lispworks.com&
80.
by lispm 2y ago
> for a programming language used by academia thirty years ago, rather than in one used by profit-oriented organizations for large data systems or games. I think that's a misconception. Common Lisp was designed as a language for Res
81.
by lispm 2y ago
> Nice or not, pretending that double precision floats and arbitrary precision integers can be stacked as a tower is foolish. There are floats that can't be represented as integers, and integers which can't be represented as fl
82.
by lispm 2y ago
> I know some people have long used "DSL" in this way, especially among LISP fans generally this would be called an "embedded domain specific language". Some languages are relatively flexible to change the syntax. Fo
83.
by lispm 2y ago
> I really feel like you are determined to misinterpret Why post here, when you are not willing to accept feedback from other people? I get that you have trouble learning Lisp, but I have been hearing the same stuff for decades. Nothing
84.
by lispm 2y ago
Pascal, Fortran, C, ... All these languages use prefix notation for function calls. Fortran: min(size(b), size(a)) Lisp: (min (size b) (size a))
85.
by lispm 2y ago
Basically no programming language is an infix-only-notation language. Most programming languages are using mixed notation: prefix, infix and possibly postfix. In most languages function calls are prefix. For a subset of functions there are
86.
by lispm 2y ago
Apple's MCL used the MMU for the stock Motorola 68020+ (M68020 + MMU, 68030/40 with included MMU, ...) processors for an efficient GC: the Ephemeral GC, using a table of changed memory pages, which was maintained by the MMU. This
87.
by lispm 2y ago
> harder to learn than other things "harder" is relative to a reference. Even "hard" is relative. The simple nested arithmetic code you stopped at in SICP is easy for most people working as developers. Maths from 5th
88.
by lispm 2y ago
That's discussed in this paper: CommonLoops: merging Lisp and object-oriented programming https://dl.acm.org/doi/pdf/10.1145/28697.28700 CommonLoops was proposed by Xerox to be the OOP system of Common
89.
by lispm 2y ago
The answer would depend on what you think "message sending" is and why you think Smalltalk does not support "message sending".
90.
by lispm 2y ago
LOOPS (Lisp object-oriented programming systems) is written in Interlisp for the Interlisp-D environment, was a Xerox product and is from around 1981. CLOS (Common Lisp Object System) is a general OOP standard extension for Common Lisp. A s

More ›