File: coon.png (1.78 MB, 1400x935)

1.78 MB PNG

>>108562871
>For some reason I thought ultralisp automatically pulled in things in quicklisp too, so if you distribute on quicklisp then it's also on ultralisp without having to do anything. Is that actually the case?

>The Data
Let's start by setting up some data to play with.

;; lang: lisp
;; get dists
(defparameter ql-dist (ql-dist:find-dist "quicklisp"))
(defparameter ul-dist (ql-dist:find-dist "ultralisp"))
;; get system names
(defparameter ql-names (mapcar #'ql-dist:name (ql:provided-systems ql-dist)))
(defparameter ul-names (mapcar #'ql-dist:name (ql:provided-systems ul-dist))) 

>How many systems exist?

;; lang: lisp
(list
 ;; number of systems in quicklisp
 (length ql-names)
 ;; number of systems in ultralisp
 (length ul-names))

Results:

(6207 6882) 

>How many systems do they have in common?

;; lang: lisp
;; number of systems in common between quicklisp and ultralisp
(length (intersection ql-names ul-names :test #'string=)) 

Results:

3441 (12 bits, #xD71) 

>How many systems are unique to each distribution?

;; lang: lisp
(list
 ;; # of systems only in quicklisp
 (length (set-difference ql-names ul-names :test #'string=))
 ;; # of systems only in ultralisp
 (length (set-difference ul-names ql-names :test #'string=))) 

Results:

(2766 3441) 

They are quite different. I expected there to be much more overlap between quicklisp and ultralisp, but the data revealed otherwise.

To be able to run code blocks using the 4g client by hitting `C-c C-c', make sure you have org-babel-do-load-languages set up.
https://orgmode.org/worg/org-contrib/babel/languages/index.html
Example:

  (org-babel-do-load-languages
   'org-babel-load-languages
   '(
     (duckdb     . t)
     (emacs-lisp . t)
     (gnuplot    . t)
     (jq         . t)
     (julia      . t)
     (lisp       . t)                   ; This is for Common Lisp.
     (perl       . t)
     (restclient . t)
     (shell      . t)
     (sql        . t)
     (sqlite     . t)
     ))

To be able to run Common Lisp code blocks, you also need this.

  ;; slime users use #'slime-eval instead
  (setq org-babel-lisp-eval-fn #'sly-eval)

Sly (or Slime) also has to be running when you want to eval.

>>108655930
Thanks for spending the time to answer my lazy question. I'm surprised there is that much of a difference. Now I wonder if there's anything awesome I'm missing out on that's only in the ultralisp ecosystem.

what do you use it for? it catches my attention but i don't know what i'd use it for :/

I need to pass programming by learning js. i also spend a long time in the terminal learning linux and networking

>>108656789
Regardless of what you want kind of program you want to make, chances are some dialect of Lisp can be used to make it. The main notable exception I can think of is OS development.

>>108657000
How is that a notable exception when multiple OSes have been made in Common Lisp?
Here's one still under active development: https://github.com/froggey/mezzano

>>108656789
>i also spend a long time in the terminal learning linux and networking
Emacs would be pretty handy here, even for mundane things like reading docs (man-pages and Info manuals).

>>108657173
I stand corrected then, though I have a hard time imagining an OS written in a garbage-collected language having acceptable performance.

File: GXc3LcbbwAMJtLP.jpg (130 KB, 1184x862)

130 KB JPG

>>108657234
GC does not preclude performance. In fact it's a well known tradeoff that GC usually gives better performance in throughput at the expense of a larger memory footprint.
Also, from Kent Pitman: "Please don't assume Lisp is only useful for Animation and Graphics, AI, Bioinformatics, B2B and E-Commerce, Data Mining, EDA/Semiconductor applications, Expert Systems, Finance, Intelligent Agents, Knowledge Management, Mechanical CAD, Modeling and Simulation, Natural Language, Optimization, Research, Risk Analysis, Scheduling, Telecom, and Web Authoring just because these are the only things they happened to list."
Common Lisp has had a long history of being used for real software. In 1987 a small group created a set of VSLI design tools complete with GUI that were used to design real processors that were made.

>>108657207
it might help. I see it later, thanks anon! nice little thread