"The focus of my research is applying #fp, in particular #chez#scheme, to low-level problems — the type of situations that usually call for #rust or #c"
— highly recommended talk on programming with serialized data from @vollmerm @ #ELSconf
Good talk about #Kandria, the platformer developed in Common #Lisp using #CLOS, as well as #Alloy, the #UI protocol toolkit used to develop it, from Tuesday at #ELSconf
We are 1 month away from the next Lisp Game Jam! Make a dating sim in Emacs Lisp. Or make a Souls-like in Chicken Scheme (aka Chicken Scheme for the Souls.) Or make a kart racer in Fennel. Or make a post-apocalyptic action platformer in Common Lisp. Or make a roguelike in Racket. Or make a farming sim in Guile. Or make a strand type game in Clojure.
In this update on Stringscope, my string listing tool in Interlisp, I summarized my work on implementing the first menu commands Sort, Reset, and Exit:
Wow, Marc Nieper-Wisskirchen's new #scheme macros tutorial looks epic... perhaps the first detailed deep dive since JRM's famous syntax-rules primer for the merely eccentric. #lisp content :chart-with-upwards-trend:
I've been giving #fish a try on a periodic basis every 6 months or so.
The pattern is always the same: I read an amazing article on how fish makes feature X easier/fancier than bash/zsh, I install it again, I spend half a day trying to export my two decades of bash/zsh customizations, and eventually I just give up overwhelmed by the amount of required work.
Fish is a great shell, but I don't know why they decided to go all the way and completely break the compatibility with anything that POSIX has produced over the past four decades.
I won't rewrite all of my shell functions, aliases, if statements, for loops, string concatenations, and/or conditions and environment variables to comply with a shell that is only compliant with itself, sorry. And I don't know why they decided to go the nuclear way and break compatibility so hard where they could have at least guaranteed a back-compatibility layer with (at least) zsh. Reinventing the whole wheel to make it look exactly the way you want, while disregarding compatibility with everything that already exists, is probably the biggest violation of the UNIX philosophy.
@blacklight@DrHyde@tyil The #JargonFile started being passed around and accumulating entries through the 1970s at #Stanford, #MIT, #CarnegieMellon, Bolt Beranek and Newman, and other pre-Internet computing centers. Some terms date back to the late 1950s MIT Tech Model Railroad Club, a very early progenitor of #hacker culture.
This stacking of IC's is reminiscent of 1980's hack by Timo Noko. (Photo here: https://timonoko.github.io/Nokolisp.htm)
.
He stacked together DRAM chips to make tagged memory for a #Lisp.
the one good thing to come out of covid is a whole slew of great courses were shared online. just found Jeremy Siek's lectures from the famous IU #compiler course here:
"#Gauche tracks source code location information and shows it in the stack trace. However, what if the source is generated by macros? In 0.9.12, the macro expander re-attached the original source info to the outermost form of the macro output. However, if a runtime error occurred in constructed code other than the outermost one, stack trace couldn't find the info and had to show '[unknown location]'. It was annoying especially when the code was the result of nested macro expansions, that you didn't get a clue about where the error came from."
“Hackett is a statically typed, pure, lazy, functional programming language in the Racket language ecosystem. Despite significant differences from #lang racket, Hackett shares its S-expression syntax and powerful, hygienic macro system. Unlike Typed Racket, Hackett is not gradually typed—it is designed with typed programs in mind, and it does not have any dynamically-typed counterpart.” - https://lexi-lambda.github.io/hackett/ #haskell#lisp
This is hilarious. A #Google engineer invented #zx to make command line scripting easier with #NodeJS, because at a certain point #shell scripts get too complicated and you need a Real #Programming Language.
This is exactly #Perl’s use case from thirty-six years ago. But the kids want #JavaScript everywhere and would rather it take more work to convert their ascended #Bash scripts to a vastly different syntax.
@swaggboi Everyone loves #Lisp because you can build the entire universe from a small set of parts, but nobody uses it because very few problems require a bespoke universe
@akater@swaggboi The “nobody” is a rough approximation compared to the “everybody” of #JavaScript, #Python, and the rest of the #TIOBE index top 20. I said it about #Lisp (number 29) from the perspective of its low-rated neighbor #Perl (number 25). Please don’t take it personally—we’re both on the same end of the long tail.
I didn’t intend to imply that you can’t or shouldn’t build large #Lisp things any more than #Perl things.
@louis Overall it was a positive experience. I didn't have any issues finding correct #lisp libraries (csv, time handling, CLI args, etc). Biggest 'issue' was going back to a dynamically typed language after I spent a lot time in #rust. Due to my #python experience I love working with dynamic types, but working in rust really boosted my productiviy due to being able to rely on static typing. It was however a very fun thing to rewrite the tool in Common Lisp!