#lispyGopherClimate #live weekly #technology #podcast every 0UTC Wednesday (Tuesday night in the Americas) since 2022.

https://toobnix.org/w/tFN3aeiUunJrU99yzWhHjq

#archive #RSS https://toobnix.org/feeds/videos.xml?accountId=580185

#climateCrisis #haiku by @kentpitman

I want to tie the climatecrisis to an Alexandrian view of the crisis of, I guess, the hugely popular failure of modern industrial architecture.

The meteoric (good) impact Kents notes on my #NicCLIM #software https://lispy-gopher-show.itch.io/nicclim and #CLIM #GUI useage. #commonLisp #McCLIM

Livechat as always in #lambdaMOO ! Fire your mud client at lambda.moo.mud.org 8888 co guest and @join screwtape .
@kentpitman

I left out a few topics because I was a bit out of sorts. When I mentioned an Alexandrian view of the climate crisis,

consider the abject general failure that is modern architecture. Alexander increasingly pointed out that bad problems were appearing on the premise that later someone would go back and fix them - but was always cheaper to make another new problem than paradoxically rewind time and fix old problems.

I would say the LLM datacentre world is 2020s' bad architecture.

@kentpitman

@mdhughes made a point about the gang of four's java Design Pattern book, where the book has a good and a bad way of reading it: a good way being, here are some careful examples of the authors' own indicative efforts of creating clearly themed powerful and broad-ranging reuseable class structures, and it is a good principle to grow these kinds of things in your own art-

and the bad way, ~ which was "copy and paste literally this text into every different software over and over"

@kentpitman

screwlisp (@[email protected])

Alright I was genuinely confused about something. Please answer / boost about what your relationship to ansi #commonLisp is [ ] I use ANSI common lisp with sly or slime [ ] I use ANSI common lisp without either sly or slime [ ] I do not use ANSI common lisp but intend to start [ ] I plan never to use ANSI common lisp

G+DBN

@screwlisp @kentpitman The other thing is, the actual GoF DP book, is in C++ & Smalltalk. It addressed problems they'd found in those languages. Immediately it got converted to Java, & several of the problems just didn't exist, but Java has its own weird tangled paths you need to do some architecture around, & the first conversions didn't go near those.

Here's their 15-years-later article:
https://www.informit.com/articles/article.aspx?p=1404056
#designPatterns

@screwlisp @mdhughes @kentpitman

Oops. I missed the poll. I intend to muck with both.

Intend. Good intentions. That with which the road to hades beeth bepaved therewith...

@screwlisp @mdhughes @kentpitman And the worst way to use the GoF:

“Hi raganwald, I’d like to start the interview by asking you to name and explain three design patterns.”

Interpreter, Command, State Machine. Use interpreter when—

“Those aren’t the ones we’re looking for. Next!”