One interesting thing I found recently was after enforcing geo-fencing, recaptcha intermittently started failing. They might be using global edge servers or something

I’m getting surprisingly good results on GEMMA4 2 bit, running on a Nvidia nano and raspberry pi

Used to follow this to a T. Love 12factor, evangelized it at a lot of companies too

Hot take - but I’d learn to build CNNs from scratch. We are only just now scratching the surface of convolutional neural networks capabilities

Self hosted GitLab has been good to me forever and has scaled and has a controllable attack surface as long as you keep on top of it

Newer app is moving to Google Cloud Secure Source Manager (because we are on Google Cloud and using backbone auth so it made more sense and less involved to manage)

If you look at how this works under the hood, “when two words that don’t necessarily matter to the context, it will pick one word over the other and a pattern emerges”

And that pattern will be reverse engineered in weeks by a startup

And a downstream agent produced by said startup will be built to roll those dice again and defeat the watermarking

And a the LLM vendors will combat this

And a cottage industry shall be born anew

To be fair, the circle jerk in virtual space is limitless. Its just unbounded reach arounds, turtle cum all the way down, human detritus as far as the eye can see.

The same VC capital will chase it because god forbid we fail at real challenges; no, we must build the torment nexus.

Have a pretty large application running HTMX + WebComponents + Hono + Cloud Functions to serve up frontends, happy with it for about 2 years now

People throw salt at my stack but it’s fast, and straightforward to manage attack surface

I'm using Hono + Tanstack Router as a Next.js replacement. Best software related decision I ever made, it feels like I stopped fighting with the stack.

It is Apple platform only implementation because of Metal (and Swift). Other platforms would require CUDA or Vulkan and a complete rework

Replace React / Vue with HTMX 2 years ago and still going strong.

Hono + WebComponents + HTMX + serverless is the backend for my apps now.

What is the point of using HTMX if your backend is JavaScript(Hono)?

Adopting something like HTMX is primarily a UX choice, and the language you use to serve it is almost irrelevant to UX. JavaScript is a nice backend language. It’s fast, has a massive ecosystem, and many people know it well.

I don't see how HTMX has anything to do with UX. Could you clarify what you mean?

Sure. I personally think SPAs/React have better DX than HTMX. IMO, the most compelling reasons to use HTMX instead (for building dynamic/interactive web applications) are to reduce the amount of JavaScript sent to the client and make pages become interactive faster. These are UX concerns: how much the user has to download (waiting) and how long before the page becomes interactive (waiting).

With HTMX, you get these benefits regardless of what language you use on the server. These benefits could be reasons the parent commenter chose HTMX, and JavaScript is a perfectly good language to serve HTMX applications for the reasons I mentioned.

> the most compelling reasons to use HTMX instead (for building dynamic/interactive web applications) are to reduce the amount of JavaScript sent to the client and make pages become interactive faster

Next.js and TanStack Start don't send any JavaScript to the client if you decide to server-render everything. The upside is that you can opt-in into client-side components, and have all the interactivity benefits of React. I understand using HTMX if you are building a backend in Go/Python/..., but if you are already using Node, I see no reason not to use TanStack Start instead.

> Next.js and TanStack Start don't send any JavaScript to the client if you decide to server-render everything.

AFAIK, this isn’t true. And you still get more JS per interactive element than with HTMX.

Maintenance burden, supply chain attacks and the constant dependency upgrade treadmill. With a very minimal footprint app, you can avoid all that to a large extent.

We ended up doing the same, own harness with a world view (schema.org) and map reduce rather than a RAG. Happy with the results and context hydration speed