← Feed

Posts

• Post #1893969

  Think I managed to rip out all the remaining slop from SBCL's 2.6.2 release. Builds on Linux x86-64 so seems fine for me™. Probably going to use this personal fork for the foreseeable future. Might try to update it to future releases but depends on the complexity and amount of slop. (Stainless) Steel Bank Common Lisp: https://codeberg.org/zyd/sbcl The name is very cute, admit it. #lisp #commonlisp

• Post #1893967

  Lisp propaganda from 1988: "Every time a program change is necessary it means starting the cycle over again." #lisp

• Post #1470405

  Really like these articles' visualizations of transforms, especially the model→view→projection. Other articles do a better job at in-depth explanation (e.g LearnOpenGL chapters) but that's fine since these seem more like notes than anything. https://jsantell.com/3d-projection/ https://jsantell.com/model-view-projection/ #gamedev

• Post #1388249

  https://clojure.org/dev/contributor_agreement#_no_generated_code 👀 Clojure’s code is written and reviewed by humans. Code generated by a large language model or similar technology, such as Anthropic’s Claude, GitHub/Microsoft’s Copilot, OpenAI’s ChatGPT, Facebook/Meta’s Code Llama et al, is not compliant with the covenants and representations of Clojure’s Contributor’s Agreement, and is thus not acceptable as code for Clojure. I'm aware of Hickey's sarcastically titled post "Thank...

• Post #646791

  I asked emacs-devel: Are LLM contributions welcomed in GNU Emacs by the maintainers and contributors? Eli Zaretskii: We are awaiting the decision by the GNU Project on these matters, which will define the policy for all the GNU packages, and in the meantime we don't accept LLM-generated code, as a precaution. For now, Emacs won't accept LLM contributions. However, given this: Obviously, the right thing to do is protect computing freedom: share complete training inputs with every user...