Chirp!lisp
https://chirp.cooleysekula.net/tag/lisp/rss
Updates tagged with lisp on Chirp!!galdor: This is a screenshot of a Go project I'm working on. But sure, #Lisp expressions are bad because they have too many parenthesis… And of course you cannot manipulate Go expressions the same way as Paredit.
https://chirp.cooleysekula.net/notice/344321
galdor's status on Tuesday, 08-Aug-2023 11:38:54 UTC<p>This is a screenshot of a Go project I'm working on. But sure, <a href="https://emacs.ch/tags/Lisp" class="mention hashtag" rel="tag">#Lisp</a> expressions are bad because they have too many parenthesis… And of course you cannot manipulate Go expressions the same way as Paredit.</p>2023-08-08T11:38:54+00:00Nicolas Martyanoffmdhughes: @clacke In 100 years, if Humans & computers still exist, there'll still be three languages from our time: COBOL, LISP, and C.Banks will keep running COBOL because it's safer to maintain than replace a thing that processes money.LISP/Scheme (but probably not ARC) because you can reinvent it from the papers in minimal time and mold it into your perfect dialect.C because people are stupid and like to watch the world burn. #cobol #lisp #clang
https://chirp.cooleysekula.net/notice/325217
mdhughes's status on Friday, 06-May-2022 00:05:19 UTC<p><a href="https://libranet.de/profile/clacke" class="u-url mention">@clacke</a> In 100 years, if Humans & computers still exist, there'll still be three languages from our time: COBOL, LISP, and C.</p><p>Banks will keep running COBOL because it's safer to maintain than replace a thing that processes money.</p><p>LISP/Scheme (but probably not ARC) because you can reinvent it from the papers in minimal time and mold it into your perfect dialect.</p><p>C because people are stupid and like to watch the world burn.<br /><a href="https://appdot.net/tags/cobol" class="mention hashtag" rel="tag">#cobol</a> <a href="https://appdot.net/tags/lisp" class="mention hashtag" rel="tag">#lisp</a> <a href="https://appdot.net/tags/clang" class="mention hashtag" rel="tag">#clang</a></p>2022-05-06T00:05:19+00:00Digital Mark λ 📚 🕹 💾 🥃lnxw48a1: after a nuclear war, the remaining people will probably not be able to spin up a modern operating system on their improvised chips. How do you build a simple, reliable, legacy-free OS from scratch? What ideas 💡 and techniques should be passed down to those people? If we think hard enough about this, I think we’ll agree that closed-source systems are basically designed to be almost impossible for people outside the sponsoring organization to reproduce (for an example, consider [ReactOS](https://reactos.org/), which launched as [a project to produce a system compatible with Windows 95](https://reactos.org/wiki/FreeWin95) and [then changed to focus on Windows NT](https://reactos.org/wiki/ReactOS/History), and after more than 25 years, is still not capable of being a daily use system. But we may also determine that most open-source systems are likewise not designed in such a way that reconstruction is viable. The Linux kernel is *huge* these days. Additionally, in my opinion, they’d probably want to use programming languages designed for readability, ease of learning, and error-reduction first (that is, more like #COBOL than #C, more like #Java than #CPlusPlus, more like !Smalltalk and #Lisp / #Scheme than #Perl / #Raku and #JavaScript) and then performance and low-level access. I think it is a mistake to assume that one could start with a modern version of #gcc or #llvm or #msvc … because it is not a given that the software itself and someone who knew how to use it (and update, modify, and adapt it) would still exist.
https://chirp.cooleysekula.net/notice/306551
lnxw48a1's status on Sunday, 05-Dec-2021 20:16:02 UTCafter a nuclear war, the remaining people will probably not be able to spin up a modern operating system on their improvised chips. How do you build a simple, reliable, legacy-free OS from scratch? What ideas 💡 and techniques should be passed down to those people?<br /><br /> If we think hard enough about this, I think we’ll agree that closed-source systems are basically designed to be almost impossible for people outside the sponsoring organization to reproduce (for an example, consider [ReactOS](<a href="https://reactos.org/" title="https://reactos.org/" rel="nofollow" class="attachment">https://reactos.org/</a>), which launched as [a project to produce a system compatible with Windows 95](<a href="https://reactos.org/wiki/FreeWin95" title="https://reactos.org/wiki/FreeWin95" rel="nofollow" class="attachment">https://reactos.org/wiki/FreeWin95</a>) and [then changed to focus on Windows NT](<a href="https://reactos.org/wiki/ReactOS/History" title="https://reactos.org/wiki/ReactOS/History" rel="nofollow" class="attachment">https://reactos.org/wiki/ReactOS/History</a>), and after more than 25 years, is still not capable of being a daily use system. <br /><br /> But we may also determine that most open-source systems are likewise not designed in such a way that reconstruction is viable. The Linux kernel is *huge* these days. <br /><br /> Additionally, in my opinion, they’d probably want to use programming languages designed for readability, ease of learning, and error-reduction first (that is, more like #<span class="tag"><a href="https://nu.federati.net/tag/cobol" rel="tag">COBOL</a></span> than #<span class="tag"><a href="https://nu.federati.net/tag/c" rel="tag">C</a></span>, more like #<span class="tag"><a href="https://nu.federati.net/tag/java" rel="tag">Java</a></span> than #<span class="tag"><a href="https://nu.federati.net/tag/cplusplus" rel="tag">CPlusPlus</a></span>, more like !<a href="https://nu.federati.net/group/241/id" class="h-card u-url p-nickname group" title="Smalltalk, Self, IO, etc (smalltalk)">Smalltalk</a> and #<span class="tag"><a href="https://nu.federati.net/tag/lisp" rel="tag">Lisp</a></span> / #<span class="tag"><a href="https://nu.federati.net/tag/scheme" rel="tag">Scheme</a></span> than #<span class="tag"><a href="https://nu.federati.net/tag/perl" rel="tag">Perl</a></span> / #<span class="tag"><a href="https://nu.federati.net/tag/raku" rel="tag">Raku</a></span> and #<span class="tag"><a href="https://nu.federati.net/tag/javascript" rel="tag">JavaScript</a></span>) and then performance and low-level access.<br /><br /> I think it is a mistake to assume that one could start with a modern version of #<span class="tag"><a href="https://nu.federati.net/tag/gcc" rel="tag">gcc</a></span> or #<span class="tag"><a href="https://nu.federati.net/tag/llvm" rel="tag">llvm</a></span> or #<span class="tag"><a href="https://nu.federati.net/tag/msvc" rel="tag">msvc</a></span> … because it is not a given that the software itself and someone who knew how to use it (and update, modify, and adapt it) would still exist.2021-12-05T20:16:02+00:00LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}lnxw48a1: Judging by the presence of parentheses, I'd say "the Janet language":{https://janet-lang.org/} is either a #Lisp / #Scheme dialect or if not, very Lisp-adjacent ... except it looks to be trying for practical usage, and many Lisp languages seem not to prioritize that.
https://chirp.cooleysekula.net/notice/299964
lnxw48a1's status on Thursday, 21-Jan-2021 03:58:27 UTCJudging by the presence of parentheses, I'd say "the Janet language":{<a href="https://janet-lang.org/" title="https://janet-lang.org/" rel="nofollow" class="attachment">https://janet-lang.org/</a>} is either a #<span class="tag"><a href="https://nu.federati.net/tag/lisp" rel="tag">Lisp</a></span> / #<span class="tag"><a href="https://nu.federati.net/tag/scheme" rel="tag">Scheme</a></span> dialect or if not, very Lisp-adjacent ... except it looks to be trying for practical usage, and many Lisp languages seem not to prioritize that.2021-01-21T03:58:27+00:00LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}lnxw48a1: Always say nice things about #Lisp and #Scheme, lest their devotees rip out your liver and sacrifice it to their deity Parentheticus.
https://chirp.cooleysekula.net/notice/288680
lnxw48a1's status on Wednesday, 05-Feb-2020 18:37:54 UTCAlways say nice things about #<span class="tag"><a href="https://nu.federati.net/tag/lisp" rel="tag">Lisp</a></span> and #<span class="tag"><a href="https://nu.federati.net/tag/scheme" rel="tag">Scheme</a></span>, lest their devotees rip out your liver and sacrifice it to their deity Parentheticus.2020-02-05T18:37:54+00:00LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}lnxw48a1: @jmgresham #Lisp and #Scheme interest me. Also #Haskell. Time and energy / focus are limited, though. Maybe in the future.
https://chirp.cooleysekula.net/notice/288679
lnxw48a1's status on Wednesday, 05-Feb-2020 18:34:30 UTC@<a href="https://gnusocial.no/user/51220" class="h-card u-url p-nickname mention">jmgresham</a> #<span class="tag"><a href="https://nu.federati.net/tag/lisp" rel="tag">Lisp</a></span> and #<span class="tag"><a href="https://nu.federati.net/tag/scheme" rel="tag">Scheme</a></span> interest me. Also #<span class="tag"><a href="https://nu.federati.net/tag/haskell" rel="tag">Haskell.</a></span> Time and energy / focus are limited, though. Maybe in the future.2020-02-05T18:34:30+00:00LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}clacke: > Mal is a Clojure inspired #Lisp interpreter> Mal is implemented in 79 languages (81 different implementations and 102 runtime modes)There's Tcl, Forth, Go, D, Lua, obviously some Lisps including itself, awk, and even GNU Make!python.ctolib.com/mal.html#for…
https://chirp.cooleysekula.net/notice/285383
clacke's status on Monday, 04-Nov-2019 23:32:34 UTC> Mal is a Clojure inspired #<a href="https://libranet.de/search?tag=Lisp" class="tag" rel="tag" title="Lisp">Lisp</a> interpreter<br /><br />> Mal is implemented in 79 languages (81 different implementations and 102 runtime modes)<br /><br />There's Tcl, Forth, Go, D, Lua, obviously some Lisps including itself, awk, and even GNU Make!<br /><br /><a href="https://python.ctolib.com/mal.html#forth">python.ctolib.com/mal.html#for…</a>2019-11-04T23:32:34+00:00Santa Claes 🇸🇪🇭🇰🎅mala: I am going to vacationarily livestream RIGHT NOW! The usual blunderings in #lisp, #guix, #guile, and digital rights gossip, this time from my back garden in San Francisco. Watch at https://codetherapy.space/
https://chirp.cooleysekula.net/notice/284387
mala's status on Friday, 04-Oct-2019 23:31:42 UTC<p>I am going to vacationarily livestream RIGHT NOW! The usual blunderings in <a href="https://mastodon.social/tags/lisp" class="mention hashtag" rel="nofollow">#<span>lisp</span></a>, <a href="https://mastodon.social/tags/guix" class="mention hashtag" rel="nofollow">#<span>guix</span></a>, <a href="https://mastodon.social/tags/guile" class="mention hashtag" rel="nofollow">#<span>guile</span></a>, and digital rights gossip, this time from my back garden in San Francisco. Watch at <a href="https://codetherapy.space/" rel="nofollow"><span class="invisible">https://</span><span>codetherapy.space/</span><span class="invisible"></span></a></p>2019-10-04T23:31:42+00:00Danny O'Btechnomancy: the Autumn Lisp Game Jam is coming up! starting the 10th of October and running to the 20th: https://itch.io/jam/autumn-lisp-game-jam-2019#gamedev #lisp #fennel
https://chirp.cooleysekula.net/notice/284381
technomancy's status on Thursday, 19-Sep-2019 18:57:32 UTC<p>the Autumn Lisp Game Jam is coming up! starting the 10th of October and running to the 20th: <a href="https://itch.io/jam/autumn-lisp-game-jam-2019" rel="nofollow"><span class="invisible">https://</span><span class="ellipsis">itch.io/jam/autumn-lisp-game-j</span><span class="invisible">am-2019</span></a></p><p><a href="https://icosahedron.website/tags/gamedev" class="mention hashtag" rel="nofollow">#<span>gamedev</span></a> <a href="https://icosahedron.website/tags/lisp" class="mention hashtag" rel="nofollow">#<span>lisp</span></a> <a href="https://icosahedron.website/tags/fennel" class="mention hashtag" rel="nofollow">#<span>fennel</span></a></p>2019-09-19T18:57:32+00:00tech? no! man, see...schemers: Thanks for the warm welcome and the follow :)This account will not follow nor follow back. This account will be dedicated (or at least try) to display a broad view of the scheme world at large this includes but is not limited to the following hashtags #lisp #racket #guile #guix #clojure and #ai.Best effort will be put to create new and original toots, that is information that you will not find by following the hashtags mentioned previously.Have a good day!
https://chirp.cooleysekula.net/notice/276533
schemers's status on Thursday, 18-Jul-2019 12:31:01 UTC<p>Thanks for the warm welcome and the follow :)</p><p>This account will not follow nor follow back. </p><p>This account will be dedicated (or at least try) to display a broad view of the scheme world at large this includes but is not limited to the following hashtags <a href="https://mastodon.technology/tags/lisp" class="mention hashtag" rel="nofollow">#<span>lisp</span></a> <a href="https://mastodon.technology/tags/racket" class="mention hashtag" rel="nofollow">#<span>racket</span></a> <a href="https://mastodon.technology/tags/guile" class="mention hashtag" rel="nofollow">#<span>guile</span></a> <a href="https://mastodon.technology/tags/guix" class="mention hashtag" rel="nofollow">#<span>guix</span></a> <a href="https://mastodon.technology/tags/clojure" class="mention hashtag" rel="nofollow">#<span>clojure</span></a> and <a href="https://mastodon.technology/tags/ai" class="mention hashtag" rel="nofollow">#<span>ai</span></a>.</p><p>Best effort will be put to create new and original toots, that is information that you will not find by following the hashtags mentioned previously.</p><p>Have a good day!</p>2019-07-18T12:31:01+00:00schemersemacsomancer: @cwebber I think other than initially looking a bit funny or being unfamiliar to people who learned programming with non-Lispy languages, #Lisp #parentheses have more advantages than disadvantages. I mentioned to Matthew Flatt (re: paren-less Racket langs) that I think the parens could make Racket/Lisp potentially easier for getting #linguistics students into non-trivial programming than other langs, since linguists are used to dealing with #trees and bracket-notation for trees.
https://chirp.cooleysekula.net/notice/275556
emacsomancer's status on Wednesday, 10-Jul-2019 13:19:06 UTC<p><span class="h-card"><a href="https://octodon.social/@cwebber" class="u-url mention" rel="nofollow">@<span>cwebber</span></a></span> I think other than initially looking a bit funny or being unfamiliar to people who learned programming with non-Lispy languages, <a href="https://linuxrocks.online/tags/lisp" class="mention hashtag" rel="nofollow">#<span>Lisp</span></a> <a href="https://linuxrocks.online/tags/parentheses" class="mention hashtag" rel="nofollow">#<span>parentheses</span></a> have more advantages than disadvantages. I mentioned to Matthew Flatt (re: paren-less Racket langs) that I think the parens could make Racket/Lisp potentially easier for getting <a href="https://linuxrocks.online/tags/linguistics" class="mention hashtag" rel="nofollow">#<span>linguistics</span></a> students into non-trivial programming than other langs, since linguists are used to dealing with <a href="https://linuxrocks.online/tags/trees" class="mention hashtag" rel="nofollow">#<span>trees</span></a> and bracket-notation for trees.</p>2019-07-10T13:19:06+00:00B. Slade :gnu: :emacs:librelounge: Interesting in #Lisp? #Guile? #OperatingSystems #GNU or #Linux? Then you should listen to the latest episode of Libre Lounge where all about GNU Guix! https://librelounge.org/episodes/episode-23-guix-with-ludovic-court%C3%A8s.html
https://chirp.cooleysekula.net/notice/273176
librelounge's status on Friday, 21-Jun-2019 17:19:18 UTC<p>Interesting in <a href="https://floss.social/tags/lisp" class="mention hashtag" rel="nofollow">#<span>Lisp</span></a>? <a href="https://floss.social/tags/guile" class="mention hashtag" rel="nofollow">#<span>Guile</span></a>? <a href="https://floss.social/tags/operatingsystems" class="mention hashtag" rel="nofollow">#<span>OperatingSystems</span></a> <a href="https://floss.social/tags/gnu" class="mention hashtag" rel="nofollow">#<span>GNU</span></a> or <a href="https://floss.social/tags/linux" class="mention hashtag" rel="nofollow">#<span>Linux</span></a>? Then you should listen to the latest episode of Libre Lounge where all about GNU Guix! </p><p><a href="https://librelounge.org/episodes/episode-23-guix-with-ludovic-court%C3%A8s.html" rel="nofollow"><span class="invisible">https://</span><span class="ellipsis">librelounge.org/episodes/episo</span><span class="invisible">de-23-guix-with-ludovic-court%C3%A8s.html</span></a></p>2019-06-21T17:19:18+00:00Libre Loungecwebber: tfw you use cond when you could have used if in places where the body clauses are large because it's easier to read but then you feel weird about that #lisp
https://chirp.cooleysekula.net/notice/259427
cwebber's status on Wednesday, 13-Feb-2019 21:07:31 UTC<p>tfw you use cond when you could have used if in places where the body clauses are large because it's easier to read but then you feel weird about that <a href="https://octodon.social/tags/lisp" class="mention hashtag" rel="tag">#<span>lisp</span></a></p>2019-02-13T21:07:31+00:00Christine Lemmer-Webberjackdaniel: Fooling around with ASDF visualisation / introspection in #McCLIM. #lisp
https://chirp.cooleysekula.net/notice/259188
jackdaniel's status on Tuesday, 12-Feb-2019 13:16:46 UTC<p>Fooling around with ASDF visualisation / introspection in <a href="https://mastodon.social/tags/mcclim" class="mention hashtag" rel="nofollow">#<span>McCLIM</span></a>. <a href="https://mastodon.social/tags/lisp" class="mention hashtag" rel="nofollow">#<span>lisp</span></a></p>2019-02-12T13:16:46+00:00Daniel Kochmańskinjoseph1: I am finally convinced to try out the Racket programming language after watching @cwebber 's #FOSDEM 2019 talk.https://fosdem.org/2019/schedule/event/guileracket/I have been looking for a Lispy replacement to #Python for a year now. #Racket is batteries-included like Python. You can also create executable binaries. I'm not looking for efficiency here, since it's just for scripts I run on my desktop.Though I prefer to use Emacs over DrRacket, I can see how it can bring down the barrier to entry significantly. #Lisp
https://chirp.cooleysekula.net/notice/258357
njoseph1's status on Saturday, 09-Feb-2019 05:08:24 UTC<p>I am finally convinced to try out the Racket programming language after watching <span class="h-card"><a href="https://octodon.social/@cwebber" class="u-url mention" rel="nofollow">@<span>cwebber</span></a></span> 's <a href="https://toot.thoughtworks.com/tags/fosdem" class="mention hashtag" rel="nofollow">#<span>FOSDEM</span></a> 2019 talk.</p><p><a href="https://fosdem.org/2019/schedule/event/guileracket/" rel="nofollow"><span class="invisible">https://</span><span class="ellipsis">fosdem.org/2019/schedule/event</span><span class="invisible">/guileracket/</span></a></p><p>I have been looking for a Lispy replacement to <a href="https://toot.thoughtworks.com/tags/python" class="mention hashtag" rel="nofollow">#<span>Python</span></a> for a year now. <a href="https://toot.thoughtworks.com/tags/racket" class="mention hashtag" rel="nofollow">#<span>Racket</span></a> is batteries-included like Python. You can also create executable binaries. <br />I'm not looking for efficiency here, since it's just for scripts I run on my desktop.</p><p>Though I prefer to use Emacs over DrRacket, I can see how it can bring down the barrier to entry significantly. </p><p><a href="https://toot.thoughtworks.com/tags/lisp" class="mention hashtag" rel="nofollow">#<span>Lisp</span></a></p>2019-02-09T05:08:24+00:00Joseph Nuthalapatismj: wicked knotted torus #lisp #hacking #math
https://chirp.cooleysekula.net/notice/258021
smj's status on Saturday, 26-Jan-2019 00:21:35 UTC<p>wicked knotted torus <a href="https://mastodon.sdf.org/tags/lisp" class="mention hashtag" rel="nofollow">#<span>lisp</span></a> <a href="https://mastodon.sdf.org/tags/hacking" class="mention hashtag" rel="nofollow">#<span>hacking</span></a> <a href="https://mastodon.sdf.org/tags/math" class="mention hashtag" rel="nofollow">#<span>math</span></a></p>2019-01-26T00:21:35+00:00SMJ :comet:smj: Gosper documented the entire Stanford demo in #lisp #math #hacking
https://chirp.cooleysekula.net/notice/258023
smj's status on Wednesday, 23-Jan-2019 01:42:15 UTC<p>Gosper documented the entire Stanford demo in <a href="https://mastodon.sdf.org/tags/lisp" class="mention hashtag" rel="nofollow">#<span>lisp</span></a> <a href="https://mastodon.sdf.org/tags/math" class="mention hashtag" rel="nofollow">#<span>math</span></a> <a href="https://mastodon.sdf.org/tags/hacking" class="mention hashtag" rel="nofollow">#<span>hacking</span></a> </p>2019-01-23T01:42:15+00:00SMJ :comet:smj: Restore Distribution Symbolics XL402 Genera 8.3 #lisp #machine #scsi2sd #computing #hacking
https://chirp.cooleysekula.net/notice/258025
smj's status on Friday, 11-Jan-2019 19:38:34 UTC<p>Restore Distribution Symbolics XL402 Genera 8.3 <a href="https://mastodon.sdf.org/tags/lisp" class="mention hashtag" rel="nofollow">#<span>lisp</span></a> <a href="https://mastodon.sdf.org/tags/machine" class="mention hashtag" rel="nofollow">#<span>machine</span></a> <a href="https://mastodon.sdf.org/tags/scsi2sd" class="mention hashtag" rel="nofollow">#<span>scsi2sd</span></a> <a href="https://mastodon.sdf.org/tags/computing" class="mention hashtag" rel="nofollow">#<span>computing</span></a> <a href="https://mastodon.sdf.org/tags/hacking" class="mention hashtag" rel="nofollow">#<span>hacking</span></a> </p>2019-01-11T19:38:34+00:00SMJ :comet:hd: uLisp — #Lisp for the #Arduino, #MicroBit, and #MSP430"uLisp® is a version of the Lisp programming language specifically designed to run on processors with a limited amount of RAM. It currently supports the ATmega-based Arduino boards, SAM/SAMD-based Arduino boards, BBC Micro Bit, and MSP430-based LaunchPad boards. You can use exactly the same uLisp program, irrespective of the platform. …"http://www.ulisp.com/
https://chirp.cooleysekula.net/notice/249005
hd's status on Monday, 28-May-2018 20:09:41 UTC<p>uLisp — <a href="https://functional.cafe/tags/lisp" class="mention hashtag" rel="tag">#<span>Lisp</span></a> for the <a href="https://functional.cafe/tags/arduino" class="mention hashtag" rel="tag">#<span>Arduino</span></a>, <a href="https://functional.cafe/tags/microbit" class="mention hashtag" rel="tag">#<span>MicroBit</span></a>, and <a href="https://functional.cafe/tags/msp430" class="mention hashtag" rel="tag">#<span>MSP430</span></a></p><p>"uLisp® is a version of the Lisp programming language specifically designed to run on processors with a limited amount of RAM. It currently supports the ATmega-based Arduino boards, SAM/SAMD-based Arduino boards, BBC Micro Bit, and MSP430-based LaunchPad boards. You can use exactly the same uLisp program, irrespective of the platform. …"</p><p><a href="http://www.ulisp.com/" rel="nofollow"><span class="invisible">http://www.</span><span>ulisp.com/</span><span class="invisible"></span></a></p>2018-05-28T20:09:41+00:00Holger Durerclacke: > After 10 years we have decided that it is time to make a new release – the first one since 2008, which was McCLIM 0.9.6, St. George's Day. Imbolc is a Gaelic traditional festival marking the beginning of spring held between the winter solstice and the spring equinox.> As Imbolc marks the beginning of spring we hope this release will be one of many in the upcoming future. Woohoo!https://common-lisp.net/project/mcclim/posts/McCLIM-097-Imbolc-release.html /via https://twitter.com/d_christiansen/status/964541368830803968 #lisp
https://chirp.cooleysekula.net/notice/239138
clacke's status on Monday, 19-Mar-2018 06:05:44 UTC<span class="greentext">> After 10 years we have decided that it is time to make a new release – the first one since 2008, which was McCLIM 0.9.6, St. George's Day. Imbolc is a Gaelic traditional festival marking the beginning of spring held between the winter solstice and the spring equinox.</span><br /><br /><span class="greentext">> As Imbolc marks the beginning of spring we hope this release will be one of many in the upcoming future.</span><br /><br /> Woohoo!<br /><br /><a href="https://common-lisp.net/project/mcclim/posts/McCLIM-097-Imbolc-release.html" title="https://common-lisp.net/project/mcclim/posts/McCLIM-097-Imbolc-release.html" rel="nofollow" class="attachment">https://common-lisp.net/project/mcclim/posts/McCLIM-097-Imbolc-release.html</a><br /><br /> /via <a href="https://twitter.com/d_christiansen/status/964541368830803968" title="https://twitter.com/d_christiansen/status/964541368830803968" rel="nofollow" class="attachment">https://twitter.com/d_christiansen/status/964541368830803968</a><br /><br /> #<span class="tag"><a href="https://social.heldscal.la/tag/lisp" rel="tag">lisp</a></span>2018-03-19T06:05:44+00:00Hallå Kittehtuturto: @m455 current release doesn't have let and you have to use setv instead. Good news is that the next release will have let again. https://engineersjourney.wordpress.com/2017/09/17/sneak-peek-of-possible-future/ has a bit of info about it. PR has been merged and next release should have this.#lisp #hy
https://chirp.cooleysekula.net/notice/233324
tuturto's status on Sunday, 04-Feb-2018 04:09:18 UTC<p><span class="h-card"><a href="https://tiny.tilde.website/@m455" class="u-url mention">@<span>m455</span></a></span> current release doesn't have let and you have to use setv instead. Good news is that the next release will have let again. <a href="https://engineersjourney.wordpress.com/2017/09/17/sneak-peek-of-possible-future/" rel="nofollow"><span class="invisible">https://</span><span class="ellipsis">engineersjourney.wordpress.com</span><span class="invisible">/2017/09/17/sneak-peek-of-possible-future/</span></a> has a bit of info about it. PR has been merged and next release should have this.<br /><a href="https://mastodon.social/tags/lisp" class="mention hashtag" rel="tag">#<span>lisp</span></a> <a href="https://mastodon.social/tags/hy" class="mention hashtag" rel="tag">#<span>hy</span></a></p>2018-02-04T04:09:18+00:00Tuukkatuturto: Booted up my virtual machine and started trying to remember how in the earth this thing was supposed to work. At least it still starts up.I'm going to try a bit different approach on making corridors and then branch out to agent based room generation.#lisp #hy #procgen #gamedev
https://chirp.cooleysekula.net/notice/216229
tuturto's status on Thursday, 16-Nov-2017 21:40:21 UTC<p>Booted up my virtual machine and started trying to remember how in the earth this thing was supposed to work. At least it still starts up.</p><p>I'm going to try a bit different approach on making corridors and then branch out to agent based room generation.</p><p><a href="https://mastodon.social/tags/lisp" class="mention hashtag" rel="tag">#<span>lisp</span></a> <a href="https://mastodon.social/tags/hy" class="mention hashtag" rel="tag">#<span>hy</span></a> <a href="https://mastodon.social/tags/procgen" class="mention hashtag" rel="tag">#<span>procgen</span></a> <a href="https://mastodon.social/tags/gamedev" class="mention hashtag" rel="tag">#<span>gamedev</span></a></p>2017-11-16T21:40:21+00:00Tuukkalobsters: PicoLisp port to Linux/Arm64 https://www.mail-archive.com/picolisp@software-lab.de/msg07756.html | https://lobste.rs/s/obd5im #lisp #release
https://chirp.cooleysekula.net/notice/212110
lobsters's status on Tuesday, 31-Oct-2017 10:35:03 UTC<p>PicoLisp port to Linux/Arm64 <a href="https://www.mail-archive.com/picolisp@software-lab.de/msg07756.html" rel="nofollow"><span class="invisible">https://www.</span><span class="ellipsis">mail-archive.com/picolisp@soft</span><span class="invisible">ware-lab.de/msg07756.html</span></a> | <a href="https://lobste.rs/s/obd5im" rel="nofollow"><span class="invisible">https://</span><span>lobste.rs/s/obd5im</span><span class="invisible"></span></a> <a href="https://botsin.space/tags/lisp" class="mention hashtag" rel="tag">#<span>lisp</span></a> <a href="https://botsin.space/tags/release" class="mention hashtag" rel="tag">#<span>release</span></a></p>2017-10-31T10:35:03+00:00Lobstersradiolaria: #Programming #Lisp #Haskell #Perl #Malbolge #Exolang https://mastodon.social/media/EQfT6MEIXOKTCl9o_Ew
https://chirp.cooleysekula.net/notice/175840
radiolaria's status on Thursday, 04-May-2017 07:13:00 UTC<p><a href="https://mastodon.social/tags/programming" class="mention hashtag">#<span>Programming</span></a> <a href="https://mastodon.social/tags/lisp" class="mention hashtag">#<span>Lisp</span></a> <a href="https://mastodon.social/tags/haskell" class="mention hashtag">#<span>Haskell</span></a> <a href="https://mastodon.social/tags/perl" class="mention hashtag">#<span>Perl</span></a> <a href="https://mastodon.social/tags/malbolge" class="mention hashtag">#<span>Malbolge</span></a> <a href="https://mastodon.social/tags/exolang" class="mention hashtag">#<span>Exolang</span></a> <a href="https://mastodon.social/media/EQfT6MEIXOKTCl9o_Ew" rel="nofollow"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/media/EQfT6MEI</span><span class="invisible">XOKTCl9o_Ew</span></a></p>2017-05-04T07:13:00+00:00 Radiolaria Ⓜ️clacke: > The engineers had originally calculated that 7 buffers per chip would be needed, but this made the chip slightly too large too build. Nobel Prize winning physicist Richard Feynman had previously calculated that 5 buffers would be enough, using a differential equation involving the average number of 1 bits in an address. They resubmitted the design of the chip with only 5 buffers, and when they put the machine together, it worked fine.> The CM-1 uses Feynman's algorithm for computing logarithms that he had developed [ . . . ] Feynman also discovered that the CM-1 would compute the Feynman diagrams for quantum chromodynamics (QCD) calculations faster than an expensive special purpose machine developed at Caltech.https://en.wikipedia.org/wiki/Connection_Machine It was a 12-dimensional CPU communications structure, and being built by TMC, obviously it ran #lisp.
https://chirp.cooleysekula.net/notice/152117
clacke's status on Saturday, 25-Feb-2017 11:02:18 UTC<span class="greentext">> The engineers had originally calculated that 7 buffers per chip would be needed, but this made the chip slightly too large too build. Nobel Prize winning physicist Richard Feynman had previously calculated that 5 buffers would be enough, using a differential equation involving the average number of 1 bits in an address. They resubmitted the design of the chip with only 5 buffers, and when they put the machine together, it worked fine.</span><br /><br /><span class="greentext">> The CM-1 uses Feynman's algorithm for computing logarithms that he had developed [ . . . ] Feynman also discovered that the CM-1 would compute the Feynman diagrams for quantum chromodynamics (QCD) calculations faster than an expensive special purpose machine developed at Caltech.</span><br /><br /><a href="https://en.wikipedia.org/wiki/Connection_Machine" title="https://en.wikipedia.org/wiki/Connection_Machine" rel="nofollow" class="attachment">https://en.wikipedia.org/wiki/Connection_Machine</a><br /><br /> It was a 12-dimensional CPU communications structure, and being built by TMC, obviously it ran #<span class="tag"><a href="https://social.heldscal.la/tag/lisp" rel="tag">lisp.</a></span>2017-02-25T11:02:18+00:00Hallå Kittehrichardbaeck: Using #Kawa #Scheme for #Android #Programming: https://github.com/abarbu/android-kawa Something similar for Common #Lisp would be cool.
https://chirp.cooleysekula.net/notice/134745
richardbaeck's status on Thursday, 17-Nov-2016 11:40:53 UTCUsing #<span class="tag"><a href="https://gnusocial.de/tag/kawa" rel="tag">Kawa</a></span> #<span class="tag"><a href="https://gnusocial.de/tag/scheme" rel="tag">Scheme</a></span> for #<span class="tag"><a href="https://gnusocial.de/tag/android" rel="tag">Android</a></span> #<span class="tag"><a href="https://gnusocial.de/tag/programming" rel="tag">Programming</a></span>: <a href="https://github.com/abarbu/android-kawa" title="https://github.com/abarbu/android-kawa" rel="nofollow" class="attachment">https://github.com/abarbu/android-kawa</a> <br /><br /> Something similar for Common #<span class="tag"><a href="https://gnusocial.de/tag/lisp" rel="tag">Lisp</a></span> would be cool.2016-11-17T11:40:53+00:00Richard Paul Bäckclackemovedtoheldscalla: RT @lnxw48 Paul Graham (2001): Why a programming language becomes popular or not. http://url.federati.net/ixI04 #Perl !Python #Lisp #Arc ...
https://chirp.cooleysekula.net/notice/75753
clackemovedtoheldscalla's status on Sunday, 17-Jan-2016 00:09:26 UTCRT @<a href="https://fresh.federati.net/lnxw48" class="h-card mention" title="lnxw48 (Linux Walt)">lnxw48</a> Paul Graham (2001): Why a programming language becomes popular or not. <a href="http://url.federati.net/ixI04" title="http://url.federati.net/ixI04" class="attachment" id="attachment-1234000" rel="nofollow external">http://url.federati.net/ixI04</a> #<span class="tag"><a href="https://quitter.se/tag/perl" rel="tag">Perl</a></span> !Python #<span class="tag"><a href="https://quitter.se/tag/lisp" rel="tag">Lisp</a></span> #<span class="tag"><a href="https://quitter.se/tag/arc" rel="tag">Arc</a></span> ...2016-01-17T00:09:26+00:00Claes Wallin (韋嘉誠)lnxw48: Paul Graham (2001): Why a programming language becomes popular or not. http://url.federati.net/ixI04 #Perl !Python #Lisp #Arc #Java #Pascal #Ada
https://chirp.cooleysekula.net/notice/75754
lnxw48's status on Saturday, 09-Jan-2016 01:47:52 UTCPaul Graham (2001): Why a programming language becomes popular or not. <a href="http://url.federati.net/ixI04" title="http://www.paulgraham.com/popular.html" class="attachment" rel="nofollow external">http://url.federati.net/ixI04</a> #<span class="tag"><a href="https://fresh.federati.net/tag/perl" rel="tag">Perl</a></span> !<a href="http://sn.1w6.org/group/247/id" class="h-card group" title="python (python)">Python</a> #<span class="tag"><a href="https://fresh.federati.net/tag/lisp" rel="tag">Lisp</a></span> #<span class="tag"><a href="https://fresh.federati.net/tag/arc" rel="tag">Arc</a></span> #<span class="tag"><a href="https://fresh.federati.net/tag/java" rel="tag">Java</a></span> #<span class="tag"><a href="https://fresh.federati.net/tag/pascal" rel="tag">Pascal</a></span> #<span class="tag"><a href="https://fresh.federati.net/tag/ada" rel="tag">Ada</a></span>2016-01-09T01:47:52+00:00lnxw48 (Linux Walt)clackemovedtoheldscalla: RT @deavmi @marcus I see. Is #Guix hard to setup. Must I know #lisp :D cause lisp is always mentioned.
https://chirp.cooleysekula.net/notice/73425
clackemovedtoheldscalla's status on Friday, 18-Dec-2015 19:00:12 UTCRT @<a href="http://quitter.se/user/126424" class="h-card mention" title="Tristan B. Kildaire">deavmi</a> @<a href="https://gnusocial.ch/marcus" class="h-card mention" title="marcus">marcus</a> I see. Is #<span class="tag"><a href="http://quitter.se/tag/guix" rel="tag">Guix</a></span> hard to setup. Must I know #<span class="tag"><a href="http://quitter.se/tag/lisp" rel="tag">lisp</a></span> :D cause lisp is always mentioned.2015-12-18T19:00:12+00:00Claes Wallin (韋嘉誠)deavmi: @marcus I see. Is #Guix hard to setup. Must I know #lisp :D cause lisp is always mentioned.
https://chirp.cooleysekula.net/notice/73426
deavmi's status on Wednesday, 16-Dec-2015 12:34:48 UTC@<a href="https://gnusocial.ch/marcus" class="h-card mention" title="marcus">marcus</a> I see. Is #<span class="tag"><a href="http://quitter.se/tag/guix" rel="tag">Guix</a></span> hard to setup. Must I know #<span class="tag"><a href="http://quitter.se/tag/lisp" rel="tag">lisp</a></span> :D cause lisp is always mentioned.2015-12-16T12:34:48+00:00Tristan B. KildairedeavmiTristan B. Kildaire