opencode is a good alternative that doesnt flake out in this way.

Spotlight has really been bothering me lately, for months now, and it’s not even indexing all the time. I disabled all but applications and the calculator, because that’s all I use Spotlight for, and it still can’t find some apps that are in /Applications. Sometimes it’s some apps, sometimes it’s everything, and after rebooting it’ll sometimes reindex. No idea what’s going on, but today might be the day I install Quicksilver, if that’s still a thing.

I also had to type over reindex 3 times to get it to stick :)

Most (all?) Spotlight replacements depend on the same underlying index and system services that Spotlight provides and uses. High chance Quicksilver is just making 'mdfind' calls like everything else, especially since it doesn't look maintained anymore.

LaunchBar doesn't use Spotlight's data. And so, as a result, can't search for data inside files. That said, it provides a Search in Spotlight command – that you can assign a shortcut, if you wish – which returns its results in a new Finder window.

If you’re showing off a UI framework, I shouldn’t be accidentally scrolling left and right on the page on mobile / my iPhone. Couldn’t be bothered to scroll down the page to look at components while accidentally activating horizontal scrolling.

Will get this fixed, thanks!

It happens on Firefox on Android as well

Thanks

It’s fixed for me, nice!

There’s benchmarks in the README. Python is ~10x faster. It’s heavily optimized. Based on the numbers and my experience with Flux.1, I’m guessing the Python run is JIT’d (or Flux.2 is faster), although it’d likely only be ~half as fast if it weren’t (i.e. definitely not 10x slower).

There are a lot of shortcomings in the current implementation, making it slow (but in my tree is 2x faster as we speak). For instance activations aren't taken in the GPU, kernels are not fused, flash attention is not used, and many other issues. Now I'll focus on that changes to approach PyTorch numbers a little bit more.

For a version of macOS that old, you’d probably want a dmg, which you can create with createinstallmedia if you have the Install macOS.app. Not sure if it’s supported with Lume as it’s the first time I’ve heard of it.

I’m just using their API tokens instead of Max. If usage gets out of control, then fine, I might need to look into an alternative. But I’ve grown very accustomed to the model and would rather not switch until I find a real need to.

I’m sorry, but the release of Plasma, around the same time IIRC, was not without controversy.

KDE 4.0 - which introduced plasma - was released in 2006, and it was awful and wasn't supposed to be generally available (blame the distros and/or poor version naming). By version 4.5 (2010), KDE had stabilized. By the time Gnome 3 and Windows 8 were released in 2011/2012 respectively, KDE plasma was pleasant to use and rock-solid

It felt great to watch Gnome stumble after all the shit-talking, some schadenfreude was in order. I didn't care much for Windows 8; Vista was a the bigger mess of a release.

But, come on, a WHOLE OTHER LEVEL of "controversy."

Plasma criticism was pointed and deliberate and grownup. Windows 8, less so.

This is one-shot.

When an API returns JSON, your JS framework can decide what to do with it. If its returning HTML that's intended to go in a particular place on a page, the front-end has far less flexibility and pretty much has to put it in a specific place. Hence why they said endpoints can return 3-5 different versions of HTML.

> When an API returns JSON, your JS framework can decide what to do with it.

The JS framework is the frontend, so you're still coordinating.

> If its returning HTML that's intended to go in a particular place on a page, the front-end has far less flexibility and pretty much has to put it in a specific place.

Well yes, because presumably that's what the app is supposed to do. If it's not supposed to put it in that place, why would that be the specified target?

If this kind of static assignment of targets is not flexible enough for some reason, then use OOB updates which lets you replace fragments by id attribute. That lets you decouple some of these kinds of decisions.

Although "endpoints can return 3-5 different versions of HTML" is also a bit of a red flag that you're not using htmx correctly, generally endpoints should be returning 1, maybe 2 fragments in unusual cases.

In any case, you might find DataStar more to your liking, it's partway between React and htmx.

To clarify, there's nothing React or SPA about datastar. Moreover, HTMX v4 is essentially Datastar-lite (but heavier, and less capable)

There is, Datastar has client-side rendering based on signals [1]. Datastar is also very explicitly designed to be modular and extensible, so you can extend the client-side with more features, as they've done with Web Components.

[1] https://data-star.dev/guide/reactive_signals

Signals aren't even really "rendering". And react and spas dont have a monopoly on doing things on the client - that's just javascript. I dare you to go to the datastar discord and tell them that they're React-adjacent, and SPA-like

"framework can decide what to do with it" sounds like a feature (more flexibility) but is actually often the source of errors and bugs.

A single, consistent, canonical response, generated by the server, taking into account all relevant state (which is stored on the server) is much cleaner. It's deterministic and therefore much more testable, predictable and easier to debug.

For pure UI-only logic (light/dark mode, etc) sure you can handle that entirely client-side, but my comment above applies to anything that reads or writes persistent data.

Wow, Slax is still around and supports Debian now too? Thanks for sharing.

I used to use it during the netbook era, was great for that.