<?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/"
		>
<channel>
	<title>Comments for brian will . net</title>
	<atom:link href="http://brianwill.net/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://brianwill.net/blog</link>
	<description></description>
	<lastBuildDate>Wed, 04 Nov 2009 06:57:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Why icons suck by Snocrash</title>
		<link>http://brianwill.net/blog/2007/02/18/why-icons-suck/comment-page-1/#comment-4067</link>
		<dc:creator>Snocrash</dc:creator>
		<pubDate>Wed, 04 Nov 2009 06:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/2007/02/18/why-icons-suck/#comment-4067</guid>
		<description>ICONS SUCK BAD

I hate them. On my TV, in my Car, my Phone - everywhere.  Often leaving the user completely clueless as to what they actually do.

But, it seems, they&#039;re not going to go away any time soon.  Evilness - that&#039;s all they are - For illiterate morons who can&#039;t read.</description>
		<content:encoded><![CDATA[<p>ICONS SUCK BAD</p>
<p>I hate them. On my TV, in my Car, my Phone &#8211; everywhere.  Often leaving the user completely clueless as to what they actually do.</p>
<p>But, it seems, they&#8217;re not going to go away any time soon.  Evilness &#8211; that&#8217;s all they are &#8211; For illiterate morons who can&#8217;t read.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reinventing the desktop (part 2): I heard you like lists&#8230; [text version] by Candy Randy</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-4056</link>
		<dc:creator>Candy Randy</dc:creator>
		<pubDate>Thu, 08 Oct 2009 23:27:40 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-4056</guid>
		<description>&quot;You left out hot keys, and a quickly accessible app-launch.

alt+f2 and type application (my favorite launcher is katapult and the keys for that are alt+space)
and in general, hotkeys it up… win+w is web browser, win+f is file manager, win+e is text editor, and win+d is doom3 (always a pleasure to accidentally open it between the two and get side tracked for an hour :)&quot;

That is nowhere near as efficient and easy as it could be. There is a much better way, but I will reveal all soon...

I&#039;m just amazed nobody has thought of it already - it shows how unable to think outside the box the entire world of computer users is...</description>
		<content:encoded><![CDATA[<p>&#8220;You left out hot keys, and a quickly accessible app-launch.</p>
<p>alt+f2 and type application (my favorite launcher is katapult and the keys for that are alt+space)<br />
and in general, hotkeys it up… win+w is web browser, win+f is file manager, win+e is text editor, and win+d is doom3 (always a pleasure to accidentally open it between the two and get side tracked for an hour :)&#8221;</p>
<p>That is nowhere near as efficient and easy as it could be. There is a much better way, but I will reveal all soon&#8230;</p>
<p>I&#8217;m just amazed nobody has thought of it already &#8211; it shows how unable to think outside the box the entire world of computer users is&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reinventing the desktop (part 2): I heard you like lists&#8230; [text version] by Candy Randy</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-4055</link>
		<dc:creator>Candy Randy</dc:creator>
		<pubDate>Thu, 08 Oct 2009 23:25:26 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-4055</guid>
		<description>&quot;Before iTunes and its imitators, users would play their music by navigating into folders, e.g. ‘music\artist\album\’. Today, iTunes simply presents everything in one big list that is textually filtered.&quot;

Using folders for your music is a GOOD idea, unless you&#039;re one of the masses of idiots who pretends to &#039;like&#039; music, and has to pretend to &#039;want&#039; to listen to &#039;rock&#039; today, or &#039;jazz&#039; tomorrow, thus needing iTunes and its bloody irritating &#039;filing&#039; system to find them what they pretend to &#039;want&#039; to listen to.

I know where every single song in my 4,000 track MP3 collection is, all filed in folders, either by artist, or about 10% in &#039;genre&#039; folders, such as &#039;80s&#039;, &#039;Love&#039;, &#039;Dance&#039;, etc. I don&#039;t want a long list of 4,000 tracks, thank you, that&#039;s for idiots.

Your &#039;long list&#039; idea doesn&#039;t work when you are dealing with thousands of files. I remember the position of some of the 4,000 songs SPATIALLY, i.e. I know it&#039;s in the first, top level folder, 
A-F
not in 
G-M
or whatever, and then within 
A-F
it&#039;s within
Dance
etc.

Your &#039;huge list&#039; idea is stupid. Microsoft&#039;s &#039;Ribbon&#039; is equally stupid. 

Spatial memory is where it&#039;s at. I will reveal all very soon...</description>
		<content:encoded><![CDATA[<p>&#8220;Before iTunes and its imitators, users would play their music by navigating into folders, e.g. ‘music\artist\album\’. Today, iTunes simply presents everything in one big list that is textually filtered.&#8221;</p>
<p>Using folders for your music is a GOOD idea, unless you&#8217;re one of the masses of idiots who pretends to &#8216;like&#8217; music, and has to pretend to &#8216;want&#8217; to listen to &#8216;rock&#8217; today, or &#8216;jazz&#8217; tomorrow, thus needing iTunes and its bloody irritating &#8216;filing&#8217; system to find them what they pretend to &#8216;want&#8217; to listen to.</p>
<p>I know where every single song in my 4,000 track MP3 collection is, all filed in folders, either by artist, or about 10% in &#8216;genre&#8217; folders, such as &#8217;80s&#8217;, &#8216;Love&#8217;, &#8216;Dance&#8217;, etc. I don&#8217;t want a long list of 4,000 tracks, thank you, that&#8217;s for idiots.</p>
<p>Your &#8216;long list&#8217; idea doesn&#8217;t work when you are dealing with thousands of files. I remember the position of some of the 4,000 songs SPATIALLY, i.e. I know it&#8217;s in the first, top level folder,<br />
A-F<br />
not in<br />
G-M<br />
or whatever, and then within<br />
A-F<br />
it&#8217;s within<br />
Dance<br />
etc.</p>
<p>Your &#8216;huge list&#8217; idea is stupid. Microsoft&#8217;s &#8216;Ribbon&#8217; is equally stupid. </p>
<p>Spatial memory is where it&#8217;s at. I will reveal all very soon&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Subtlety hinders grokability by Nicholas Harris</title>
		<link>http://brianwill.net/blog/2008/03/17/subtlety-hinders-grokability/comment-page-1/#comment-4052</link>
		<dc:creator>Nicholas Harris</dc:creator>
		<pubDate>Tue, 06 Oct 2009 15:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/2008/03/17/subtlety-hinders-grokability/#comment-4052</guid>
		<description>I agree. Yet it isn&#039;t just euphoria that &#039;blinds the designer to some side-effect&#039;, but a practically unavoidable &quot;tunnel-vision&quot; that prevents the designer from being mindful of all aspects and interdependencies of their language&#039;s syntax and semantics. There is just too much to be familiar with whilst the design is in flux. The pragmatic designer concentrates on one particular area, but it is all too easy to forget about a superficially unrelated aspect, especially if that part of the design has not been looked at recently. I have found this to be a great problem in fusing the styles and rich capabilities of my multi-paradigm language. A simpler, one paradigm language would present far fewer difficulties.</description>
		<content:encoded><![CDATA[<p>I agree. Yet it isn&#8217;t just euphoria that &#8216;blinds the designer to some side-effect&#8217;, but a practically unavoidable &#8220;tunnel-vision&#8221; that prevents the designer from being mindful of all aspects and interdependencies of their language&#8217;s syntax and semantics. There is just too much to be familiar with whilst the design is in flux. The pragmatic designer concentrates on one particular area, but it is all too easy to forget about a superficially unrelated aspect, especially if that part of the design has not been looked at recently. I have found this to be a great problem in fusing the styles and rich capabilities of my multi-paradigm language. A simpler, one paradigm language would present far fewer difficulties.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Learn to program in 20+ easy steps by Appi Dhillon</title>
		<link>http://brianwill.net/blog/2009/07/22/learn-to-program-in-20-easy-steps/comment-page-1/#comment-4047</link>
		<dc:creator>Appi Dhillon</dc:creator>
		<pubDate>Tue, 29 Sep 2009 05:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=687#comment-4047</guid>
		<description>Fantastic goal!  Thanks so much for sharing.  I&#039;ve recently been intrigued by Erlang.  If it&#039;s not too much bother, I hope you&#039;ll consider putting together lessons for a basic introduction to Erlang and Concurrent Oriented Programming as part of your worthy goal to teach programming.  I&#039;m growing more certain every day that learning to support multi-core, multi-processor, and distributed programming is as important to learn today as any other aspect of programming.  Thank you again!</description>
		<content:encoded><![CDATA[<p>Fantastic goal!  Thanks so much for sharing.  I&#8217;ve recently been intrigued by Erlang.  If it&#8217;s not too much bother, I hope you&#8217;ll consider putting together lessons for a basic introduction to Erlang and Concurrent Oriented Programming as part of your worthy goal to teach programming.  I&#8217;m growing more certain every day that learning to support multi-core, multi-processor, and distributed programming is as important to learn today as any other aspect of programming.  Thank you again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reinventing the desktop (part 2): I heard you like lists&#8230; [text version] by Kevin Cannon</title>
		<link>http://brianwill.net/blog/2009/08/03/reinventing-the-desktop-part-2-i-heard-you-like-lists-now-in-text-form/comment-page-1/#comment-4039</link>
		<dc:creator>Kevin Cannon</dc:creator>
		<pubDate>Sun, 20 Sep 2009 22:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=721#comment-4039</guid>
		<description>Have you seen the way the help in OSX Leopard works? It&#039;s very nice - I think you&#039;d like it.

http://www.youtube.com/watch?v=ggoTQqNXOQs</description>
		<content:encoded><![CDATA[<p>Have you seen the way the help in OSX Leopard works? It&#8217;s very nice &#8211; I think you&#8217;d like it.</p>
<p><a href="http://www.youtube.com/watch?v=ggoTQqNXOQs" rel="nofollow">http://www.youtube.com/watch?v=ggoTQqNXOQs</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nationalschriftattribut by Nicholas Harris</title>
		<link>http://brianwill.net/blog/2007/06/05/nationalschriftattribut/comment-page-1/#comment-4025</link>
		<dc:creator>Nicholas Harris</dc:creator>
		<pubDate>Sat, 12 Sep 2009 13:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/2007/06/05/nationalschriftattribut/#comment-4025</guid>
		<description>Damn. I forgot how these things eat indentation. Using _ for space then:

foo a b
_ _ _ _ bar c d (moo) e f g
_ _ _ _ ...h i j k l

I hope this makes sense now...</description>
		<content:encoded><![CDATA[<p>Damn. I forgot how these things eat indentation. Using _ for space then:</p>
<p>foo a b<br />
_ _ _ _ bar c d (moo) e f g<br />
_ _ _ _ &#8230;h i j k l</p>
<p>I hope this makes sense now&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Nationalschriftattribut by Nicholas Harris</title>
		<link>http://brianwill.net/blog/2007/06/05/nationalschriftattribut/comment-page-1/#comment-4024</link>
		<dc:creator>Nicholas Harris</dc:creator>
		<pubDate>Sat, 12 Sep 2009 13:11:24 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/2007/06/05/nationalschriftattribut/#comment-4024</guid>
		<description>foo a b
        bar c d (moo) e f g
        ...h i j k l


My suggestion (may look less weird than starting a new line with a comma)
...for your interesting Pythonic LISP.</description>
		<content:encoded><![CDATA[<p>foo a b<br />
        bar c d (moo) e f g<br />
        &#8230;h i j k l</p>
<p>My suggestion (may look less weird than starting a new line with a comma)<br />
&#8230;for your interesting Pythonic LISP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Stop creating new languages by Nicholas Harris</title>
		<link>http://brianwill.net/blog/2009/08/30/stop-creating-new-languages/comment-page-1/#comment-4015</link>
		<dc:creator>Nicholas Harris</dc:creator>
		<pubDate>Sun, 06 Sep 2009 14:18:58 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=844#comment-4015</guid>
		<description>New languages should be privately tested by their creators by applying them to the task of building whole applications, user interfaces or operating systems. If this resultant software proves to be a success (user-centred, rapidly-developed, efficient and robust) then the language-author can &quot;come out of hiding&quot; and tell the world what weird and wonderful homebrew language they used to make it all a resounding success without fear of ridicule.

Just creating a freeware game with your new language as a proof of concept may be sufficient to convince others of its utility. You would at least attract potential &quot;modders&quot; who would be prepared to learn your language in order to script new AI behaviours, etc.

I say this because I have been working on an entirely new language for very many years, struggling to find the exact ingredients to &quot;bake the perfect cake&quot;. My fear being that I will need some feature or programming paradigm in the future and curse the tools at my disposal for not supporting those semantics - something that would be made all the more infuriating by having the knowledge that I was in the ideal position to avoid all of these problems if I had only anticipated them in the design at the outset. That said, I also wanted to keep my language &quot;small&quot; in the sense that it could be described by a thin manual as I felt that there were many &#039;full featured&#039; languages out there already that just seemed to have musty annexes that one didn&#039;t come into regular enough contact with to retain a degree of mastery and which, as a result, forced you back into reading a huge reference manual.

I don&#039;t want to sound negative as I quite understand the desire to tell people who may be &quot;in a position to understand what you are on about&quot; what you have been able to achieve. I know no one who I can talk about the specific details of what I have been working on and have, eventually, come to accept this. In fact, if I were to find that someone wanted to really know I wouldn&#039;t tell them because I would not want them to steal my ideas and implement something similar to my work long before I got around to doing it (as I am quite a slow worker). I also want my ideas to be taken as a package, rather than &quot;cherry-picked&quot; as it is how they all fit together that makes it significant.

Anyway, best of luck with Animus. I can say that designing a language makes for an extremely diverting intellectual pursuit - even if there is no money at the end of it...</description>
		<content:encoded><![CDATA[<p>New languages should be privately tested by their creators by applying them to the task of building whole applications, user interfaces or operating systems. If this resultant software proves to be a success (user-centred, rapidly-developed, efficient and robust) then the language-author can &#8220;come out of hiding&#8221; and tell the world what weird and wonderful homebrew language they used to make it all a resounding success without fear of ridicule.</p>
<p>Just creating a freeware game with your new language as a proof of concept may be sufficient to convince others of its utility. You would at least attract potential &#8220;modders&#8221; who would be prepared to learn your language in order to script new AI behaviours, etc.</p>
<p>I say this because I have been working on an entirely new language for very many years, struggling to find the exact ingredients to &#8220;bake the perfect cake&#8221;. My fear being that I will need some feature or programming paradigm in the future and curse the tools at my disposal for not supporting those semantics &#8211; something that would be made all the more infuriating by having the knowledge that I was in the ideal position to avoid all of these problems if I had only anticipated them in the design at the outset. That said, I also wanted to keep my language &#8220;small&#8221; in the sense that it could be described by a thin manual as I felt that there were many &#8216;full featured&#8217; languages out there already that just seemed to have musty annexes that one didn&#8217;t come into regular enough contact with to retain a degree of mastery and which, as a result, forced you back into reading a huge reference manual.</p>
<p>I don&#8217;t want to sound negative as I quite understand the desire to tell people who may be &#8220;in a position to understand what you are on about&#8221; what you have been able to achieve. I know no one who I can talk about the specific details of what I have been working on and have, eventually, come to accept this. In fact, if I were to find that someone wanted to really know I wouldn&#8217;t tell them because I would not want them to steal my ideas and implement something similar to my work long before I got around to doing it (as I am quite a slow worker). I also want my ideas to be taken as a package, rather than &#8220;cherry-picked&#8221; as it is how they all fit together that makes it significant.</p>
<p>Anyway, best of luck with Animus. I can say that designing a language makes for an extremely diverting intellectual pursuit &#8211; even if there is no money at the end of it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Stop creating new languages by Brian Will</title>
		<link>http://brianwill.net/blog/2009/08/30/stop-creating-new-languages/comment-page-1/#comment-4011</link>
		<dc:creator>Brian Will</dc:creator>
		<pubDate>Wed, 02 Sep 2009 00:53:46 +0000</pubDate>
		<guid isPermaLink="false">http://brianwill.net/blog/?p=844#comment-4011</guid>
		<description>&gt; The reason it doesn’t make sense to embed Haskell in Lisp is that it is statically typed

I don&#039;t think you understand the idea. C is static and native compiled too, of course, but an in-memory representation of C code in Lisp can be compiled out to object code. The Lisp layer becomes just syntax and a build system, effectively.

Languages with their own runtime are a bit trickier. If you wanted, say, to write Python in Animus but target CPython, Animus somehow has to get its hooks into running and managing CPython. Or say you&#039;re writing Javascript in Animus but targeting the browser: there&#039;s no way to do it, really, except to generate actual Javascript source (like GWT, I suppose). In any of these scenarios, you&#039;re bridging over &quot;legacy&quot; layers, which is never ideal. The idea, though, is that we would eventually ditch these intermediate layers. But in the mean time, I admit, things would be a bit messy.</description>
		<content:encoded><![CDATA[<p>> The reason it doesn’t make sense to embed Haskell in Lisp is that it is statically typed</p>
<p>I don&#8217;t think you understand the idea. C is static and native compiled too, of course, but an in-memory representation of C code in Lisp can be compiled out to object code. The Lisp layer becomes just syntax and a build system, effectively.</p>
<p>Languages with their own runtime are a bit trickier. If you wanted, say, to write Python in Animus but target CPython, Animus somehow has to get its hooks into running and managing CPython. Or say you&#8217;re writing Javascript in Animus but targeting the browser: there&#8217;s no way to do it, really, except to generate actual Javascript source (like GWT, I suppose). In any of these scenarios, you&#8217;re bridging over &#8220;legacy&#8221; layers, which is never ideal. The idea, though, is that we would eventually ditch these intermediate layers. But in the mean time, I admit, things would be a bit messy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
