<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Algorithms on Blowing in the wind</title>
    <link>https://zheng-bobo.github.io/en/categories/algorithms/</link>
    <description>Recent content in Algorithms on Blowing in the wind</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 13 Nov 2019 20:32:10 +0800</lastBuildDate>

  <atom:link href="https://zheng-bobo.github.io/en/categories/algorithms/index.xml" rel="self" type="application/rss+xml" />


    <item>
      <title>Why Is Quicksort Used More Often Than Merge Sort?</title>
      <link>https://zheng-bobo.github.io/en/post/why-quicksort-is-used-more-than-merge-sort/</link>
      <pubDate>Wed, 13 Nov 2019 20:32:10 +0800</pubDate>

      <guid>https://zheng-bobo.github.io/en/post/why-quicksort-is-used-more-than-merge-sort/</guid>
      <description>What is honey to you is arsenic to another.   Quick sort: 1 2 3  * Worst-case time complexity: O(n^2) * Best-case time complexity: O(n log n) * Average time complexity: O(n log n)   Merge sort: 1  * Worst-, best-, and average-case time complexity: O(n log n)   Since the time complexity of merge sort is &amp;gt;= the time complexity of quick sort in different situations, why are the sorting algorithms we use in actual programming quick sort instead of merge sort?</description>
    </item>

  </channel>
</rss>