whacked_new

haha I forgot I had hackertube opened in a tab, then when I saw it, I was like, wait, youtube recommendations are actually good? ... oh

I literally just type into the input what functionality I want. In the beginning it was capability exploration: "integrate draw.io", which was quick work, but I never actually used it.

Then I threw actually useful things at it: find this directory of pdf scans, and create an interface where I can browse the files, preview them, and query an lmstudio server, and auto-rename the pdf based on the content.

Another is to ssh to a remote machine that has a particular file organization structure, and give me a preview gallery.

Nothing is particularly complex, but I couldn't be bothered to making that myself. It's also something that I would've used in emacs (the preview function is like dired-preview-mode in emacs), but a graphical interface would perform better.

I agree, it's an awesome concept in principle (and Girba is graciously welcoming people in discord). Working with an agent in GT, the agent will just look at the data and figure out how to express it in the graphical framework.

But in practicality, at least at this point, bb wins out by sheer expansiveness of ecosystem. I was working on a mishmash of an editor interface that combined obsidian with heptabase, directly in GT. It kind of worked. And the amazing thing is, everything has just a single representation: window positions displayed as text automatically have 2 way bindings across widgets, because they are the same data. But even with agents doing everything, 2 things creep up.

First is in JS/TS, all these binding problems are solved 1000x already. You can fake shared memory with callbacks and the agent won't lose track. In GT you move the cursor around, and have to decide at what point do you convert a widget representation to source representation, and when to restore the widget: is it a delay? is it after changing lines? is it after you move off the text? before or after the whitespace? There's a package for that somewhere in npm that answered all these questions, and it has tables, and it's performant. It doesn't do the 2% stuff that GT does using its magical shared memory representation (which also makes TS->smalltalk porting not straightforward), but you can still tape over it with sheer optimized code.

The second thing is that GT got really slow with all the data structure re-interpreting and rerendering. As "dirty" as bb is in reloading dynamic code, the runtimes are so optimized, I wanted the markdown nodes to be GPU-accelerated in bb, and it turns out they already were.

Best comment in <duration>*

* dependent on velocity

This is great! I remember being extremely impressed by Boris Johnson's "great supine protoplasmic invertebrate jellies" insult. How does one come up with such a string of words? I would've used this as a study resource.

I guess there's going to be a perfume that breaks down 2-noneal on the market soon.

Tangentially, in my 20s I was in an audience seating and sat next to an old person. And I smelled a new kind of odor. It was displeasing, but not like body odor. I quickly realized it's an old person smell. It really just makes you think "old person". I assume there's some biological wiring in there.

It's also because exercise requires exertion, which is effortful, and most people who need the exercise would rather spend money to not have to exert.

Does it pain me to say it? Nah, I'm numb :-/

I'm convinced this is true, and think music piracy in the classical sense will be mostly dead in the near future, thanks to AI, which already absorbed most of the pirating and has token-tumbled all the elements so that what most people listen to is already generated from the pirated elements

q3dm17 in the browser... what a time to be alive

this is low key one of the few things that I think of doing for the rest of my life, though my bias is towards seaweed farming and related ecosystems