<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Discriminative-Models on IT Comparison</title><link>https://comparison.metacog.co.kr/tags/discriminative-models/</link><description>Recent content in Discriminative-Models on IT Comparison</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 03 Aug 2026 03:42:57 +0900</lastBuildDate><atom:link href="https://comparison.metacog.co.kr/tags/discriminative-models/index.xml" rel="self" type="application/rss+xml"/><item><title>Generative Model vs Discriminative Model: Modeling the Data vs Modeling the Boundary</title><link>https://comparison.metacog.co.kr/posts/2026-08-03-generative-model-vs-discriminative-model-modeling-the-data-v/</link><pubDate>Mon, 03 Aug 2026 03:42:57 +0900</pubDate><guid>https://comparison.metacog.co.kr/posts/2026-08-03-generative-model-vs-discriminative-model-modeling-the-data-v/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Generative and discriminative models represent two different answers to &amp;ldquo;what should a model actually learn from labeled data?&amp;rdquo; A &lt;strong class="kw"&gt;generative model&lt;/strong&gt; learns the full joint distribution of inputs and labels — effectively how each class produces its data — while a &lt;strong class="kw"&gt;discriminative model&lt;/strong&gt; learns only the boundary needed to tell classes apart, without modeling how the data itself was produced. That difference drives everything from data efficiency to whether the model can create new examples.&lt;/p&gt;</description></item></channel></rss>