Any active product or business development - builds product/domain/operational depth. That depth feeds back into every decision.

Without taking into account that depth, complexity, competence of Managers and Employees in that depth, headcount invested into automation, etc, just focusing unidimensionally on some behavioral or organizational methodology, IMHO, makes it worse.

It gives CxOs some cute stories to blame someone or something against. If your coordination is slow, then there is a reason behind it. Find it.

docker.io/node:26-alpine - 61MB

docker.io/node:26-trixie-slim: 84MB

gcr.io/distroless/nodejs26-debian13: 55MB

Before this post, we have issues with different, slower DNS resolution in musl.

In 2026, there in no reason other than self-inflicted compatibility and performance pain to use musl in production services.

It has it's place, for binary cross-OS distribution, and generally having an alternate C STL. But avoid for SaaS.

Sadly, it's often too late. Looks to be the case here, appears clearly a diagnosis delay. It does not take much for a skilled system to connect "airport worker" and the right lab readings together.

I can't imagine what these people would have gone through. They would have been given the "just a flu" treatment for some days, and then waited many more days for appointments. RIP.

PS: What you've said is pretty eye opening! This would amplify a lot of the diagnosis problems.

This is not enough for companies to invest heavily in.

JXL is broad use/ universal. High bit depth, wide gamut, different color spaces — from HDR displays, to web, to print to medical photography and so on. It would help the device that your viewing this on, right now.

It's not like WebP where the only focus is to reduce file size. The fact that it does this also, and also recompresses jpegs lossless, is just an addon, not a singular reason.

If you get a chance, ignore all the file size noise, and look at JXL for what it is and how it's being adopted by different industries.

And it supports animation by default, so the "motion photos" will be natively shareable.

Also, recompressing JPEG as JPEG-XL gives a free boost, so simply, why not. If you're sharing something in social media or anywhere, there is no reason to not convert and have the other person receive JPEG-XL by default.

My point is less about the size and so on. But what the visual (bit depth and color gamut) and functional leap of JPEG-XL. It's a format that combines and replaces the many different use cases that different formats are doing now.

Does it work? yeah... But I'd pick a subscription anyday...

Look at the later comments, they have substance oriented discussions.

HN Mods - can you please consider a policy against such comments, it's overflowing the site and is diluting discourse and value. If people don't like an article, they can simply ignore it. These articles are reaching the top because enough people consider it of value.

But when an article comes to the top, and the topmost comment and discussion thread is an unqualified witch hunt, it's getting sick.

How many people who were writing blogs or creating open source tools before signed an on-call oath or declaration? Does that mean they're all wrong or unqualified?

On call avoidance should be rewarded more than on call superheroism. People managing software fail to realize it. Avoidance is stashing enough operational bullet points, mental checklists and manpages.

Everything is generic — because your use case and your operating environment is ONLY yours. Postgres has hundreds of parameters. Nothing is specific or made to satisfy you. If it doesn't, then you don't call the parameter as generic. You choose what to apply for your environment and expectation.

What you're saying is both a wrong reward cycle and it was also not necessary or practical before AI.

The blog lists ways to optimize sqlite for production, for those who have already made that choice. But these comment links are about choosing sqlite vs others and differences, which is completely unrelated and unnecessary for those who have already made that choice.

I'm seeing a worrying trend on HN. Nearly for all articles, there is one unquantified, unproven comment at the top saying it's 100% AI — no proof, just baseless emotion of what fits the commenter's writing style. This is the new witch hunt, or virtue trolling.

I read the original article and to be honest, this off topic comment definitely looks more like an AI troll bot wrote it than the article. The troll bot is instructed to do a google search and put 3 source links — no matter how irrelevant they are.

So what is it now — one emotion vs another? If an article has sections and blocks, it's AI. What about infinite poor humans like me who have been writing like this since childhood?

Since LLMs were trained on high quality blog posts, we can no longer have posts that fit the pre-AI definition of high quality? The content must be dumbed down with typis and scatter unconventional words, to prove AI trollers that it's not AI? Or a timelapse video of typing the article?

Instead how about: if you don't want to read the article because it doesn't fit your personal style expectation — just don't bother commenting?

I hope HN would ban AI trolling comments, and discuss substance.

On one hand, I'd assume a "focused" feature, like exceptions, would always be easier to fine-tune and optimize the language, runtime and workflow – rather than generalizing it.

But at the same time, the prospect of saying all those are just special forms of a stacked "yield" (just for my mental model) is quite tantalizing.

This is IMHO the reason why we can't have sanity, because there are people ready to hack it.

I did try Bergamot but that was a year ago, and the experience was not as good as Chrome...

Switzerland has one of the highest Internet prices in the world: https://worldpopulationreview.com/country-rankings/internet-...

And don't talk to me about mobile data prices, it's out of the planet.

I would assume the same here. If they are forced to move to EU just because of compliance, the alternatives would remain poor quality.

There is a clear difference between $25k and $100k.

64 iPhones at retail price is already around $64k. For something at 768GB to be profitable at Apple's terms, this has to retail at $100k for it to be profitable. That was the OP's point.