<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Core | iLog</title>
	<atom:link href="https://isite.tw/tags/core/feed" rel="self" type="application/rss+xml" />
	<link>https://isite.tw</link>
	<description>日誌、科技、軟體、硬體、手機、架站</description>
	<lastBuildDate>Sat, 06 Jan 2018 14:26:38 +0000</lastBuildDate>
	<language>zh-TW</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://isite.tw/wp-content/uploads/2015/09/cropped-icon_512-150x150.png</url>
	<title>Core | iLog</title>
	<link>https://isite.tw</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">85978772</site>	<item>
		<title>(2018/01/06 更新 v2) Intel 爆發史上影響範圍最廣的處理器安全漏洞事件，解決方案可能造成性能下降</title>
		<link>https://isite.tw/2018/01/04/18749?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=intel-%25e7%2588%2586%25e7%2599%25bc%25e5%258f%25b2%25e4%25b8%258a%25e5%25bd%25b1%25e9%259f%25bf%25e7%25af%2584%25e5%259c%258d%25e6%259c%2580%25e5%25bb%25a3%25e7%259a%2584%25e8%2599%2595%25e7%2590%2586%25e5%2599%25a8%25e5%25ae%2589%25e5%2585%25a8%25e6%25bc%258f%25e6%25b4%259e%25e4%25ba%258b%25e4%25bb%25b6%25ef%25bc%258c</link>
					<comments>https://isite.tw/2018/01/04/18749#comments</comments>
		
		<dc:creator><![CDATA[Andrew Huang]]></dc:creator>
		<pubDate>Wed, 03 Jan 2018 16:29:53 +0000</pubDate>
				<category><![CDATA[硬體技術與教學]]></category>
		<category><![CDATA[AMD]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[Core]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[Intel]]></category>
		<category><![CDATA[memory leak]]></category>
		<category><![CDATA[安全性漏洞]]></category>
		<category><![CDATA[漏洞]]></category>
		<category><![CDATA[硬體]]></category>
		<guid isPermaLink="false">https://isite.tw/?p=18749</guid>

					<description><![CDATA[<p>(2018/01/06 更新) 蘋果已針對此次事件旗下產品之受影響情形發出聲明故本文內容已進行修正、Intel [&#8230;]</p>
The post <a href="https://isite.tw/2018/01/04/18749">(2018/01/06 更新 v2) Intel 爆發史上影響範圍最廣的處理器安全漏洞事件，解決方案可能造成性能下降</a> first appeared on <a href="https://isite.tw">iLog</a>.]]></description>
		
					<wfw:commentRss>https://isite.tw/2018/01/04/18749/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">18749</post-id>	</item>
		<item>
		<title>寫在改朝換代前，為什麼我不建議現在換電腦？</title>
		<link>https://isite.tw/2015/07/20/13432?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=%25e5%25af%25ab%25e5%259c%25a8%25e6%2594%25b9%25e6%259c%259d%25e6%258f%259b%25e4%25bb%25a3%25e5%2589%258d%25ef%25bc%258c%25e7%2582%25ba%25e4%25bb%2580%25e9%25ba%25bc%25e6%2588%2591%25e4%25b8%258d%25e5%25bb%25ba%25e8%25ad%25b0%25e7%258f%25be%25e5%259c%25a8%25e6%258f%259b%25e9%259b%25bb%25e8%2585%25a6%25ef%25bc%259f</link>
					<comments>https://isite.tw/2015/07/20/13432#comments</comments>
		
		<dc:creator><![CDATA[Andrew Huang]]></dc:creator>
		<pubDate>Sun, 19 Jul 2015 18:43:51 +0000</pubDate>
				<category><![CDATA[硬體新品情報]]></category>
		<category><![CDATA[Broadwell]]></category>
		<category><![CDATA[Core]]></category>
		<category><![CDATA[Haswell]]></category>
		<category><![CDATA[Intel]]></category>
		<category><![CDATA[Skylake]]></category>
		<category><![CDATA[硬體]]></category>
		<category><![CDATA[電腦組裝選購攻略]]></category>
		<guid isPermaLink="false">https://isite.tw/?p=13432</guid>

					<description><![CDATA[<p>最近正逢大學指考的成績公佈，還有早已放榜正在享受暑假生活的學測、繁星生，許多準大學生在自己未來四年的歸宿終於塵 [&#8230;]</p>
The post <a href="https://isite.tw/2015/07/20/13432">寫在改朝換代前，為什麼我不建議現在換電腦？</a> first appeared on <a href="https://isite.tw">iLog</a>.]]></description>
		
					<wfw:commentRss>https://isite.tw/2015/07/20/13432/feed</wfw:commentRss>
			<slash:comments>14</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">13432</post-id>	</item>
	</channel>
</rss>
