Life is Tetris @tetrislife@qoto.org

Thanks to a colossal amount of work by Jacob Young, the x86_64 backend of Zig is now passing 101% of the behavior tests compared to the LLVM backend.

Or perhaps put another way, the LLVM backend is passing 99% of the behavior tests compared to the x86_64 backend 😉

Still a few more issues to tackle before it can be made the default, however.

@profoundlynerdy That's really interesting to hear. I perceive python's popularity as streaming from diametrically opposing sources - grassroots enthusiasm from a wide variety of geeks who found it to be useful. In my mind , the PyCon conference exemplified this: scrappy, inclusive, run at cost by volunteers. Compared to previous establishment like Java or C++, which were very expensive corporate affairs.

@julesh @indigoparadox Is that part of why corposcum hate Lisp?

Programming languages train you to not want what they don't provide, which is why programmers should learn a wide variety of different styles in order to not take any shit from language designers

finally some good news

You know what the biggest problem with pushing all-things-AI is? Wrong direction.
I want AI to do my laundry and dishes so that I can do art and writing, not for AI to do my art and writing so that I can do my laundry and dishes.

I noticed two (hopefully minor) errors in the patches I sent earlier:

- I failed to untabify a couple of added lines in the second patch

- I failed to add the "contributed by" note to RELEASE_NOTES.md in the third patch

if you'd like me to send fixed versions thereof, whether over these minor issues or other ones, just let me know.

I'm open to discussing the design and details of any of them. the third is more of a working prototype than a proper implementation: the packing of so much functionality in a single function is probably unwise, maintenance-wise, but that was what worked, so that's what I shared to get a concrete depiction of the feature across, to get the conversation about it started. I hope the feature makes sense to you.

another nit: I found that the placement of the link to the message in the date is less than ideal. it might be better to place it next to the interaction buttons, where one would look for them after reading the whole message. I find myself occasionally having to page back up to get back to it, which I find less than ideal. the date made sense to me, for not using up more screen real state, and for being "intuitive" for a user coming from GNU social, but I'd be happy to change it. it probably makes sense to add an attribute to have the link opened in a separate tab or page, though; it makes little sense without that IMHO, but I didn't think of it before because I automatically go for the alternate button that will open it in another tab. again, I'd be happy to amend the patch, or post a follow up, just let me know

there's something exciting about using snac to share patches for snac, but I don't suppose it's the most convenient way to share them. if you'd rather get them by other means, I'll probably be happy to oblige; I'm probably going to set up a (plain) anon git server soon (I just haven't got 'round to doing so yet), and I could post only pull requests (in the original sense) here, pointing at branches to pull from in the git server

A graphviz-produced diagram of concepts and artifacts in the Syndicateverse/Preservesverse

@futurebird so. much. junk! I think about this all the time I am going to buy a thing. A lot of the time I end up not buying the thing, because the version that is repairable is like 3 times the price of the shitty one, so maybe I don't need that thing after all - it's a useful filter!