https://yabu.me https://yabu.me/npub1rvqtlf0gwacxmmdaznz44nm7adw78fmgzdacc4tjzhweruent6lsw9qc7s https://yabu.me/nevent1qqsy2la3mvrv5nnkjx93qg8qff3mttkflm9lpxezy6dhf75de3wzm6gzyqdsp0a9apmhqm0dh52v2kk00m44mca8dqfhhrz4wg2amy0nxd0t724f9cu In reply to <a href='/nevent1qqsyk3xstszjy59zaw2hf3jqhp4vw5lelyvjusahg4zssnec5w9mp9qpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43q09a5qw'>nevent1q…a5qw</a><br/>_________________________<br/><br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub105ve72qqmjxz08skum2lkds9qkj67689djwwr2a0qkrxts3hqydqm9hk8p" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>npub105ve72qqmjxz08skum2lkds9qkj67689djwwr2a0qkrxts3hqydqm9hk8p</span> (<span class="italic">npub105v…hk8p</span>)</a></span> thanks for sharing my article, and for the additional comments. I&#39;m glad to hear I&#39;m not the only one who thinks this is a sad state of affairs.<br/><br/>I think the big challenge is backwards compatibility. We need to evolve C in a way that doesn&#39;t break too many applications. There is enough C code out there that any change is going to break something. On the other hand: past updates to C libraries have broken applications, so this isn&#39;t a new problem. We just have to be willing to accept the cost and provide good tools to make fixes easy. 2023-11-20T11:30:18Z