They let me know what the current big companies are doing to improve developer experience and/or devops. Their teams are often bigger than my entire company, so learning from them is a great way to see what we might be able to implement (whether by buying their service or doing a small scale version of it in-house).
Secondarily, they sometimes also show end-user experience improvements that I never thought would be possible at a certain scale/cost. Cloudflare hosting Doom and IRC on serverless is one such example, or Vercel doing multiplayer live editing (Figma style) out of the box with Next.js is another.
For this case of this particular post, the idea of having an external metadata analytics system for Mysql, stored in a separate store and dashboard, is something I've only vaguely seen in DigitalOcean. Seeing it as fully featured as in Planetscale makes me both wonder if we should consider using them instead of a some generic cloud DB, and also whether we can implement something similar on a standard LEMP container. It's one of the more interesting pieces I read on HN today, actually.
For those of us who don't live and breathe infrastructure, big(ger) tech company blog posts is a great way to learn, and I value them!
Let me help you understand it a little bit more in-depth.
First of all, the title used for this submission does not imply an announcement of a new feature. This one[0], however, does. Now, let's look past that. Let's say that the submission warrants front-page treatment fair and square because it has valuable content (a write-up at the very least). Lo and behold - it does not.
This submission[1] announcing Vercel's Build Output API has both a decent submission title (I can instantly tell it's a feature announcement) and fairly decent explanation for the feature, also. In fact, they even provided links to various documentations to help developers get started right away.
I'm still eagerly awaiting for someone to tell me what they learned from this specific submission.
Now, if your issue was with the article title, I fully agree. I wish the titles here were clearer.
same reason why filesystems are often mounted with noatime attribute !
The next ingredient would be if dropping MySQL tables is a relatively big pain (or known but unmanaged risk) that most of those people have experienced at some point.
Then this feature would be exciting news for that not-so-small cohort and that seems sufficient for HN upvotes?
I don't know if that's what happened today. I've heard about planetscale a few times but never used it. I can attest that dropping tables is always scary.
Don’t get me wrong but clicking on this link I was expecting an actual detailed guide/explanation.
There is nothing anyone can say to justify this being on the front page considering both the submission title and the actual content of the said submission.
There's a "hide" button on HN posts if downvoting them isn't enough for you.
also posted by a former github person. not sure if poster is author or works at planetscale but a lot of ex github engg are there