<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nokogiri on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/nokogiri/</link>
    <description>Recent content in Nokogiri on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 21 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/nokogiri/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ruby Web Scraping Libraries: Nokogiri vs Mechanize vs KimuraFramework — Picking the Right Tool for Data Extraction</title>
      <link>https://www.pistack.xyz/posts/2026-07-21-ruby-web-scraping-nokogiri-mechanize-kimurarails/</link>
      <pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-21-ruby-web-scraping-nokogiri-mechanize-kimurarails/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Ruby has long been a favorite language for web scraping thanks to its expressive syntax and mature ecosystem of HTML parsing and HTTP interaction libraries. Whether you&amp;rsquo;re extracting product prices from e-commerce sites, aggregating news headlines, or building a data pipeline that ingests web content, choosing the right scraping library can make the difference between a maintainable project and a fragile mess.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
