<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>mask of the robtasm (Posts about javascript)</title><link>https://mahurin.us/robtasm/</link><description></description><atom:link href="https://mahurin.us/robtasm/categories/javascript.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2026 &lt;a href="mailto:robert.s.mahurin@gmail.com"&gt;rob mahurin&lt;/a&gt; </copyright><lastBuildDate>Sat, 31 Jan 2026 04:42:48 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>watching for changes</title><link>https://mahurin.us/robtasm/posts/2025/06/21/watching-for-changes/</link><dc:creator>rob mahurin</dc:creator><description>&lt;p&gt;One of the differences between the kind of text-mode/compile interface
that I like to use, versus the WYSIWYG-style editors that the rest of
the world has been using since forever, is that you generally have to
do something or other in order to see whether your changes are having
any effect.  I've spent some time yesterday and today trying to come
up with a mechanism to ease that transition, and I think I like what I
have.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://mahurin.us/robtasm/posts/2025/06/21/watching-for-changes/"&gt; …&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;</description><category>html</category><category>javascript</category><category>nikola</category><guid>https://mahurin.us/robtasm/posts/2025/06/21/watching-for-changes/</guid><pubDate>Sat, 21 Jun 2025 22:08:44 GMT</pubDate></item></channel></rss>