<?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>Computer Science on Yukari's Blog</title><link>https://yukar.icu/tags/computer-science/</link><description>Recent content in Computer Science on Yukari's Blog</description><generator>Hugo</generator><language>zh-cn</language><lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yukar.icu/tags/computer-science/index.xml" rel="self" type="application/rss+xml"/><item><title>Operating System</title><link>https://yukar.icu/posts/cs/operatingsystem/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><guid>https://yukar.icu/posts/cs/operatingsystem/</guid><description>Architecture and core mechanisms of Operating Systems.</description></item><item><title>Operating System</title><link>https://yukar.icu/posts/cs/computerorganization/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><guid>https://yukar.icu/posts/cs/computerorganization/</guid><description>Architecture of Operating System.</description></item><item><title>Package Management: Introduction</title><link>https://yukar.icu/posts/cs/packagemanagement/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://yukar.icu/posts/cs/packagemanagement/</guid><description>&lt;p&gt;A &lt;strong&gt;package manager&lt;/strong&gt; automates the lifecycle of software dependencies: fetch, install, upgrade, configure, and remove. At scale, it answers the question:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Given a set of packages, each with version constraints on its own dependencies, does there exist a consistent assignment of versions such that every constraint is satisfied?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is, at heart, a constraint-satisfaction problem — and different package managers attack it with different algorithms, trade-offs, and scopes of responsibility. This article surveys the landscape, unpacks the resolution mechanisms, and provides a decision framework for choosing the right tool.&lt;/p&gt;</description></item><item><title>Virtual Environment: Practical Guide(To be Continued)</title><link>https://yukar.icu/posts/cs/virtualenvironment/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://yukar.icu/posts/cs/virtualenvironment/</guid><description>&lt;p&gt;A &lt;strong&gt;virtual environment&lt;/strong&gt; is an isolated, self-contained workspace that decouples a project&amp;rsquo;s dependencies, runtime, and configuration from the host system and from other projects. The core tension it resolves is:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Project A and Project B may require different versions of the same dependency, but the host OS allows only one version to be installed globally.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Different tools address this at different layers of the stack:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Docker&lt;/strong&gt; at the OS/kernel level,&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conda&lt;/strong&gt; at the userland binary level,&lt;/li&gt;
&lt;li&gt;&lt;code&gt;uv venv&lt;/code&gt; at the Python interpreter level.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This article will introduce each tool with their design philosophy, logical structure, implementation mechanism, and practical usage examples. It will also provide a comparative summary, debugging strategies for version conflicts and VSCode integration tips.&lt;/p&gt;</description></item></channel></rss>