<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: ingy</title><link>https://news.ycombinator.com/user?id=ingy</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 18 May 2026 09:55:55 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=ingy" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by ingy in "Show HN: I made a Clojure-like language in Go, boots in 7ms"]]></title><description><![CDATA[
<p><a href="https://github.com/gloathub/glojure" rel="nofollow">https://github.com/gloathub/glojure</a> is the actively maintained fork.</p>
]]></description><pubDate>Sat, 09 May 2026 23:09:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=48079190</link><dc:creator>ingy</dc:creator><comments>https://news.ycombinator.com/item?id=48079190</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48079190</guid></item><item><title><![CDATA[New comment by ingy in "Show HN: I made a Clojure-like language in Go, boots in 7ms"]]></title><description><![CDATA[
<p>Try out this Wasm browser REPL <a href="https://gloathub.org/repl/" rel="nofollow">https://gloathub.org/repl/</a><p>Gloat is a Glojure AOT automation tool.
I worked with James Hamlin to get Glojure AOT going last summer and have been moving it forward since. I've also been working with marcingas (nooga) to get Gloat/Glojure/let-go all cooperating.</p>
]]></description><pubDate>Sat, 09 May 2026 22:49:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=48079017</link><dc:creator>ingy</dc:creator><comments>https://news.ycombinator.com/item?id=48079017</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48079017</guid></item><item><title><![CDATA[New comment by ingy in "I accidentally used YAML.parse instead of JSON.parse and it worked"]]></title><description><![CDATA[
<p>> "YAML documents can't start with a tab while JSON documents can, making JSON not a strict subset of YAML"<p>But YAML can start with tabs. Tabs are allowed as separating whitespace in most of the spec productions but are not allowed as indentation. Even though those tabs look like indentation, the spec productions don't interpret them as such.<p>See my comment above and esp see <a href="https://play.yaml.io/main/parser?input=CXsKCQkibGlzdCI6IFsKCQkJe30sCgkJCXt9CgkJXQoJfQo=" rel="nofollow">https://play.yaml.io/main/parser?input=CXsKCQkibGlzdCI6IFsKC...</a><p>Note: the YAML spec maintainers (I am one) have identified many issues with YAML which we are actively working on, but (somewhat surprisingly) we have yet to find a case where valid JSON is invalid YAML 1.2.</p>
]]></description><pubDate>Mon, 24 Jan 2022 19:42:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=30062858</link><dc:creator>ingy</dc:creator><comments>https://news.ycombinator.com/item?id=30062858</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=30062858</guid></item><item><title><![CDATA[New comment by ingy in "I accidentally used YAML.parse instead of JSON.parse and it worked"]]></title><description><![CDATA[
<p>This is completely valid YAML.<p>YAML does not allow tabs in indentation, but the tabs in your example are not indentation according to the YAML spec productions.<p>You can see it clearly here against many YAML parsers: <a href="https://play.yaml.io/main/parser?input=CXsKCQkibGlzdCI6IFsKCQkJe30sCgkJCXt9CgkJXQoJfQo=" rel="nofollow">https://play.yaml.io/main/parser?input=CXsKCQkibGlzdCI6IFsKC...</a><p>As tinita points out, sadly PyYAML and libyaml implement this wrong.<p>See <a href="https://matrix.yaml.info/" rel="nofollow">https://matrix.yaml.info/</a></p>
]]></description><pubDate>Mon, 24 Jan 2022 19:23:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=30062570</link><dc:creator>ingy</dc:creator><comments>https://news.ycombinator.com/item?id=30062570</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=30062570</guid></item><item><title><![CDATA[New comment by ingy in "I accidentally used YAML.parse instead of JSON.parse and it worked"]]></title><description><![CDATA[
<p>I'm one of the authors of the YAML specification. <a href="https://yaml.org/spec/1.2.2/" rel="nofollow">https://yaml.org/spec/1.2.2/</a><p>To date we honestly have not identified a case where where valid JSON is not valid YAML 1.2.<p>If anyone can point out a case where this is true, please file an issue here: <a href="https://github.com/yaml/yaml-spec/issues/" rel="nofollow">https://github.com/yaml/yaml-spec/issues/</a></p>
]]></description><pubDate>Mon, 24 Jan 2022 18:11:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=30061495</link><dc:creator>ingy</dc:creator><comments>https://news.ycombinator.com/item?id=30061495</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=30061495</guid></item><item><title><![CDATA[A New YAML Specification (Revision 1.2.2)]]></title><description><![CDATA[
<p>Article URL: <a href="https://yaml.com/blog/2021-10/new-yaml-spec/">https://yaml.com/blog/2021-10/new-yaml-spec/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=28717321">https://news.ycombinator.com/item?id=28717321</a></p>
<p>Points: 7</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 01 Oct 2021 12:00:01 +0000</pubDate><link>https://yaml.com/blog/2021-10/new-yaml-spec/</link><dc:creator>ingy</dc:creator><comments>https://news.ycombinator.com/item?id=28717321</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=28717321</guid></item><item><title><![CDATA[New comment by ingy in "Git 2.0 release notes"]]></title><description><![CDATA[
<p>You may want to take a look at <a href="https://github.com/ingydotnet/git-subrepo#readme" rel="nofollow">https://github.com/ingydotnet/git-subrepo#readme</a> (and join #git-commands on freenode).</p>
]]></description><pubDate>Wed, 12 Mar 2014 14:29:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=7385789</link><dc:creator>ingy</dc:creator><comments>https://news.ycombinator.com/item?id=7385789</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=7385789</guid></item><item><title><![CDATA[New comment by ingy in "Exploring an alternative to git-subtree"]]></title><description><![CDATA[
<p>Serendipitously, I've been working on a new Git command called `git-subrepo`
for the last 3 months that deals with all these concerns and more. The command
became fully usable about a week ago.<p>The <a href="https://github.com/ingydotnet/git-subrepo" rel="nofollow">https://github.com/ingydotnet/git-subrepo</a> addresses all the known concerns
of the project owner, project collaborators, and end users. It keeps state in
`path/subdir/.gitrepo` which means that git commands like `git mv` just work.<p>It also has squeaky clean history, which I've documented here:
<a href="https://github.com/ingydotnet/git-subrepo/blob/master/doc/intro-to-subrepo.md#clean-history" rel="nofollow">https://github.com/ingydotnet/git-subrepo/blob/master/doc/in...</a><p>Feel free to contact me by GitHub, IRC ingy@irc.freenode.net or email ingy@ingy.net.</p>
]]></description><pubDate>Mon, 24 Feb 2014 21:39:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=7293570</link><dc:creator>ingy</dc:creator><comments>https://news.ycombinator.com/item?id=7293570</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=7293570</guid></item></channel></rss>