Hacker News: mattclarkdotnet

New comment by mattclarkdotnet in "Flat Datacenter Networks at Scale at Amazon"

mattclarkdotnet — Tue, 09 Jun 2026 23:26:50 +0000

It's almost certainly meant to be 27%, not a factor of 27.

New comment by mattclarkdotnet in "Humanoid Robot Actuators"

mattclarkdotnet — Mon, 04 May 2026 10:08:19 +0000

So you’re wanting to bet that we’ll get humanoid robots capable of driving a dumb car at L4 before we get cars capable of L5? When we have no humanoid robots driving cars, and many L4 cars driving around? I’ll take that!

New comment by mattclarkdotnet in "We still don't have a more precise value for "Big G""

mattclarkdotnet — Wed, 29 Apr 2026 13:42:45 +0000

Only by embracing solipsism, in which case why are you here debating things, since your entire truth is derivable from your existence alone with no other observations or interactions required?

New comment by mattclarkdotnet in "We still don't have a more precise value for "Big G""

mattclarkdotnet — Wed, 29 Apr 2026 08:35:02 +0000

Philosophy can be perfectly effective as a tool of thought while still being unable to resolve self evidently unsolvable “ultimate questions”

New comment by mattclarkdotnet in "We still don't have a more precise value for "Big G""

mattclarkdotnet — Wed, 29 Apr 2026 07:27:16 +0000

The theistic schism? I had to look it up, and was not cleverer after. Nobody can ever know an ultimate why, for obvious and well established philosophical reasons. At least the scientists are trying to squeeze the knowledge gap down as small as possible instead of making up stories.

New comment by mattclarkdotnet in "Fully Featured Audio DSP Firmware for the Raspberry Pi Pico"

mattclarkdotnet — Mon, 27 Apr 2026 23:01:12 +0000

Oh it's worse than that, for distribution and playback sampling at more than 48kHz is likely worse in many ways due to unwanted ultrasonic noise and increased intermodulation distortion. 96/24 makes sense for production, and 96/float56 is common in DSP chains.

New comment by mattclarkdotnet in "Fully Featured Audio DSP Firmware for the Raspberry Pi Pico"

mattclarkdotnet — Mon, 27 Apr 2026 22:02:40 +0000

The analog input will use separate ADC modules, just as the analog output uses separate DACs. DSPi itself is purely digital (OK, excepting the PWM based sub out). These modules are just a few dollars on AliExpress for ~96dB SINAD

New comment by mattclarkdotnet in "Fully Featured Audio DSP Firmware for the Raspberry Pi Pico"

mattclarkdotnet — Mon, 27 Apr 2026 22:00:42 +0000

I2S input is on the roadmap, and hardware modules from AliExpress are being tested by Troy, so yes you will get plenty of analog inputs!

New comment by mattclarkdotnet in "Fully Featured Audio DSP Firmware for the Raspberry Pi Pico"

mattclarkdotnet — Mon, 27 Apr 2026 21:58:51 +0000

It's for the pico. RP2040 works fine, but RP2350 has a hardware FPU and much more processing capability, so supports more channels and filters

New comment by mattclarkdotnet in "Amateur armed with ChatGPT solves an Erdős problem"

mattclarkdotnet — Mon, 27 Apr 2026 00:25:37 +0000

We throw away food because we are so good at making it cheaply that the problem has shifted to distribution costs and fair wages. Also high productivity economies need to deal effectively with the Baumol effect (https://en.wikipedia.org/wiki/Baumol_effect). If they don't then even people in the USA can be food poor despite huge GDP per capita.

New comment by mattclarkdotnet in "Amateur armed with ChatGPT solves an Erdős problem"

mattclarkdotnet — Mon, 27 Apr 2026 00:15:18 +0000

You might enjoy the book "Red Plenty" by Francis Spufford, which traces the consequences of this thesis ("Capitalism already is a poor allocator") through the Khrushchev years of the USSR, seen through the eyes of the economists, mathematicians and planners who tried to do better than capitalism.

Of course there are in-between approaches like industrial policy in mixed economies, for example the South Korean shipbuilding industry. But those tend to work with the grain of capitalism, not against it.

New comment by mattclarkdotnet in "Migrating the American express payment network, twice"

mattclarkdotnet — Mon, 23 Mar 2026 08:54:03 +0000

At best it’s checking available credit. All the other stuff is done after the fact. The idea that any banking transaction involves “subtracting one number from another” is so wrong it’s barely worth engaging with.

New comment by mattclarkdotnet in "Migrating the American express payment network, twice"

mattclarkdotnet — Mon, 23 Mar 2026 03:40:53 +0000

Since when were payment networks latency sensitive? It’s usually 2 or more seconds to even get a payment up on the card terminal from the merchant POST system, then 2-5 seconds more from card presentation to getting approval back.

New comment by mattclarkdotnet in "Python 3.15's JIT is now back on track"

mattclarkdotnet — Thu, 19 Mar 2026 22:51:42 +0000

Thank you! Spy looks brilliant, especially the comptime-like freezing after import.

New comment by mattclarkdotnet in "Python 3.15's JIT is now back on track"

mattclarkdotnet — Wed, 18 Mar 2026 05:34:47 +0000

What's nuts is that the language doesn't guarantee that successive references to the same member value within the same function body are stable. You can look it up once, go off and do something else, and look it up again and it's changed. It's dynamism taken to an unnecessary extreme. Nobody in the real world expects this behaviour. Making it just a bit less dynamic wouldn't change the fundamentals of the language but it would make it a lot more tractable.

New comment by mattclarkdotnet in "Python 3.15's JIT is now back on track"

mattclarkdotnet — Wed, 18 Mar 2026 04:53:58 +0000

Let's not get started on the cached shared object refs for small integers....

New comment by mattclarkdotnet in "Python 3.15's JIT is now back on track"

mattclarkdotnet — Wed, 18 Mar 2026 04:51:09 +0000

It's still ridiculous. A hypothetical Python4 would treat function declarations as declarations not executable statements, with no impact on real world code except to remove all the boilerplate checks.

New comment by mattclarkdotnet in "Python 3.15's JIT is now back on track"

mattclarkdotnet — Wed, 18 Mar 2026 04:48:32 +0000

Allowing metaprogramming at module import (or another defined phase) would cover most monkey patching use cases. From __future__ import python4 would allow developers to declare their code optimisable.

New comment by mattclarkdotnet in "Python 3.15's JIT is now back on track"

mattclarkdotnet — Wed, 18 Mar 2026 04:45:18 +0000

Performance is one part of the discussion, but cleanliness is another. A Python4 that actually used typing in the interpreter, had value types, had a comptime phase to allow most metaprogramming to work (like monkey patching for tests) would be great! It would be faster, cleaner, easier to reason about, and still retain the great syntax and flexibility of the language.

New comment by mattclarkdotnet in "Python 3.15's JIT is now back on track"

mattclarkdotnet — Wed, 18 Mar 2026 04:20:26 +0000

Oh, and while we're at it, fix the "empty array is instantiated at parse time so all your functions with a default empty array argument share the same object" bullshit.