s_gourichon

Not sure it really has huge benefits, but I guess something like this should work:

``` #!/bin/sh N=20 msg_len=$(git log -1 --pretty=%B | wc -c) if [ "$msg_len" -lt "$N" ]; then exit 125 fi # Here you would run your actual test and report 0 (good), 1 (bad) as needed exit 0 ```

Also floats seem to "forget" the integer part, and also have two minus signs when negative.

Nice. Comprehensive unit tests are indeed welcome. Even a simple test code that tests all features, flags combinations, etc, and outputs a log. It will make easy for anyone to run it and compare the logs.

I had a bug:

    u_printf( my_output_cb, NULL, "%d" NL, -42 );

prints:

--42

I may have found an explanation. In u_parse_format(), case 'i': calls u_itoa( value, buffer, 10, false ); which outputs minus sign.

Then if ( number ) does if ( sign ) { output_cb( '-', ctx ); chars_written++; } which outputs another minus sign.

> visual programming

25 years ago when I read that Microsoft has a software development environment named "Visual Studio" I imagined, well, something with graphs and nodes and flow and... Well something visual, right? Now it's 2024 and VS is still not visual.

Of course things are not as simple. Flyde (along with many alternatives mentioned) is visual IMHO. Keep up the good work!

In my opinion, you're spot on: being deprived of hearing the lowest frequencies typically occurs only when there's a pressure imbalance between the inner and outer ear. Therefore, when you experience silence at these lowest frequencies due to noise cancelling, your brain may assume a pressure imbalance must be the cause.

I've had the opportunity to use a variety of noise cancelling headphones over the years, from various brands, both in-ear and over-ear, and they all had this effect.

The good news is that you can become completely accustomed to it: after a while, the brain understands that there's no pressure imbalance, and it becomes a non-issue. Not hearing low frequencies is exactly what we expect from the product.

The article goes further to discuss some slope in a graph around 500Hz, which might be true, but I don't subscribe to that. It seems unnecessary to explain the observed facts and adds nothing.

What is not addressed at all is why all models seem to emit a subtle continuous shhhhhhh across a broad range of high frequencies. It's so subtle that you can only notice it when the outside environment is already quiet. I've never been certain whether it's just noise from the signal processing. My intuition is that it's artificially added to prevent inducing tinnitus in some users.