(The motor is less important than the battery in terms of total weight, long term durability, etc. But nonetheless, any improvement helps!)

(We have a couple apps that use BullMQ, and I keep wondering if we could drop Redis and use a PG-backed queue instead, for fewer single points of failure. Maybe this is the one.)

* their app hosting product is similar to Heroku.

* very easy onboarding and controls for modest complexity apps. Unlike the extreme hoop-jumping required to do anything on one of the major cloud providers.

* everything looks reasonably up to date.

* it's an actual operating profitable company that's been around a while and probably will be for a long time... not a startup burning capital.

That said, this magic containers thing looks more analogous to Google Cloud Run, which I think is an absolutely fantastic offering. Unlike almost everything else out there, Cloud Run and presumably Magic Containers can do things like have a whole bunch of versions of your app up and running ready to come to life when a request arrives, but scaled to zero in the meantime. This category of hosting should be far more popular than it is, and it is wonderful to see another company offer it.

That's the whole point, right? A pretense to remove any remaining anonymity from communications?

Governments are endlessly infested with the worst people. They look back at historical attempts at totalitarianism and think to themselves, "Let's facilitate something like that, but worse".

For example, think about "sniping" from the seller side. Sellers are rightly concerned about any wrinkle of the bidding process that might leave money on the table. Automatically extending the time so that every potential buyer has time to "answer" a new bid soothes the concern that buyers were willing to pay higher, but they didn't have the technological prowess to post their bid in the last 0.3 seconds.

Seems like a pointless and foolish product design error for X/grok to publish arbitrary image generation results under its own name. How could you expect that to go anything but poorly?

Sure, you can have your LLM code with any JavaScript framework you want, as long as you don't mind it randomly dropping React code and React-isms in the middle of your app.

If you were copy-pasting long strings of Tailwind classes all over, you were already doing it wrong before you even heard of Daisy.

Starting a new project today, I think the right move is to use TSX or Bun or whatever. You want a roadblock at the very first moment you start trying one of these limited compatibility libraries, Because it won't work and then you'll pick a different library that doesn't rely on non-erasable TypeScript syntax.

Paid hosted software is easier to scale financially.

Without the latter, it's very hard to come up with the money to pay people to build, to support the market, etc.