8,512 karma · joined April 26, 2010
Segmentation fault (core dumped)
In fact, I find Django and Postgres to be the best solution for htmx but Go stack is probably almost as good in terms of developer velocity and obviously much faster. So I think that's a good solution.
You can really build powerful production apps with htmx, and what people underestimate is how good it is with AI assisted development (Claude understands it and does it well, and if any JS glue logic on a specific template is required, it's pretty well written and not a mess).
Soniox came out really good. OpenAI started getting some things very wrong and even introduced some German. Google did okay but cut off the start by several seconds.
What's Soniox doing (left most) that's making it so good ? It was also the only one that could distinguish between the speakers.
In which case your sentiment is probably correct. And now that I think of it, this is potentially very bad news for the outsourcing companies in countries like India. They also have less money to spend on tokens.
Humanity can then relax in floating chairs drinking soft drinks and consuming AI generated entertainment.
ZStack {
NaturePhoto()
LightEffectOnBlack()
.blendMode(.plusLighter)
}
How is the performance?What you speak of may happen, but I doubt it will happen in the next 10 years.
> After some performance checks it became clear that PostgreSQL was even faster than reading from the file system for our use-case. PostgreSQL uses the file system very efficiently for its data - and it adds a lot of caching and efficient reading and writing strategies that can outperform writing and reading raw data on a file system.
This goes against conventional knowledge. I've always heard (and followed best practice) to avoid storing binary data in BYTEA columns that should otherwise be put on a filesystem or an object storage like S3.
I'd like to find out more about this, because in many cases it would be very convenient indeed to store it in the database itself.
Have a look at https://diskprices.com/ - this is great UX because it's extremely functional, yet it has nearly no design to speak of. On a scale of data dense designs, this one would be on the extreme side, so I guess if you ask the LLM to meet you somewhere in the middle.