<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: Pranav_Ghoghari</title><link>https://news.ycombinator.com/user?id=Pranav_Ghoghari</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 27 Sep 2026 13:56:16 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=Pranav_Ghoghari" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by Pranav_Ghoghari in "Special Projects (2016)"]]></title><description><![CDATA[
<p>Its really impressive that they stuck to their vision over the long term. This is difficult and more challenging than it sounds.</p>
]]></description><pubDate>Fri, 25 Sep 2026 09:59:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=49842334</link><dc:creator>Pranav_Ghoghari</dc:creator><comments>https://news.ycombinator.com/item?id=49842334</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49842334</guid></item><item><title><![CDATA[New comment by Pranav_Ghoghari in "Introducing System One Models and Jev"]]></title><description><![CDATA[
<p>I am not sure for how long the output will stay absolutely free. But apart from the pricing advantage of Jev itself, I just love the simplicity of having only an input price. Input is pretty easy to estimate and calculate upfront, which makes the cost of running something at scale much more predictable.<p>With LLMs, even with JSON schema constraints and structured output, the actual cost can still be hard to predict because of varying output lengths and, especially, unpredictable reasoning costs. There is something really nice about being able to tokenize and predicting the budget beforehand.</p>
]]></description><pubDate>Sun, 20 Sep 2026 10:59:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=49774568</link><dc:creator>Pranav_Ghoghari</dc:creator><comments>https://news.ycombinator.com/item?id=49774568</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49774568</guid></item><item><title><![CDATA[New comment by Pranav_Ghoghari in "Ask HN: What are you working on? (September 2026)"]]></title><description><![CDATA[
<p>Trying to take Vector DBs beyond RAG.<p>Thinking about making an open-source library specific to Vector related operations like clustering, classification, anomaly detection to make it easy for developers to get more out of their vector embeddings. Basically sk-learn for Vector operations.</p>
]]></description><pubDate>Wed, 16 Sep 2026 13:46:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=49726990</link><dc:creator>Pranav_Ghoghari</dc:creator><comments>https://news.ycombinator.com/item?id=49726990</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49726990</guid></item><item><title><![CDATA[New comment by Pranav_Ghoghari in "Ask HN: If embeddings are so powerful, why are they mostly used for retrieval?"]]></title><description><![CDATA[
<p>Trueee,,,the use cases normally are very engineering oriented and not useful for every end user.</p>
]]></description><pubDate>Sun, 13 Sep 2026 17:15:10 +0000</pubDate><link>https://news.ycombinator.com/item?id=49686193</link><dc:creator>Pranav_Ghoghari</dc:creator><comments>https://news.ycombinator.com/item?id=49686193</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49686193</guid></item><item><title><![CDATA[Ask HN: If embeddings are so powerful, why are they mostly used for retrieval?]]></title><description><![CDATA[
<p>Vector embeddings natively are capable of much more than just retrieval. Even when OpenAI released their initial embedding models, it mentioned that their embeddings are natively capable of Search, Clustering, Recommendations, Anomaly Detection, Diversity Measurement, and Classification.<p>But everything is concentrated around Vector DBs and RAG, and is progressing towards GraphRAG and Knowledge Graphs. Why are the other representations being underused? Like, why didn’t they catch up?<p>Everyone is complaining that RAG is dead, Vector DBs are done, they are expensive, and the ROI is not worth it. I know most of this is noise. Embeddings are meaningful and a part of many production pipelines. But why don’t these people try to get more value out of their existing stored embeddings?<p>I don’t know if it’s just me being delusional, but I feel there is a lot of hidden potential that is untapped. Why is retrieval so dominant? I mean, yeah, search has throughout history been a really important operation across any data. But the purpose of embeddings itself was to capture semantic relations beyond just search. Is it because search is the easiest to productize and build features around? And other use cases are not so frequent?</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=49685838">https://news.ycombinator.com/item?id=49685838</a></p>
<p>Points: 2</p>
<p># Comments: 2</p>
]]></description><pubDate>Sun, 13 Sep 2026 16:38:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=49685838</link><dc:creator>Pranav_Ghoghari</dc:creator><comments>https://news.ycombinator.com/item?id=49685838</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49685838</guid></item></channel></rss>