<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:media="http://search.yahoo.com/mrss/"

	>
<channel>
	<title>
	Comments on: Fucking FormatStyle	</title>
	<atom:link href="https://wadetregaskis.com/fucking-formatstyle/feed/" rel="self" type="application/rss+xml" />
	<link>https://wadetregaskis.com/fucking-formatstyle/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2024 22:00:43 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Wade Tregaskis		</title>
		<link>https://wadetregaskis.com/fucking-formatstyle/#comment-3844</link>

		<dc:creator><![CDATA[Wade Tregaskis]]></dc:creator>
		<pubDate>Sat, 18 May 2024 22:00:43 +0000</pubDate>
		<guid isPermaLink="false">https://wadetregaskis.com/?p=8181#comment-3844</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://wadetregaskis.com/fucking-formatstyle/#comment-3843&quot;&gt;Michael Critz&lt;/a&gt;.

Yeah, I end up with a family of &lt;code&gt;asPercent&lt;/code&gt; convenience properties as well.

I haven&#039;t really cogitated on it, but I tend to feel that some simple methods would have been much easier (for humans and the compiler) than the existing, complex design.  e.g. &lt;code&gt;asPercent(…)&lt;/code&gt; with just all the relevant parameters as actual method parameters, all in one place, easy to auto-complete, hard to get lost in.

That could also be added through extensions, I just haven&#039;t happened to get that far yet - most of my uses are fairly specific, so I haven&#039;t been compelled to generalise.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://wadetregaskis.com/fucking-formatstyle/#comment-3843" data-wpel-link="internal">Michael Critz</a>.</p>
<p>Yeah, I end up with a family of <code>asPercent</code> convenience properties as well.</p>
<p>I haven&#8217;t really cogitated on it, but I tend to feel that some simple methods would have been much easier (for humans and the compiler) than the existing, complex design.  e.g. <code>asPercent(…)</code> with just all the relevant parameters as actual method parameters, all in one place, easy to auto-complete, hard to get lost in.</p>
<p>That could also be added through extensions, I just haven&#8217;t happened to get that far yet &#8211; most of my uses are fairly specific, so I haven&#8217;t been compelled to generalise.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Michael Critz		</title>
		<link>https://wadetregaskis.com/fucking-formatstyle/#comment-3843</link>

		<dc:creator><![CDATA[Michael Critz]]></dc:creator>
		<pubDate>Sat, 18 May 2024 21:53:51 +0000</pubDate>
		<guid isPermaLink="false">https://wadetregaskis.com/?p=8181#comment-3843</guid>

					<description><![CDATA[I like that extensions exist to help smooth this down. I don’t like that these API ship to us like this to begin with.

My ideal would be like:

&lt;code&gt;Text(progress.percent())&lt;/code&gt;]]></description>
			<content:encoded><![CDATA[<p>I like that extensions exist to help smooth this down. I don’t like that these API ship to us like this to begin with.</p>
<p>My ideal would be like:</p>
<p><code>Text(progress.percent())</code></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
