Recent submissions

Comment · 1 year ago
Glad you find it useful! :)
Comment · 1 year ago
It adds notable complexity, and I sense that the whole server/client side component reality is wildly ill-understood.
Comment · 1 year ago
There are often additional hints to go by, e.g., the executed network requests, the user path taken or "breadcrumbs", i.e., custom events captured.

Of course that requires a certain operational maturity.

Comment · 1 year ago
What's missing are the summaries that web developers are commonly used to. For example, the network tab in the developer tools. It is arguably very handy for development – and often more actionable than having to step through individual requests.

But you are of course also right that you can just attach a debugger. That's also called out in the article.

Comment · 1 year ago
Web browser developer tools are incredible, but what do you do when more of your work is shifting to the server? These tools are no longer available or only provide minimal insights. Bye-bye network tab and source tab! That's a challenge for developers adopting React Server Components (RSCs).
Comment · 1 year ago
You should put all these interactions on the web. For education purposes ofc.
Comment · 1 year ago
Somewhat unrelated, but I'd love to have an ability to export Google docs to semantic HTML. To easily put legal documents on websites. It is otherwise a big pita in the collaboration with legal and updates to ToS/privacy policy etc.
Comment · 1 year ago
Yes, it absolutely works. I meant that this is currently not intuitively discoverable :)
Comment · 1 year ago
Pretty interesting visualization. I wonder if you could indicate better that the dial can be interacted with via the mouse?
Comment · 2 years ago
Perses is an excellent step towards vendor neutrality. We at Dash0 are basing our dashboarding data model entirely on Perses to allow you to bring/take away as much of your configuration as possible.

The team around Perses did a solid job coming up with the data model and making it look very Kubernetes manifest-like. This makes for good consistency, especially when configuring via Kubernetes CRs.

Comment · 2 years ago
The OpenTelemetry collector works very well for us – even for internal pipelines. You can build upon a wide array of supported collector components; extending it with your own is also relatively straightforward. Plus, you can hook up Kafka (and others) for data ingress/egress.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton