Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
vindarel
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
151.
▲
by
vindarel
2y ago
Those are 2 lisp tools not unlike Ansible: * [Consfigurator]( https://spwhitton.name/tech/code/consfigurator/ ) - Lisp declarative configuration management system. You can use it to configure hosts as root, de
152.
▲
by
vindarel
2y ago
Last time I played with Elixir (I'll assume it's similar enough to Erlang), I found the REPL / interactive experience not as rich as CL's (which I must say, reassured my beliefs), even though the command-line tools are g
153.
▲
by
vindarel
2y ago
The plugin in Pulsar (Atom) is pretty good: https://lispcookbook.github.io/cl-cookbook/editor-support.ht... (Sublime, Vim, Jupyter notebooks, VSCode (OKish), Eclipse (simple)…)
154.
▲
by
vindarel
2y ago
Fresh news from 2 weeks ago for CCL: > I recently decided to leave my current full-time job, and I’ll be working on CCL again. […] I’ll be able to work about half-time on an ARM64 port. Please write me privately if you want to talk about
155.
▲
by
vindarel
2y ago
I disagree: Common Lisp has many remaining powerful features AND a large set of them, when a language maybe caught up with one. The interactive debugger is unmatched, image-based development nearly doesn't exist elsewhere, the conditio
156.
▲
by
vindarel
2y ago
Thanks to ITA Software (powering Kayak and Orbitz), Google dedicates resources to open-source Common Lisp development. More specifically, to SBCL: > Doug Katzman talked about his work at Google getting SBCL to work with Unix better. For
157.
▲
by
vindarel
3y ago
Why mention Emacs here? I'm sure you know CL works fine with Vim and other editors like Jupyter notebooks, Atom/Pulsar (very good support), VSCode (still in development), etc. https://lispcookbook.github.io/cl-cook
158.
▲
by
vindarel
3y ago
Resumable exceptions are really cool though: on error get the interactive debugger, go to the bug, recompile the function, come back to the debugger, resume exception, see execution pass. Another CL thing that speeds up development, is more
159.
▲
by
vindarel
3y ago
It's still… not the same. In CL (and specially with SBCL), we get compile time (type) errors and warnings at the blink of an eye, when we compile a single function with a keystroke (typically C-c C-c in Slime). And there's also be
160.
▲
by
vindarel
3y ago
Hello, a single counter-example I hope https://lispcookbook.github.io/cl-cookbook/editor-support.ht... (see more from https://github.com/CodyReichert/awesome-cl?tab=readme-ov-fil... https:/&
161.
▲
by
vindarel
3y ago
and obligatory link for more editors ;) https://lispcookbook.github.io/cl-cookbook/editor-support.ht... (Emacs, Atom/Pulsar (very good support), Jetbrains, Sublime, VSCode (less good support yet), Jupyter kernel,
162.
▲
by
vindarel
3y ago
> treemacs try C-x d aka M-x filer?
163.
▲
by
vindarel
3y ago
> magit Lem has a wip Git mode: see status, stage files/hunks, commit, interactive rebase, basic hg and fossil support. (I added it) It's WIP and undocumented yet (don't worry I'll document when ready, I love document
164.
▲
by
vindarel
3y ago
to answer for readers: yes: Lem has a LSP system, something like projectile (M-x project-find-file, M-x project-switch etc, still inferior but nearly there and easy to extend) images: yes (the SDL2 version). It can display games (M-x tetris
165.
▲
by
vindarel
3y ago
> treemacs Try C-x d in Lem (Alt-x filer) https://lem-project.github.io/usage/usage/#filer---project-e...
166.
▲
by
vindarel
3y ago
You are right :) This file is primarily for the ones who rage quit CL, hoping for greener grass elsewhere (and eventually come back).
167.
▲
by
vindarel
3y ago
Everyone, if you don't have a clue on how's Common Lisp going these days, I suggest: https://lisp-journey.gitlab.io/blog/these-years-in-common-li... ( https://www.reddit.com/r/lisp/co
168.
▲
by
vindarel
3y ago
not true, sorry! And if some languages took features, the combination of them is unique in CL. Image-based REPL interactivity, condition system, interactive debugger, restarts, compile-time computing, compile-time checks, incremental typing
169.
▲
by
vindarel
3y ago
> Every program, every module, is potentially its own DSL it isn't, don't worry. Problem solved ;)
170.
▲
by
vindarel
3y ago
These points scare me: https://gist.github.com/vindarel/15f4021baad4d22d334cb5ce2be... I doubt Julia gives as many image-based tools for the REPL (no conditions and restarts?), no single-file binary? I guess Julia'
171.
▲
by
vindarel
3y ago
yet no other language gives so many tools to the developer… quantum companies would disagree. https://github.com/azzamsa/awesome-lisp-companies/ (BTW: CL isn't Smalltalk which isn't uniquely that anymore
172.
▲
by
vindarel
3y ago
- (i don't get the first point) - unicode: major implementations support it. - oh yeah. UIOP (shipped-in) and libraries fix pathname handling. https://github.com/Shinmera/pathname-utils - https://github
173.
▲
by
vindarel
3y ago
For package management, we have: - Quicklisp, which is pretty handy, since we can install and use a library from the Lisp REPL, without restarting anything. - Qlot, that installs dependencies locally, and allows to pin them (yeah you can&#x
174.
▲
by
vindarel
3y ago
My web app with dozens of dependencies is ±35MB, using SBCL core compression. So that's heavier than Rust, lighter than Deno, maybe in par with Go when the application grows. It starts up in 0.4s, without compression it does in 0.01s.
175.
▲
by
vindarel
3y ago
much, much, much less than Python. CL compilers (looking at SBCL) get you many type checks, at compile time, instantly (you compile the function at point), or you can send computation to compile time yourself, and the OO is different, etc.
176.
▲
by
vindarel
3y ago
sorry but nah, nobody encourages anyone, let alone newcomers, to write macros. You don't even need to. You can chain function calls and get the job done. BTW you get many static type checks at compilation with SBCL, instantly, and see
177.
▲
by
vindarel
3y ago
I doubt it :D https://gist.github.com/vindarel/15f4021baad4d22d334cb5ce2be...
178.
▲
by
vindarel
3y ago
> the code is difficult to organize we can simply do `(defpackage :mypackage (:use :cl))` then `(in-package :mypackage)`. Since they don't have to follow file hierarchy, we are free. That's good for the long term, and general f
179.
▲
by
vindarel
3y ago
see here: https://lispcookbook.github.io/cl-cookbook/data-structures.h...
180.
▲
by
vindarel
3y ago
Examples (for Common Lisp, so not citing Emacs): reddit v1, Google's ITA Software that powers airfare search engines (Kayak, Orbitz…), Postgres' pgloader ( http://pgloader.io/ ), which was re-written from Python to
More ›