+1 to this. Evolving the lib to support text too would be high roi.  <div><br></div><div>I&#39;d be happy to help maintain URI if that sort of change / evolution was in scope for how to evolve it.  <span></span><br><div><br>
On Friday, August 15, 2014, Herbert Valerio Riedel &lt;<a href="mailto:hvr@gnu.org">hvr@gnu.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2014-08-15 at 10:35:54 +0200, Christian Maeder wrote:<br>

<br>
[...]<br>
<br>
&gt; network-uri should be preferred over other &quot;uri&quot; packages [1]<br>
<br>
Tbh, I don&#39;t like the current Network.URI API, as it&#39;s heavily &#39;String&#39;<br>
based. If you have process/store a lot of URIs you incur a measurable<br>
overhead.<br>
<br>
Fwiw, this has been noticed in the past:<br>
<br>
 - <a href="http://www.haskell.org/pipermail/haskell-cafe/2012-March/100004.html" target="_blank">http://www.haskell.org/pipermail/haskell-cafe/2012-March/100004.html</a><br>
<br>
 - <a href="http://permalink.gmane.org/gmane.comp.lang.haskell.libraries/18761" target="_blank">http://permalink.gmane.org/gmane.comp.lang.haskell.libraries/18761</a><br>
<br>
<br>
However, I am not aware of any Network.URI replacement based on &#39;Text&#39;<br>
or &#39;ByteString&#39; yet. So far I&#39;ve just coded up minimal URL parsers that<br>
worked on a small subset of the URI grammer when I wanted something more<br>
efficient.<br>
<br>
Cheers,<br>
  hvr<br>
_______________________________________________<br>
Libraries mailing list<br>
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;Libraries@haskell.org&#39;)">Libraries@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/libraries" target="_blank">http://www.haskell.org/mailman/listinfo/libraries</a><br>
</blockquote></div></div>