<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Concurrency on NicoLabs</title>
		<link>http://blog.hellonico.info/tags/concurrency/</link>
		<description>Recent content in Concurrency on NicoLabs</description>
		<generator>Hugo</generator>
		<language>ja-JP</language>
		
		
		
		
			<lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="http://blog.hellonico.info/tags/concurrency/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Building Native Parallel Downloads in Coni</title>
				<link>http://blog.hellonico.info/posts/coni/parallel-downloads/</link>
				<pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate>
				<guid>http://blog.hellonico.info/posts/coni/parallel-downloads/</guid>
				<description>&lt;p&gt;One of the great things about building your own language and tooling is the ability to rethink how operations are performed. In our latest commits, we decided to tackle a major bottleneck in our build process: downloading Maven dependencies.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-problem-with-platform-specific-scripts&#34;&gt;The Problem with Platform-Specific Scripts&lt;/h2&gt;&#xA;&lt;p&gt;Previously, the &lt;code&gt;download-url-to-file&lt;/code&gt; function in Coni relied on shelling out to platform-specific tools:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;On Linux/macOS, it spawned a &lt;code&gt;curl&lt;/code&gt; process.&lt;/li&gt;&#xA;&lt;li&gt;On Windows, it invoked a massive &lt;code&gt;powershell&lt;/code&gt; command using &lt;code&gt;System.Net.WebClient&lt;/code&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;While this worked, it had several drawbacks. First, shelling out to external processes is slow and resource-intensive. Second, the dependency on external tools meant that subtle differences in &lt;code&gt;curl&lt;/code&gt; versions or Windows security protocols could cause unexpected failures. Most importantly, downloading artifacts sequentially using these shell commands meant that resolving a large Maven project would take entirely too long.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
