#fridaycheckin (Observed)

The 21st annual Genetic Programming Theory & Practice workshop was a couple of weeks back, and it was nice and upbeat, with a lot of good ideas. It Gave Me Ideas, as usual. But this time around I painted myself into a corner by (1) suggesting folks create short explainer videos for discussion throughout the rest of the year but also (2) NOT volunteering to run it.

So somebody else volunteered to run it, and then told me I’d be first.

1/N

#fridaycheckin (observed)

So this last 10 days or so I’ve been learning #Manim and refreshing my Python stuff after a decade of Clojure & Swift, which has been… OK? Python3 is not bad, and the big libraries and notebooks didn’t exist before.

Having to type `range(len(list))` is still a damned sin though.

Anyway hoping to get the Manim video scenes done in a couple days, then voiceover and editing and maybe a bloop of electronic soundtrack.

Wonder if I know anybody who does bloops.

#fridaycheckin #Manim

anyway the video will be about various tricks and fiddly insights I’ve had over the years about old-fashioned lisp-style tree GP, @lspector’s PushGP, and how to interconvert and use them both together for I dunno…fun but not profit.

Oh and running infinite programs. I hate code that terminates. I need to really try harder to show folks in the GP community why.

@Vaguery Aside: list(range(value)) is also a sin. I want a literal list of value number of items. A list, not a goddamned worthless iterator, an actual range of values - the result of the original range() function before some incompetent decided that words don't have meaning and personal pique was more important than millions of lines of existing code.

This is the kind of behavior that makes me hate anything to do with functional programming. Some times I have a small amount of work that I want done Right Now and I don't want or need lazy evaluation. I need the code to do what I told it to do now, not what it feels like when it feels like it. It may not be fair to blame all of FP for what's properly Python's malfunctions but given how much Python tries to ram FP down your throat whether it serves your problem or not, it's difficult to assign blame appropriately.

@arclight We should do Ruby's lambda and Proc implementation too, just for parity :)

Another day perhaps.

@Vaguery Living in SE Michigan, there's a likelihood of bloops producers within rock throwing distance in every direction.