<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: pansa2</title><link>https://news.ycombinator.com/user?id=pansa2</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 10:05:28 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=pansa2" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by pansa2 in "Changing how we develop Ladybird"]]></title><description><![CDATA[
<p>Lua is the same IIRC: open source but not open development.<p>It’s MIT licensed, and the maintainers are always grateful for bug reports, but all the code in the project was written by just 3 people.</p>
]]></description><pubDate>Fri, 05 Jun 2026 09:24:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=48410068</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=48410068</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48410068</guid></item><item><title><![CDATA[New comment by pansa2 in "The Green Side of the Lua"]]></title><description><![CDATA[
<p>> <i>The C interface to ruby is just superb.</i><p>How does it handle garbage collection? AFAIK GC is the main reason behind Lua's stack-based API: it's designed so that C code never needs to hold a pointer to a Lua object, which means an object will never be garbage-collected while C code is still trying to use it.<p>OTOH Python <i>does</i> allow C code to hold such pointers - so it requires that code to perform error-prone manual reference-counting.<p>How does Ruby solve this problem?</p>
]]></description><pubDate>Thu, 28 May 2026 08:44:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=48306340</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=48306340</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48306340</guid></item><item><title><![CDATA[New comment by pansa2 in "The Green Side of the Lua"]]></title><description><![CDATA[
<p>I guess it alludes to “The Dark Side of the Moon”</p>
]]></description><pubDate>Thu, 28 May 2026 07:00:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=48305584</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=48305584</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48305584</guid></item><item><title><![CDATA[New comment by pansa2 in "Python 3.15: features that didn't make the headlines"]]></title><description><![CDATA[
<p>Mojo?</p>
]]></description><pubDate>Fri, 22 May 2026 12:57:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=48235246</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=48235246</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48235246</guid></item><item><title><![CDATA[New comment by pansa2 in "Python 3.15: features that didn't make the headlines"]]></title><description><![CDATA[
<p>`npm isntall`</p>
]]></description><pubDate>Thu, 21 May 2026 22:36:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=48229666</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=48229666</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48229666</guid></item><item><title><![CDATA[New comment by pansa2 in "Mojo 1.0 Beta"]]></title><description><![CDATA[
<p>> <i>they intended to make it compatible with existing Python code</i><p>That was the original claim, but it was quietly removed from the website. (Did they fall for the common “Python is a simple language” misconception?).<p>Now they promise I can “write like Python”, but don’t even support fundamentals like classes (which are part of stage 3 of the roadmap, but they’re still working on stage 1).<p>Maybe Mojo will achieve all its goals, but so far has been over-promising and under-delivering - it’s starting to remind me of the V language.</p>
]]></description><pubDate>Fri, 08 May 2026 07:35:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=48059892</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=48059892</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48059892</guid></item><item><title><![CDATA[New comment by pansa2 in "NZ Government to Disestablish the BSA"]]></title><description><![CDATA[
<p>> <i>New Zealanders are forced to pay a sky high TV licence</i><p>There’s no TV license in New Zealand</p>
]]></description><pubDate>Wed, 06 May 2026 12:33:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=48035476</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=48035476</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48035476</guid></item><item><title><![CDATA[New comment by pansa2 in "Executable installer will stop being released with Python 3.16"]]></title><description><![CDATA[
<p>The PEP for this change is here [0] and discussion of it is here [1]. Both are very long and seem to represent a huge amount of complexity, apparently to make installing Python easier for novices?<p>But what about those of us who listened to Rich Hickey and prefer "simple" over "easy"? With the executable installer no longer available, how do I get a copy of python.exe, python316.dll etc onto my machine so that `C:\Python316\python.exe <script>` works, without having to think about `py`, `pymanager`, Windows Store etc?<p>[0] <a href="https://peps.python.org/pep-0773/" rel="nofollow">https://peps.python.org/pep-0773/</a><p>[1] <a href="https://discuss.python.org/t/pep-773-a-python-installation-manager-for-windows/77900" rel="nofollow">https://discuss.python.org/t/pep-773-a-python-installation-m...</a></p>
]]></description><pubDate>Sun, 03 May 2026 14:38:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=47997369</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47997369</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47997369</guid></item><item><title><![CDATA[New comment by pansa2 in "How to make a fast dynamic language interpreter"]]></title><description><![CDATA[
<p>In a similar vein, see this page about the performance of the interpreter for the dynamic language Wren: <a href="https://wren.io/performance.html" rel="nofollow">https://wren.io/performance.html</a><p>Unlike the Zef article, which describes implementation techniques, the Wren page also shows ways in which language design can contribute to performance.<p>In particular, Wren gives up dynamic object shapes, which enables copy-down inheritance and substantially simplifies (and hence accelerates) method lookup. Personally I think that’s a good trade-off - how often have you really needed to add a method to a class after construction?</p>
]]></description><pubDate>Tue, 21 Apr 2026 06:31:44 +0000</pubDate><link>https://news.ycombinator.com/item?id=47845313</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47845313</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47845313</guid></item><item><title><![CDATA[New comment by pansa2 in "Rubysyn: Clarifying Ruby's Syntax and Semantics"]]></title><description><![CDATA[
<p>Yes, Smalltalk's syntax fits on a postcard - and it's possible to go even more minimal than that, e.g. Lisp or Forth.<p>OTOH Ruby doesn't need a postcard, it needs a full poster.</p>
]]></description><pubDate>Sun, 05 Apr 2026 09:34:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=47647674</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47647674</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47647674</guid></item><item><title><![CDATA[New comment by pansa2 in "Python 3.15's JIT is now back on track"]]></title><description><![CDATA[
<p>> <i>all the encoding/decoding functions default to utf-8</i><p>Languages that use UTF-8 natively don't need those functions at all. And the ones in Python aren't trivial - see, for example, `surrogateescape`.<p>As the sibling comment says, the only benefit of all this encoding/decoding is that it allows strings to support constant-time indexing of code points, which isn't something that's commonly needed.</p>
]]></description><pubDate>Wed, 18 Mar 2026 01:07:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=47420475</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47420475</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47420475</guid></item><item><title><![CDATA[New comment by pansa2 in "Python 3.15's JIT is now back on track"]]></title><description><![CDATA[
<p>> <i>Wouldn't this get the funding back?</i><p>The funding was Microsoft employing most of the team. They were laid off (or at least, moved onto different projects), apparently because they weren't working on AI.</p>
]]></description><pubDate>Tue, 17 Mar 2026 23:51:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=47419957</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47419957</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47419957</guid></item><item><title><![CDATA[New comment by pansa2 in "Python 3.15's JIT is now back on track"]]></title><description><![CDATA[
<p>The Python devs didn’t want to make huge changes because they were worried Python 3 would end up taking forever like Perl 6. Instead they went to the other extreme and broke everyone’s code for trivial reasons and minimal benefit, which meant no-one wanted to upgrade.<p>Even the main driver for Python 3, the bytes-Unicode split, has unfortunately turned out to be sub-optimal. Python essentially bet on UTF-32 (with space-saving optimisations), while everyone else has chosen UTF-8.</p>
]]></description><pubDate>Tue, 17 Mar 2026 23:19:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=47419675</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47419675</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47419675</guid></item><item><title><![CDATA[New comment by pansa2 in "Python 3.15's JIT is now back on track"]]></title><description><![CDATA[
<p>Maybe they could have two versions of the interpreter, one that’s thread-safe and one that’s optimised for single-threading?<p>Microsoft used to do this for their C runtime library.</p>
]]></description><pubDate>Tue, 17 Mar 2026 22:38:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=47419319</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47419319</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47419319</guid></item><item><title><![CDATA[New comment by pansa2 in "Python 3.15's JIT is now back on track"]]></title><description><![CDATA[
<p>There isn’t a dev mailing list any more, is there? Do you mean the Discord forum?</p>
]]></description><pubDate>Tue, 17 Mar 2026 22:29:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=47419228</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47419228</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47419228</guid></item><item><title><![CDATA[New comment by pansa2 in "Python 3.15's JIT is now back on track"]]></title><description><![CDATA[
<p>>> <i>Python 2->3 transition</i><p>> <i>taking backwards compatibility so seriously</i><p>Python’s backward compatibility story still isn’t great compared to things like the Go 1.x compatibility promise, and languages with formal specs like JS and C.<p>The Python devs still make breaking changes, they’ve just learned not to update the major version number when they do so.</p>
]]></description><pubDate>Tue, 17 Mar 2026 22:21:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=47419164</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47419164</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47419164</guid></item><item><title><![CDATA[New comment by pansa2 in "My “grand vision” for Rust"]]></title><description><![CDATA[
<p>Crystal’s syntax is similar to Ruby’s, but AFAIK the similarity more-or-less ends there.</p>
]]></description><pubDate>Mon, 09 Mar 2026 08:22:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=47306180</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47306180</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47306180</guid></item><item><title><![CDATA[New comment by pansa2 in "Warn about PyPy being unmaintained"]]></title><description><![CDATA[
<p>You’re right, of course: even Guido seems to have been moved off working on CPython and onto some tangentially-related AI technology.<p>However, Faster CPython was supposed be a 4-year project, delivering a 1.5x speedup each year. AFAIK they had the full 4 years at Microsoft, and only achieved what they originally planned to do in 1 year.</p>
]]></description><pubDate>Sun, 08 Mar 2026 11:18:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=47296434</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47296434</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47296434</guid></item><item><title><![CDATA[New comment by pansa2 in "Warn about PyPy being unmaintained"]]></title><description><![CDATA[
<p>PyPy is a fantastic achievement and deserves far more support than it gets. Microsoft’s “Faster CPython” team tried to make Python 5x faster but only achieved ~1.5x in four years - meanwhile PyPy has been running at <i>over</i> 5x faster for decades.<p>On the other hand, I always got the impression that the main goal of PyPy is to be a research project (on meta-tracing, STM etc) rather than a replacement for CPython in production.<p>Maybe that, plus the core Python team’s indifference towards non-CPython implementations, is why it doesn’t get the recognition it deserves.</p>
]]></description><pubDate>Sun, 08 Mar 2026 06:57:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=47295211</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47295211</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47295211</guid></item><item><title><![CDATA[New comment by pansa2 in "Index, Count, Offset, Size"]]></title><description><![CDATA[
<p>Fundamentally, CPUs use 0-based addresses. That's unavoidable.<p>We can't choose to switch to 1-based indexing - either we use 0-based everywhere, or a mixture of 0-based and 1-based. Given the prevalence of off-by-one errors, I think the most important thing is to be consistent.</p>
]]></description><pubDate>Sat, 21 Feb 2026 14:20:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=47101092</link><dc:creator>pansa2</dc:creator><comments>https://news.ycombinator.com/item?id=47101092</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47101092</guid></item></channel></rss>