* read from the database

* make a request to an API (or really any kind of long running non-database thing)

* write to the database

You're going to end up with a transaction that is open way longer than it needs to be, particularly if you're upstream API is misbehaving, which will potentially end up causing a lot more grief.

How are people solving that issue with SQLite? Everytime I’ve investigated it, it seems like the state of the art is not very battle tested WAL shipping solutions.

If I’m setting something like that up, suddenly running Postgres with its battle tested replication starts to look not so much more complicated in comparison.

Maybe focus the site on capturing ratings to start instead of sharing ratings for products that don't have many ratings (visual studio appears to be highest rated product with 2 ratings).

If you just showed me two related products and had me click on my favorite, I'd probably do that 10 times for no good reason.

I suppose it’s interesting to see how they make better greenfield apps. But I am much more interested in how they solve hard problems in existing gnarly codebases.

Even if they sell the debt to collections, the collections service is probably only going to pay them fractions of pennies on the dollar, since "bill for random service someone signed up for the internet" is not likely to have a high recovery rate.

It seems like it's driven either by 1) people hearing Macs are good for AI, buying one, and using Claude for inference, not realizing that you interact with the anthropic API from an internet connected hair dryer. Or 2) people want their agents to have blue bubbles.

I find it hard to believe that enough normal people are doing on device inference is driving Mac Mini's out of stock. And even if they were the Mac mini is not actually a very good platform for it.

It still tends to do those things, but maybe 40% less.

Though in my experience dogs that are ok with fireworks are the edge case.

Comments URL: https://news.ycombinator.com/item?id=48799736

Points: 4

# Comments: 5

She posted through the trip and answered a lot questions about logistics and the experience.

The one in my car sucks, and to use the most basic features (navigation, music) that cost nothing on CarPlay (beyond my phone bill) cost $15-25/month from Toyota.

Comments URL: https://news.ycombinator.com/item?id=48732489

Points: 2

# Comments: 0

This has been a big pain point me with various VM solutions I’ve tried. Having to allocate say 8GB to a sandbox, and a) having that RAM eaten up when I’m not using it and b) only having 8GB when I am using kinda sucks.

Yes, I could stop the sandboxes when I’m not using them, but that also kinda sucks.

I really don’t understand why everyone insists that you should use it as a work/message queue.

There are lots of purpose-built bullet proof queuing systems that are simple to setup and administer (or just use SQS).

Your queue is likely to have very different access patterns than the rest of your data, and sticking it in Postgres means you’re probably going to end up setting up partitions or optimizing auto-vacuum on that table way earlier than you probably need to mess around with this things in your scaling.

If your queue has more than a few hundred jobs a day (or you anticipate that like anytime soon), just use a queue.

Zuckerberg likely has similar tendencies, should he be given a pass for making social media such a large part of our society?

Though Carmack certainly gets credit for keeping me entertained for a good portion of my youth.

And gates probably gets some civilizational credit for what he’s done with his wealth after he made it.