Another #CodeGolf puzzle for #JavaScript #WebDev people:
I have n functions that type one argument of the same type and return a boolean.
The current usage is:
function a(b) {
return c(b) && d(b)
}
I boiled down a to
a = (b) => [c, d].every(fn => fn(x))
I assume, this can be further boiled down via bind/ #PartialApplication/ #Currying
What do you think?
#lispygopherclimate https://archives.anonradio.net/202501220000_screwtape.mp3 #archive
#ClimateCrisis haiku/wildfires by @kentpitman
Electric (guitar) #music by @ksaj, community message from @TheGibson
Arrokoth #McClim Graphical adventure Game creation system #lisp
by five decade #gamedev veteran @mdhughes
#NUD #codegolf / adopting Arrokoth
@baruchel #lisp destructive permutation
#mastobook club - Snow crash
#livechat in #lambdaMOO
telnet lambda.moo.mud.org 8888
co guest
@join screwtape
#NUD #codegolf #programming #gamedev #commonlisp
If you'll forgive the daily throwaway challenges, here's another one. To quote from the link,:
```
'(a (b c) d (e f))
overwrite the b with the f.
```
My solution, featuring the new "apply nconc to register", &
```
(progn ^^ [ >> >> v [ & ^^ [ >> >> ] )
```
the ability to use & to create portals opens up a world of puzzles/golf challenges.
https://lispy-gopher-show.itch.io/lispmoo2/devlog/872152/nud-golf-2-more-nconc
I'll add @mdhughes' https://mdhughes.tech/software/arrokoth/ for the interface this week.
![** Challenge 2 :screwlisp:
*** Input
#+begin_src lisp :exports code
'(a (b c) d (e f))
#+end_src
overwrite the b with the f.
*** Screwtape's solution.
#+begin_src lisp :exports both :cache yes :results output verbatim
(progn
(require :nud)
(in-package :nud/user)
(setq *test2* '(a (b c) d (e f)))
(gird *test2*)
(progn ^^ [ >> >> v [ & ^^ [ >> >> ] )
(print *test2*))
#+end_src
#+RESULTS[2892b5078657512145cbba8e177e48f3b7dc43fd]:
:
: (#1=(#:CURSOR F) D E (F B . #1#))
Well, if you'll believe me that F behind the cursor used to be that b.](https://mastodon.sdf.org/system/media_attachments/files/113/864/565/408/903/752/original/6aea4d0bdc14efdd.png "** Challenge 2 :screwlisp:
*** Input
#+begin_src lisp :exports code
'(a (b c) d (e f))
#+end_src
overwrite the b with the f.
*** Screwtape's solution.
#+begin_src lisp :exports both :cache yes :results output verbatim
(progn
(require :nud)
(in-package :nud/user)
(setq *test2* '(a (b c) d (e f)))
(gird *test2*)
(progn ^^ [ >> >> v [ & ^^ [ >> >> ] )
(print *test2*))
#+end_src
#+RESULTS[2892b5078657512145cbba8e177e48f3b7dc43fd]:
:
: (#1=(#:CURSOR F) D E (F B . #1#))
Well, if you'll believe me that F behind the cursor used to be that b.")
FFmpeg boasts up to a 94x performance increase using hand written assembly!
Via TomsHardware:
"The benchmarking results show that the new handwritten AVX-512 code path performs considerably faster than other implementations, including baseline C code and lower SIMD instruction sets like AVX2 and SSE3. In some cases, the revamped AVX-512 codepath achieves a speedup of nearly 94 times over the baseline, highlighting the efficiency of hand-optimized assembly code for AVX-512.
This development is particularly valuable for users running on high-performance, AVX-512-capable hardware, enabling them to process media content far more efficiently. There is an issue, though: Intel disabled AVX-512 for its Core 12th, 13th, and 14th Generations of Core processors, leaving owners of these CPUs without them. On the other hand, AMD's Ryzen 9000-series CPUs feature a fully-enabled AVX-512 FPU so the owners of these processors can take advantage of the FFmpeg achievement."
CET 