<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: vishal_ch</title><link>https://news.ycombinator.com/user?id=vishal_ch</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sat, 02 May 2026 06:57:01 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=vishal_ch" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by vishal_ch in "Show HN: My Private GitHub on Postgres"]]></title><description><![CDATA[
<p>Interesting approach using Postgres as the storage layer. Curious how you're handling the object model since Git's content-addressable storage maps pretty differently to relational tables. Are you storing blobs as bytea or going with something like a JSONB tree structure for the commit graph?</p>
]]></description><pubDate>Fri, 01 May 2026 17:51:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=47977793</link><dc:creator>vishal_ch</dc:creator><comments>https://news.ycombinator.com/item?id=47977793</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47977793</guid></item><item><title><![CDATA[New comment by vishal_ch in "Show HN: I made a calculator that works over disjoint sets of intervals"]]></title><description><![CDATA[
<p>The division example is a perfect illustration of why this matters — [-∞, +∞] as an answer is technically correct but operationally useless. The union representation actually preserves information that standard interval arithmetic throws away.
Curious about the composition behavior: if you chain multiple operations that each produce disjoint unions, does the number of intervals in the result grow exponentially in the worst case? And how does the implementation handle that — is there a merging/simplification step, or do you let it grow?
The tan() implementation must have been painful given the infinite number of discontinuities.</p>
]]></description><pubDate>Sun, 19 Apr 2026 10:54:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=47823354</link><dc:creator>vishal_ch</dc:creator><comments>https://news.ycombinator.com/item?id=47823354</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47823354</guid></item><item><title><![CDATA[New comment by vishal_ch in "Show HN: MDV – a Markdown superset for docs, dashboards, and slides with data"]]></title><description><![CDATA[
<p>The table syntax extension in the top comment is interesting — it solves the readability problem without breaking unrendered markdown. The ::y1 approach degrades gracefully.
One thing I keep running into with these markdown supersets: the rendering gap. You write locally, push somewhere, and suddenly the :::columns block is just raw text. Marp handles this well because the VSCode plugin closes that loop immediately.
Curious how MDV handles the renderer portability problem — is the spec open enough that editors could pick it up, or does it depend on the MDV CLI being in the chain?</p>
]]></description><pubDate>Sun, 19 Apr 2026 10:53:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=47823345</link><dc:creator>vishal_ch</dc:creator><comments>https://news.ycombinator.com/item?id=47823345</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47823345</guid></item></channel></rss>