home.social

#lisp — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lisp, aggregated by home.social.

fetched live
  1. Since the Metaspec (metaspec.dev/) was announced a couple of months ago, there have been many improvements. Thanks to #commonlisp on libera.chat for your suggestions!

    - Added a search box in the header
    - Added a dark/light theme button
    - Added an outline sidebar that shows if there's horizontal space
    - There is an OpenSearch spec to add it as a browser search engine
    - Extra information is now listed in an Addenda section
    - New Texinfo and Info renders added
    - There is a new emacs integration package metaspec.dev/elpa/ for details
    - X3J13 Issues have been integrated into the HTML
    - Better handling of linking of LOOP keywords

    #metaspec #lisp

  2. Since the Metaspec (metaspec.dev/) was announced a couple of months ago, there have been many improvements. Thanks to #commonlisp on libera.chat for your suggestions!

    - Added a search box in the header
    - Added a dark/light theme button
    - Added an outline sidebar that shows if there's horizontal space
    - There is an OpenSearch spec to add it as a browser search engine
    - Extra information is now listed in an Addenda section
    - New Texinfo and Info renders added
    - There is a new emacs integration package metaspec.dev/elpa/ for details
    - X3J13 Issues have been integrated into the HTML
    - Better handling of linking of LOOP keywords

    #metaspec #lisp

  3. RayforceDB – a pure C analytics database with a Lisp-like syntax

    rayforcedb.com/

    #database #lisp

  4. RayforceDB – a pure C analytics database with a Lisp-like syntax

    rayforcedb.com/

    #database #lisp

  5. “In this post, I want to swoon about macros, explain what "homoiconic" actually means, demonstrate their ubiquity in Elisp, depict their beauty on a detour through Hofstadter's strange loops and Escher's prints, and finally show off some tooling (macroexpand, emacs-lisp-macroexpand, macrostep) that enhances both comprehension and appreciation of macros.”

    chiply.dev/post-elisp-macros-a

    #lisp

  6. “In this post, I want to swoon about macros, explain what "homoiconic" actually means, demonstrate their ubiquity in Elisp, depict their beauty on a detour through Hofstadter's strange loops and Escher's prints, and finally show off some tooling (macroexpand, emacs-lisp-macroexpand, macrostep) that enhances both comprehension and appreciation of macros.”

    chiply.dev/post-elisp-macros-a

    #lisp

  7. 🚀🙄 Behold, the hipster's dream: a "modern, hyperhackable" dock for the 3.5 people who use #Wayland and have a #Lisp fetish. 🤓 Just what the world needed, another reason to pretend we're all still living in the 1980s while sipping overpriced, artisanal coffee. ☕👴
    codeberg.org/jjba23/lambdock #hipstertech #retrocomputing #artisanalcoffee #HackerNews #ngated

  8. 🚀🙄 Behold, the hipster's dream: a "modern, hyperhackable" dock for the 3.5 people who use #Wayland and have a #Lisp fetish. 🤓 Just what the world needed, another reason to pretend we're all still living in the 1980s while sipping overpriced, artisanal coffee. ☕👴
    codeberg.org/jjba23/lambdock #hipstertech #retrocomputing #artisanalcoffee #HackerNews #ngated

  9. Show HN: Lambdock – Wayland-native GTK4 dock with a live Lisp REPL

    codeberg.org/jjba23/lambdock

    #lisp

  10. Show HN: Lambdock – Wayland-native GTK4 dock with a live Lisp REPL

    codeberg.org/jjba23/lambdock

    #lisp

  11. Пишу русскоязычный ЯП. Помогите выбрать самый читаемый вариант синтаксиса

    Если честно, я давно планировал написать свой язык. Просто надоело на каждом проекте писать одинаковый бойлерплейт, ловить неожиданные ошибки в рантайме, натыкаться на компоненты аля LoanPreloanInterractNDFL6.2ReportViewComponent - и гадать - что имел ввиду художник... В итоге получился язык "Марка" — штука статически-типозированная, но в которой типы живут во время выполнения, ошибки обрабатываются сами, а из REPL можно сразу дергать запросы и смотреть, что приходит на клиенте и сервере. Как давно мечтал. Но раскидав исходники по знакомым, получил неутешительный фидбэк: читать трудно! Встал дурацкий вопрос: как это должно выглядеть в коде, чтобы было удобно? Я набросал 4 варианта синтаксиса — от LISP-стиля до почти Python - нотации. У каждого есть плюсы и минусы, и я уже неделю не могу выбрать. Т.к. язык русскоязычный, все варинаты сделаны так, чтобы в процессе кодинга не пришлось переключать раскадку. Для некоторых действиет правило: - `фун(эл1 эл2)` символ без пробела перед скобкой - значит вызов функции - `(эл1 эл2)` нет символа без пробел перед скобкой - значит список Поэтому хочу обратиться за помощью к вам: какой вариант был бы реально удобен в ежедневной работе? Не теоретически, а когда надо быстро накидать фичу и не думать о запятых. Какой вариант Вам читать и писать было бы удобнее?

    habr.com/ru/articles/1070114/

    #языки_программирования #lisp #функциональное_программирование #синтаксис #fullstack #backend #frontend #статическая_типизация #typescript #python

  12. Emacs lost the text war and won another one. The default buffer is a notepad, so history framed it as Vim's rival, but the actual architecture is a cross-OS Lisp runtime with a shared event bus where every module talks to every other. Vim stayed in the buffer. Emacs kept expanding until it became an interface to the operating system. The real competitor was never another tool. It was the browser - tabs, applications, a portable virtual machine, everything under one window.

    #emacs #lisp #tools

  13. Emacs lost the text war and won another one. The default buffer is a notepad, so history framed it as Vim's rival, but the actual architecture is a cross-OS Lisp runtime with a shared event bus where every module talks to every other. Vim stayed in the buffer. Emacs kept expanding until it became an interface to the operating system. The real competitor was never another tool. It was the browser - tabs, applications, a portable virtual machine, everything under one window.

    #emacs #lisp #tools

  14. @aud Assembler for (a) speed and (b) gatekeeping. Not Prolog and definitely not APL because APL is simply insane. Possibly with a side project purporting to write it in Lisp just to draw in all the posers and weirdos and those who weirdly pose as weirdos.
    #assembler #prolog #apl #lisp

  15. As feared, there's something afoot with nested clipping using the stencil buffer. But we now have kittens (images).

    #McCLIM #SDL #CommonLisp #OpenGL #Lisp

  16. As feared, there's something afoot with nested clipping using the stencil buffer. But we now have kittens (images).

    #McCLIM #SDL #CommonLisp #OpenGL #Lisp

  17. The (German-language) book "LISP - Anwendungsgebiete, Grundbegriffe, Geschichte" (LISP - Applications, Fundamentals, History)

    doi.org/10.1515/9783112563724

    is an unusual compilation of pre-1980 LISP dialects.

  18. The (German-language) book "LISP - Anwendungsgebiete, Grundbegriffe, Geschichte" (LISP - Applications, Fundamentals, History)

    doi.org/10.1515/9783112563724

    is an unusual compilation of pre-1980 LISP dialects.

    #Lisp #RetroComputing #RetroProgramming

  19. There are still things that aren't working, like textures for patterns or complex clipping regions but, this has been illuminating where my opengl-fixed-function-medium isn't quite as reusable as I want it nicely.

    #CommonLisp #Lisp

  20. There are still things that aren't working, like textures for patterns or complex clipping regions but, this has been illuminating where my opengl-fixed-function-medium isn't quite as reusable as I want it nicely.

    #CommonLisp #Lisp